Adaptive Timestepping causing PrismaticConstraint not to reach target lower than current position with low LinearResponsiveness

[ShrekWasMyIdea]

Reproduction Steps

This bug has just started happening today and is game-breaking for one of my games that relies on PrismaticConstraints reaching their targets reliably. Up until now this has worked without issue.

1. Create a basic PrismaticConstraint elevator with 2 parts and a LinearResponsiveness of 5
2. Set a lower limit on the constraint, and set the target to be above this
3. Run the game, and set the target position to be lower than its current value
4. Observe that the constraint stops higher than the target. (For example, setting a lower limit at 0 and going from a target of 10 to 2, the constraint stops at around 2.7)

PrismaticBugRepro.rbxl (38.6 KB)

Expected Behavior

I expect the constraint to stop at the target

Actual Behavior

The constraint stops higher than the target

Workaround

Switching to Fixed timestepping resolved this issue

Issue Area: Engine
Issue Type: Other
Impact: High
Frequency: Constantly
Date First Experienced: 2023-03-15 20:03:00 (+00:00)

[Hajimalago]

We reverted the flag that was suspected to cause the issue. Can you let is know if the issue is resolved yet?

[ShrekWasMyIdea]

Yes the issue appears to be resolved. Thank you!

[Hajimalago]

Sorry for the bad experience. We’ll fix the issue before we re-enable the flag and report back to you.