Thank you for clarifying that Ashley.
Is it possible you can describe the process on how Event Triggers
and Functions
are handled? I know they are skipped, which is great, but to what extent?
I've been experimenting on a new optimization technique I've been doing on an existing mobile project, and I've found that moving all utility functions to JavaScript has dropped my mobile CPU usage from +-60% to +-32%, and removed stuttering janks which I've only recently discovered how to specifically solve.
Now, I only use the event sheet for every ticks and event listeners, which makes the project feel lightweight.
However, amazingly, I've found that moving functions to a non-included event sheet does the similar performance improvement.
I previously mistakenly thought the performance issue was the GPU, since the CPU usage is not that high and I've not seen a way to profile the GPU usage, and lowering the fill-rate was improving the experience so it easily disguised the issue.
Fortunately, it seems it was just the accumulated event count causing the CPU usage, which is understandable given the limited performance capability of mobile CPUs.
I would appreciate if you could explain here how the event triggers and functions are skipped, so that we can better understand how we can make better use of the event sheet.
Thank you!