Search Issue Tracker
Fixed
Fixed in 6000.0.68f1, 6000.3.9f1, 6000.4.X, 6000.5.0a7
Votes
14
Found in
6000.0.55f1
6000.2.0f1
6000.3.0a4
6000.4.0a1
6000.5.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)
-
vlad061201
Aug 12, 2025 06:35
Also reproducible in 2021.3.26f1
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Fixed in 6000.5.0a7
Resolution Note (fix version 6000.5.0a7):
Fixed in 6000.5.0a7
Resolution Note (fix version 6000.4):
Fixed in 6000.4.0b10
Resolution Note (fix version 6000.3.9f1):
Fixed in 6000.3.9f1
Resolution Note (fix version 6000.0.68f1):
Fixed in 6000.0.68f1