To all creators using VAMStory
A warning about the new synchronization system.
I can't thank enough
@PetaZwega to shine some light on that.
VAMStory since 1.17 waits for all plugins of the "suite" to be ready before initializing themselves. Due to the way Unity works... realtime updates (Update function) and coroutines cannot work while the atoms are in a off state.
Which result in any other active (in on state) plugin of VAMStory waiting forever until the atoms are swapped to a on state.
This does not mean you have to control the on/off state of VAMStory plugins,
it means you have to keep all VAMStory atoms on. For Director, there is pretty much no problem since the plugin is "invisible" in the scene. For Actions it means you can use the new option "UI starts hidden (at scene load)" if you need, and well... Story will only show up when you start a group so you don't need to control it's initial state at all.
VAMStory is thought to be the "main controller" of the scene. And ensure that no matter what PC is behind (fast, normal, slow or turbo-potato-slow), the scene starts properly.
Drop all "old tricks" (animation patterns, scene animation, Timeline...) to control the start of the scene, and favor VAMS for any scene initialization process AND keep all atoms on.
I'm gonna update the documentation to mention that and also add a warning in the "ingame" help section.
If there is any trouble for you to understand what this update note says, feel free to ask me more in the discussion.
Cheers!
