Are SubScenes terrible?

[bill_prime]

I am trying to build scene logic to load a bunch of different positons/mocaps dynamically using SubScene loading.
There are so many things that don't work with SubScenes: external Person links, external atom AnimationPattern drivers, etc.

These subscenes have maybe 30-50 atoms and when I load a couple VAM just locks up totally.

Anyone else try stuff with SubScenes?

 

[atani]

Subscenes have their limitations and by design are meant to be used as self-containing resources. Many of the problems associated with subscenes are because they're taken beyond their intended scope. The subscene atom is rather new in terms of VAM 1.x development, and has some specificity that may not be very compatible with other VAM core features or bugs may exist. Possibly animation patterns may not handle subscenes at all.
Regarding subscenes, what you should start by asking is: why does it need to be in a subscene?

I use subscenes for specific needs where other options are too cumbersome or not suitable, while limiting its use as much as possible. If it spits out errors, it's important to understand what those errors mean. They may not mean you can't do something, just that such something will be potentially broken if the conditions are not met.

 

[entitycs]

I use SubScene Atoms extensively, but "never" save a scene with a "saved" subscene. Just "lambda" subscenes, so to speak, where if I load a subscene for re-use, I clear the fields out before saving the scene. One thing to note is that using Atom parenting (subscene or not) "moves" the components "into" the Parent atom - so you can't then call childAtom.GetComponent<x> as expected, aside from some cases where the childAtom is a Person.