What is the recommended method of trying to do a looping check like this?
Attempting it results in a pretty noticeable lag, from checking every .1 seconds. Changing it to a check every 1s helps alleviate that, but also means that there's often a 1s delay in the result instead of instant. Is there a better way to achieve it?
Maybe it'd be good to have a variety of 'Wait For' steps similar to the Wait For Input step? They'd be pretty handy for stuff like this.
- Wait for Status Value Change (Plus an optional Check) - Wait for Status Effect Change (Plus an optional Check) - Wait for Variable Change (Plus an optional Check) etc.
Unless you've got hundreds of status checks in the Check Status node, this shouldn't really cause any noticable performance drops ...
Please consider rating/reviewing my products on the Asset Store (hopefully positively), as that helps tremendously with getting found. If you're enjoying my products, updates and support, please consider supporting me on patreon.com!
I thought that as well! I tried a few more times; and I realized what was causing the editor lag; the event object was selected and showing in the inspector while in play mode, and had both ORK and Makinom object variable components on it, one of which was a timer variable. Deselecting the object got rid of the lag in the editor.
Oh, yeah, the constant editor updates can be quite demanding ...
Please consider rating/reviewing my products on the Asset Store (hopefully positively), as that helps tremendously with getting found. If you're enjoying my products, updates and support, please consider supporting me on patreon.com!
If you're enjoying my products, updates and support, please consider supporting me on patreon.com!
---------------------------------------
Personal Twitter: https://twitter.com/AMO_Crate
I make RFI! https://twitter.com/NootboxGames
If you're enjoying my products, updates and support, please consider supporting me on patreon.com!