We discussed this one in http://www.gamesas.com/topic/1360514-cannot-start-scene-because-its-parent-quest-was-not-running/. Rather than necro the thread, I thought I'd start a new one.

Basically, I have the same problem again. I know I can get around it by making it start when the quest starts, but having just dragged myself beaten and bloody from the wreckage of a 50 phase scene, I think I'd prefer to have lots of small scenes stitched together for the next one. Having a quest for each of them seems wasteful.

The really odd thing is that this is happening in stage 30 - two stages have happened by this point, including the explicit startup stage. I'd have thought that everything would have been initialised by that point. Oh, well, go figure.

I suppose I could auto start the quest in an OnUpdate loop. I can probably auto start the first scene as well and then hand script the others to start. has anyone else found any useful strategies for dealing with this since 2012?

The other reason I wanted to post this: are people aware that the people over on www.gamesas.com are copying our threads verbatim and republishing them with the names and avatars changed? I mean compare http://www.gamesas.com/cannot-start-scene-because-its-parent-quest-was-not-run-t258379.html with the one I linked at the start of this post.

Is it just me, or is that a bit bloody cheeky?

[edit]

Apparently I am secretly both "Louise Lowe" and "Matt Bee" :/

why don't you just put all the scenes on the same quest and start each of them from the previous scene's end fragment?

Does your startup stage use SetStage to set the following two stages? SetStage will not return until the stage you set has finish running its fragments, and it's likely the quest is not considered started until the startup stage is finished.

I have a few different ways into the quest for debug purposes and there's initialisation that needs to be done in some cases. I could probably do it, but it's messy.


So all those quests I made where I start with stage 0, setstage(10) in the expectation that stage 10 would be fully initialialised - that was all a waste of time? Oh boy...

I take it a RegisterForSingleUpdate would do the job? Give the quest a chance to finish the fragments and finish setting up before coming back and advancing the quest?

I'm going off of memory of what the script system does and what SetStage does. Quests and scenes are not my area - I don't know exactly what part of the quest the scene is looking at to determine if it can start.

A RegisterForSingleUpdate would potentially let the start stage fragment finish running, if it was at the end of the fragment, so it's certainly worth a try.

It does tend to make sense if you think about it - the quest startup stage is kind of a chance for a script to make sure everything in the quest is ready to go before it is considered "started"

i think you should get around that by not start()ing it before setting the stage.

if you just SetStage, that should start the quest right at that stage like that was the starting stage (at least that's what i get from the wiki),

except if you have that "always start with this stage" checkbox checked for another one.

(just for the records and not trying to speak against registering for an update)

I just tried to post and was told I'd been blocked. Testing from another browser.

[edit]

In which case, I was going to say this: