I have some game events that use a node loop to repeat themselves.
I also tried using repeat event in the event interaction settings without the node loop in the game event settings.
Both give me the repeat results I'm looking for.
Which one is better for performance?
As far as my HUD goes, I have text that doesn't get updated, float variables, Status Value Numbers and Status Value Bars.
Would it be better for performance to have all status elements in one HUD, or should I divide each information and status element into it's own HUD?
I noticed a huge boost to the performance of my HUD'S when I disabled Show Shadow and Show Outline.
HUD performance really depends on which system you're using, e.g. legacy GUI has a constant, small performance cost and the new UI has higher cost when initializing and updating a UI, but no constant performance cost.
I can't really say if it's better to have a single HUD or multiple HUDs, it always depends on your game and how things are used. E.g. a single HUD is probably a bit better with performance, as it only uses 1 GUI box, but it needs to update everything in case something changes, while multiple HUDs have a small overhead through using multiple GUI boxes, but only need to update a smaller content.
Shadown and outline definitely impact performance, as they basically draw the text another time :)
If you're enjoying my products, updates and support, please consider supporting me on patreon.com!
I tried doing the single HUD and multiple HUDs in real time battles, and didn't really notice
performance differences . I did notice that when using multiple HUDs the batches number in the stats window was higher than the single HUD. Would more batches make any difference in performance?
As for the HUDs (or generally), less batches is always better.
If you're enjoying my products, updates and support, please consider supporting me on patreon.com!
If I use the wait for input fork node with it's wait time set to 0, should I still use a wait node for the loop?
Since there are safeguards, you can use loops without wait, but it just executes unneeded loops per frame with the same conditions, impacting your performance.
A Wait For Input node with a wait time of 0 wouldn't really be able to get any input, so you could just use a regular wait node instead :)
If you're enjoying my products, updates and support, please consider supporting me on patreon.com!