mirror of
https://github.com/TES3MP/openmw-tes3mp.git
synced 2025-02-20 19:39:41 +00:00
Don't run unstuck if there is no simulation running in async case.
In this case, the actor mPreviousPosition is not updated, so the actor position is interpolated between an old (stucked) position and the new (unstucked) position. The new position is most likely "stucked", so the unstuck code strikes again, making the actor "vibrates". That's exactly what the sync code path does, and it doesn't exhibit this behavior.
This commit is contained in:
parent
9eba086c34
commit
e37e5d4d16
1 changed files with 2 additions and 0 deletions
|
@ -173,6 +173,8 @@ namespace MWPhysics
|
|||
{
|
||||
if (mDeferAabbUpdate)
|
||||
updateAabbs();
|
||||
if (!mRemainingSteps)
|
||||
return;
|
||||
for (auto& data : mActorsFrameData)
|
||||
if (data.mActor.lock())
|
||||
{
|
||||
|
|
Loading…
Reference in a new issue