Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
0
Found in
6000.0.66f1
6000.3.4f1
6000.4.0b5
6000.5.0a5
Issue ID
UUM-134022
Regression
No
Some of the Rigidbody2D properties cannot be set after disabling the GameObject on the same frame
How to reproduce:
1. Open the “IN-133881.zip“ project
2. Open the “SampleScene“
3. Enter Play Mode
4. Press the Spacebar key
5. Observe the Console
Actual result: All asserts fail, all logs show zero values
Expected result: All asserts pass, all logs show non-zero values
Reproducible in: 2023.1.0a1, 6000.0.67f1, 6000.3.7f1, 6000.4.0b7, 6000.5.0a6
Reproduced on: Windows 11 Pro (25H2)
Not reproduced on: No other environment tested
Notes:
- User states that this problem occurs on (3D) Rigidbody as well, but this was not observed locally
- Only reproducible if the properties are changed on the same frame as the GameObject is disabled
- List of the affected properties (observed locally):
-- linearVelocity
-- angularVelocity
-- intertia
-- position
-- rotation
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor hangs when a huge mesh is used for CanvasRenderer
- ChildSafetyHandles grow indefinitely when repeatedly creating and disposing NativeLists with a long‑lived custom allocator
- My Assets in Package Manager appear empty when the search is cleared and the tab is switched
- Test Shader appears twice in Material Shader selection menu
- "CustomPass.injectionPoint" returns "AfterPostProcess" when a global CustomPass is registered with "BeforeRendering" in HDRP
Add comment