When teleporting AI around the map, and changing their behaviour to CARELESS or SAFE, there is a clear fps drop, and it becomes worse and worse as you keep teleporting them. This doesn't seem to happen with any other behaviour (COMBAT, AWARE, STEALTH etc). See video (timestamped to where it gets really bad, keep an eye out on the fps hint in the top right corner). In the video I had CBA loaded, it's not the issue, the same exact thing happens in vanilla with no mods.
Description
Description
Details
Details
- Severity
- None
- Resolution
- Open
- Reproducibility
- Always
- Operating System
- Windows 10 x64
- Category
- Performance
Steps To Reproduce
Create an AI group, teleport them around while changing behaviour from CARELESS or SAFE to any other (or vice-versa), and notice the fps dropping.
Event Timeline
Comment Actions
In the video > https://www.youtube.com/watch?v=IXDaHrGk2ak&t=96s
It is pretty clear that the FPS drop is quite significant of -20/-40 FPSs...
Also if anything it should be the other way around because ai units in CARELESS or SAFE modes should be performing less checks compared to a unit in AWARE or COMBAT (Which are now maneuvering, flanking, firing, checking detected enemy position, searching for cover etc etc).
If this is confirmed to happen on all missions and not only in your particular mission setup then I hope devs can look into it and resolve it.
PS: Since the test happens in Malden and when moving Ai units around, I wonder if it could be related to the Ai units causing issues when near big rocks reported here: https://feedback.bistudio.com/T160213
Could be a separate issue thou...
Comment Actions
If this is confirm to happen on all missions and not only in your particular mission setup then I hope devs can look into it and resolve it.
My mission setup was nothing special, opening editor, placing a single soldier (player), and creating units at runtime (exactly like in the video). I'm able to reproduce this on any map, Altis, Stratis, even VR.
Comment Actions
If it happens in VR then you've isolated to issue to be completely and exclusively inside the Ai behaviour/FSM/Code.
Comment Actions
Ok this could to be perhaps related to the Ai not forgetting their old generated path? When teleported around the Ai will still try to device a path that uses their previous path point which is now very far away and that makes the process use a lot more resources. A solution could be that the setPos command always resets the Ai path which after being moved has to generate a completely new one (path) without considering their previous paths.
Still we can't discard that changing modes from AWARE to SAFE etc might also cause other FPS issues in addition to the issue I previously described.