I'm getting a very weird message trying to start a scene.

The scene is being started from its parent quest. I've set up a property, set it to the scene in question (correctly, I just checked) and launch it from a fragment in the quests start stage.

The quest starts. The fragment runs. But I get

"cannot start scene because its parent quest was not running"

Whiskey Tango Foxtrot, anyone?

Just had the same problem. Seems you cannot start a scene from within the quest's startup stage, because the quest isn't actually considered to be running until the startup stage is done.

I worked around it by simply doing a RegisterForSingleUpdate(1) in the startup stage, and starting the scene from within the OnUpdate event.

Ciao, muh!

There is also a checkbox on the SCENE tab that says "run scene at Quest startup" (or something like that).

I never tried it, but does that work?

(note: Many checkboxes like that one don't work ... So don't come shoot me if it doesn't)


the other way to handle it is to have a Stage 1 after Stage 0. Do all your setup in Stage0, then at the end of that advance to stage-1, which has only the Scene.Start() command. That does work.

I think it's because there is a delay between the quest being 'started' and the quest actually 'running'. That delay is when your calling the scene function, so it doesn't work. Try the aforementioned checkbox. I believe this start delay is exactly why they added that checkbox. So that you could have scenes run on the quests start, instead of having this problem.

Makes sense.

The checkbox does indeed work, so it's clearly the way to go