Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
11
Found in
6000.0.55f1
6000.2.0f1
6000.3.0a4
6000.4.0a1
Issue ID
UUM-113920
Regression
No
Prismatic ArticulationBody moves in opposite direction when using targetVelocity
Reproduction steps:
1. Open the attached “IN-110956.zip” project
2. Open the “SampleScene”
3. Enter Play mode
4. Observe the Cube on the right
Expected result: The Cube moves upwards towards the +1 limit
Actual result: The Cube moves downwards towards the -1 limit
Reproducible with: 2023.1.0b1, 6000.0.55f1, 6000.2.0f1, 6000.3.0a4
Reproducible on: Windows 10 (user reported), Windows 11
Not reproducible on: No other environment tested
Notes:
- Position-based control (using target + stiffness) works correctly in the expected direction
- Physics Debug window shows inverted velocity values (e.g., targetVelocity = +1 → actual velocity = -1).
- Issue persists regardless of Damping values (tested from 1 to 1e+25)
Comments (1)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
vlad061201
Aug 12, 2025 06:35
Also reproducible in 2021.3.26f1