Hi, we are using much less on screen than 500.
The problem can’t be seen on your video because you only use one nav agent. I dont speak about agents in the sense of pawns/characters registered to the crowd controller. I speak of nav agents. You can define different nav agents, which use different nav meshes. This is usefull for different size of characters. For example very small characters which can go where medium characters can’t go and large characters, which can’t go where mediums go. You only use one nav agent. The detour controller only ever uses one nav agent. Agents which use a different nav agent can still be obstacles but can’t be part of the controlled crowd and if they are registered as such, can’t move at all. You can test that out by creating a second nav agent in navigation settings. For example a larger one and make a character with larger capsule, which will pick the new nav agent.
Only thing to workaround it is to derive from detour crowd controller and expose properties to blueprint or change in c++ to make it register as obstacle only. But then bigger characters will not avoid smaller characters. Only the smaller avoid the bigger ones.
Root of the problem is that the detour crowd controller only ever supports a single nav agent.