 |
r11281. Fixed FPS-dependent movement estimates in MovementSubsystem::CheckBlocked. Origin and frame index were recorded in 32-entry ring buffer, so that we could compute velocity using them. I have no idea why there are 32 entries, since the code only every references the last 2 frames =) but OK. The velocity is computed as (Orig[i+1] - Orig[i]) / (Frame[i+1] - Frame[i]), and it basically "movement per frame". It is then compared with hardcoded constants like 0.1 and 0.3 to check if AI movement has stalled due to some kind of block. If this is true, then AI starts some kind of evasion manoeuvre. The problem is that the velocity is FPS-dependent, and on high FPS is falls unexpectedly low. As the result, slowly moving AI becomes blocked constantly, and just circles around trying to evade nothing. Instead of tracking frame numbers, now we track gameplay time. We compute velocity as (Orig[i+1] - Orig[i]) / (Time[i+1] - Time[i]) * 16, which is basically "movement per 16 ms of time". This should be the same velocity that is there in 60 FPS move / capped FPS, so the thresholds which used to work back then should work fine now. Also I refactored the velocity computation. There are two methods: velocity by last two moment in history, and velocity by curent state and last moment in history. I unified these two methods and replaced the code in CheckBlocked with a call to GetPrevTraveled. The horses move find for me now, even with 300 and 1000 FPS. Normal missions seems to work fine too. |
- Anonymous
