If you have a scene with multiple subscenes, when you disable a/some subscene(s) with a person atom within (and possibly others), then add a new atom to anything, the hierarchy window stops updating. Sometimes, re-enabling all subscenes at the same time can unlock it (if you have enough vram), but it often looses changes, or causes vam to be unstable in other ways, which can result in corrupted saved scenes changes. When this happens it also results in an endless spinning hourglass icon in the UI.
It makes it almost impossible to continue working on the scene. My guess is it is locking-up/crashing the thread early, resulting in other incomplete code even if later worked-around. Subscenes are great for vram conservation and reducing FPS impact of things like multiple scene areas, but they really could use some fixes.
They often also break most plugins seemingly due to merging and optimizations as well, but this is most probably as intended and to be expected, and is much less of an issue. I don't expect any fix on this second issue as it's not really a bug, and most likely just the way they work.
It makes it almost impossible to continue working on the scene. My guess is it is locking-up/crashing the thread early, resulting in other incomplete code even if later worked-around. Subscenes are great for vram conservation and reducing FPS impact of things like multiple scene areas, but they really could use some fixes.
They often also break most plugins seemingly due to merging and optimizations as well, but this is most probably as intended and to be expected, and is much less of an issue. I don't expect any fix on this second issue as it's not really a bug, and most likely just the way they work.
