koobas.hobune.stream
What is PhysX "postIslandGen" and how can I reduce its impact on performance.
I believe it has something to do with the AI, given that the more Nav Mesh Agents I put down, the more CPU it drains, but I would like to allow for significantly more enemies then it currently allows for and this is bottle necking my performance.
if you are looking to have 30-40 enemies rushing to your player, then you may want to check for "flocking" behaviours or plugins. Having one enemy doing something and the others replicating that is easier on the cpu than having 30 enemies doing their own thing.
Alright don't worry about it, I figured it out and I am dumb. I am using pretty simple buildings, so I figured a mesh collider would be fine. It wasn't don't use mesh colliders kids.
The colliders, in terms of performance go: Sphere,Capsule,Box,$$anonymous$$esh (from fastest to slowest). Also, ticking on "convex" on the mesh collider component helps with speed.
Note: Large moving Trigger colliders can really push the postIslandGen to reduce performance. Possible solution switch the Trigger collider off and on at intervals or reduce or dynamically change their size.
@Arowx Have my babies. Thanking you isn't an option. The solution is so simple but it improved the number of AI I can have on screen from 100-200 to 1000+. I just set the trigger on for a single fixed update frame every couple of seconds and delay the toggle a random amount so every agent isn't turning on their collider in the same frame. So ya, thank you.
