You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if this is due to high speed tracking or not.
The test project included features a free falling rigidbody and the camera tracking it; it's possible to see some "jumps" that appear randomly, in addition to some sudden changes in velocity that shouldn't happen due to not having anything to stop the body's fall.
In addition, the source code ported to v3 is included as well.
However, even with this fix, it's not an exact solution (especially in varying framerates like in the editor sandbox) and shouldn't be relied on for backtracking object positions to previous frames or similar calculations.
Not 100% sure, but I think varying framerates might be what causes this, as I can reproduce the behavior you described in the editor, but not in a VSynced test run in the launcher.
From the launcher it looks way better; also I automatically add a VelocityTracker to the Camera (if needed) to use its smoothed Velocity calculations.
For the moment I believe this can be put aside, just leaving it open to remind myself to look at it once Duality v3 is stable.
SirePi
added
the
🔼 v3
The issue is here, but is relative to v3. To be assesed again once Duality v3 is released
label
Mar 14, 2018
Not sure if this is due to high speed tracking or not.
The test project included features a free falling rigidbody and the camera tracking it; it's possible to see some "jumps" that appear randomly, in addition to some sudden changes in velocity that shouldn't happen due to not having anything to stop the body's fall.
In addition, the source code ported to v3 is included as well.
CameramanTest.zip
duality-companion-v3.zip
The text was updated successfully, but these errors were encountered: