Hi, been checking the profiler since there’s a nasty spike when the game reaches a certain point. I see that the coroutines reach 258 from 0. I don’t have coroutines here but i did notice some for loops. Are these for loops being counted as coroutines in the profiler?
A coroutine is only a coroutine if you specify it as one, it will end as locking code otherwise which naturally will cause spikes in the profiler because while the loop runs, nothing else in the application can run at all
So that roughly means that its the for loops that are causing the spikes right?
Edit.
I tihnk the main culprit is the Instantiate code inside the double for loops.
Yeah instantiate in such a loop will definitely not make it better at all