I know MieszkoZ has created a separate AIController class for DetourCrowds which BP users can use in place of the default one to enable DetourCrowds functionality (in lieu of changing the default components, which is something BP users can’t do).
So I did this, and it worked fine, but then I realized something:
When using this AI controller, if told to “move to Actor”, it uses the old buggy behavior of getting the actor’s location once and moving to IT even after said actor has moved, rather than updating its movement in real-time to reach the desired actor. This happens using both the AIMoveTo node in BPs (via a custom BT event) and using the built-in BT “Move To” command (which I imagine just fires the same thing).
I know that at one point this was a known bug with AIMoveTo, and a fix was committed, but it appears that said fix was only committed for the standard AIController class, rather than the DetourCrowds variant provided?
Just an FYI, I know that the DetourCrowds variant AI was a workaround for BP users since we can’t modify default components and a proper Avoidance-Method-Switching thing isn’t exposed yet to BP, so there may not be much desire to fix this, but for us BP users who would like to work with DetourCrowds rather than RVOAvoidance it’s kind of a headache.