How to prevent systems from updating multiple times at start

At startup PlayerLoop is called multiple times, and Systems are called multiple times as well. This makes it hard to deduce the latency of systems. Is there a way to prevent multiple updates, or figure out the running time of systems?

 

Is the any reason, why you are concerned about startup delay? Your more important is system runtime, when game is already running.

Maind, You may be needles needing check / profile in built, rather in editor.

 

I have a monobehaviour that tests the system in the Start() function, but now that you've mentioned it it might be better to have a coroutine that waits a second or two before executing the test. Or maybe I should just write editor-mode unit tests.

 

However, ECS systems run independently from MonoBehaviour. Unless you trigger it there.
If you want profile / test system, you would be better do it in corresponding system.

 

I can't replicate this.

My systems only update once during the initial player loop update.



It seems like only the MonoBehaviour loop gets called multiple times.