Interaction collider delayed while in physical locomotion

[shiftyscales]

Describe the bug?

The collider for interaction, e.g. a touch button is delayed a frame behind the user while in a physical locomotion. This issue does not occur in noclip.

This issue initially started at some point during the bepuv2 upgrade.

Relevant issues

Similar to #2906 but this issue has existed prior to it being changed, so there hasn't been a regression as a result of #2906.

To Reproduce

• Go to neosrec:///U-Shifty/R-23331563-b1e4-4c99-a597-33f67bea112a
• Move around while in physical locomotion
• Note that the laser breaks away from the collider and is delayed behind the visual (the laser can interact with the collider which is positioned where the visual was was one frame earlier.

Expected behavior

The collider and its visual should be in sync.

Log Files

No response

Screenshots

While moving to the left, the collider's position was to the right of the box, delayed in position.

How often does it happen?

Always

Does the bug persist after restarting Neos?

Yes

Neos Version Number

2021.9.6.614

What Platforms does this occur on?

Windows

Link to Reproduction Item/World

neosrec:///U-Shifty/R-23331563-b1e4-4c99-a597-33f67bea112a

Did this work before?

Yes

If it worked before, on which build?

Pre-bepuv2

Additional context

This was originally discovered in the JUMP worlds which utilize a HUD featuring a restart button. If aiming at this visual while falling, the user will see their laser drift upward sticking to the collider's delayed position as they gain speed, and if they try to aim where the button should be while falling they can't click it/need to aim up/above the position of the visual.

JUMP SP 1-1 is a good demonstration of this effect: neosrec:///G-PolyLogiX/R-bc774eec-3f0d-4848-bbfd-134c155ccd4c

Reporters

Shifty

[Frooxius]

How exactly is the collider positioned in this case? There's probably some order of operation issue.

[shiftyscales]

In this case, its using a slightly version of the previous world using the PositionAtUser component (changed the behavior so it follows head rotation as well so it's easier to demonstrate the issue occuring.

This has also occured with Logix handling the positioning as noticed by myself, and Ryuvi when using her NeoMeet panel.

[Dirko3000]

Have very often experienced that issue of getting biffed into low earth orbit by some weapon, but being unable to use my context menus at all to do anything due to the speed, leaving the respawn gesture being the only valid option other than waiting to begin falling downward, inevitably crossing the respawn point.