lindenkron
Member
If you leave out the "scene changed" condition and just use the "current scene is ..." part it should start your actions as soon as the transition begins.
I assume you added the "scene changed" part to avoid endlessly triggering these actions while the caster scene is active.
I would instead recommend adding a time restriction to the "current scene is" condition by clicking on the small clock icon.
So far I had not observed any memory leaks on my end.
If you are certain that the scene switcher is causing these please export your current scene switcher settings and I will try to reproduce the leak on my end.
Hope that helps!
Super helpful!
It wasn't immediately clear that 'For at most' was an indicator of how long it could trigger for; it sounded like "If scene XXX for at most 1 seconds" would indicate how long you were on the scene for; not how long the If statement would trigger for. Glad to know this functionality is in there, that's why I had previous scene change on indeed :)
I don't think the leaks are on your end either - just mentioned it incase you we're like "yes I'm aware and looking into it". If you don't think there's any; I don't think it's your plugin either!
The version you linked previously have worked well so far; not had any issues and using the timer now avoids the delay issue I had before!
Thanks!