|
Description
|
If we work on the prims or the scripts of a worn attachement, detach it and attach again immediatly, the changes are normally lost.
Somewhere once I read one has to wait minimum 10 seconds before attaching the item again, because the asset server needs some time to save it.
Unfortunetly, especially in the last weeks, 10 seconds are not enough. I had some cases of lost changes last weeks. Waiting 30 seconds is a safer approach. But I had one case even that was enough.
My proposal: grey out or mark in any way detached (previouly worn) objects that are still unsaved, so we can see how long we have to wait to attach it again.
Or give us some other mechanism to make sure asset is saved.
|
If we work on the prims or the scripts of a worn attachement, detach it and attach again immediatly, the changes are normally lost.
Somewhere once I read one has to wait minimum 10 seconds before attaching the item again, because the asset server needs some time to save it.
Unfortunetly, especially in the last weeks, 10 seconds are not enough. I had some cases of lost changes last weeks. Waiting 30 seconds is a safer approach. But I had one case even that wasn't enough.
My proposal: grey out or mark in any way detached (previouly worn) objects that are still unsaved, so we can see how long we have to wait to attach it again.
Or give us some other mechanism to make sure asset is saved.
|