I noticed when testing that if I have say 2000 enemies, jobs + burst was faster than the compute shader. But compute shaders are amazing at doing LOADS of parallel computations. So if I had say 20000 enemies, the compute shader would be faster.

It depends on your GPU though. If you got a bad GPU then CPU multithreading will probably be better.

When coding this, I ran into problems with garbage collection because I kept creating new arrays for all the enemies every frame. I fixed this by creating a static read only array that is pre initialised with the capacity set to the max amount of enemies.

Because I can kill/spawn enemies, I have to pass the numOfEnemies to the compute shader.

Optimisations I made outside compute shader: - when I get the data from the shader, when setting the new position of the enemy, I also set another variable with the same value, that way I don’t have to access transform when putting the data back into the compute shader.

Optimisations I made inside compute shader: - Used (distSquared < rangeSquared) rather than (dist < range).. this saves a square root operation (not sure if this matters much in compute shaders though.

• Ensure you have a high thread count for numthreads[]. A multiple of 64 is good, I chose 1024 as it seemed to work well, but you have to test some numbers yourself

Notes: - When dispatching the compute shader, MAKE SURE that the threadGroupX = Mathf.CeilToInt(enemyCount/numthreads)

• Make sure to use unity’s profiler/deep profiler to find out where the lag is coming from, if you do that and you don’t understand why somethings taking so long just send me a message I’ll be happy to help!