Waiting and Parallel Processes

[King Moogle]

Hey, all,

I've got a quick question for you. If I have a parallel process event that's configured to...

1. Turn on Switch X
2. Wait for 30
3. Turn off Switch X

And I have a second event as a parallel process that is cued by Switch X, will it continue to check during the 30 frames, or only for the split-frame between the first and second lines?

Thanks!

 

[Deathbreak]

You mean that the left hand drop down box is set to check for that? Ya, the second it turns on that other event happens.

EDIT- It.. um... checks evrey second. It will lag your game really fast if you're not careful.

 

[King Moogle]

Alright, I simply wasn't sure if Waiting put Parallel Processes on hold as well, thanks.

 

[Zeriab]

Waiting does put the parallel process on hold.
After 30 frames it will turn off Switch X.
The wait will not hold the second event.
An event that is waiting doesn't really use many resources. It should not make your game lag. I don't know about the second event, that might do, though you can always put a few 1-frame waits in to delay further execution to next frame.

In case you are playing around with common events: Note that parallel common event reset when you transfer to a new map.

 

[Deltree]

I guess it depends on context, but remember that parallel process events loop, so immediately after the switch is shut off, it will jump back to line 1 and turn it back on before waiting again.  So, don't forget either another delay after the switch is turned off, or some sort of termination statement so it doesn't repeat.

Unless you want it to behave that way, that is.