I've got a Dialogue System Controller with a bunch of other components and nested children sitting in the main scene of my game. Running the scene from the editor works fine, but if I go through the title screen scene (which has no Dialogue System Controller or any dialogue system components in it), when the main scene loads the Dialogue System Controller GameObject and all its children don't exist. This, unsurprisingly, breaks the main scene.
There's no existing Dialogue System Controller that could be interfering with the instantiation in the main scene, so I'm not sure what's going on here.
Any help would be greatly appreciated!
Dialogue Manager GameObject not instantiating on scene change
Re: Dialogue Manager GameObject not instantiating on scene change
As is often the case, after posting this I uncovered the issue. There was a Save System component attached to the Dialogue System Controller gameobject that was destroying the GO due to its singleton nature, as there was a Save System present in the title screen.
Re: Dialogue Manager GameObject not instantiating on scene change
That'll do it. I've done that before myself. Glad you found the issue. The Dialogue System has 3 components that can act as singletons:
- Save System: This must be a singleton to manage data and scene transitions when changing scenes.
- Dialogue System Controller: Technically you can un-singleton it by unticking Other Settings > Don't Destroy On Load, but I strongly recommend running it as a singleton to make it easier and more performant to carry DS data such as variables and quest states across scene changes.
- Input Device Manager: Typically not a worry since it's also on the Dialogue Manager GameObject. But technically you can untick the Singleton checkbox to prevent it from destroying duplicates.