Search Issue Tracker
Fixed
Fixed in 6000.2.13f1
Votes
0
Found in
6000.2.11f1
Issue ID
UUM-125724
Regression
Yes
A specific Rigidbody GameObject breaks unpredictably when another Rigidbody GameObject is Destroyed or manipulated
Steps to reproduce:
1. Open the attached “IN-122033” project
2. Open the “Assets/Scene/Stunt.unity” Scene
3. Enter Play Mode
4. In the Game view, click the “Delete Bot” button
5. Observe the Game view
Expected result: The “Player” GameObject does not react to the event
Actual result: The “Player” GameObject breaks and flies off in an unpredictable direction
Reproducible with: 6000.2.0a10, 6000.2.11f1
Not reproducible with: 2023.3.0a5, 6000.0.61f1, 6000.2.0a9, 6000.3.0b9, 6000.4.0a4
Reproducible on: macOS 26.0.1 Standalone Player
Reproducible with these devices:
VLNQA00641 - Google Pixel 9 (Pixel 9), CPU: -, GPU: Mali-G715, OS: 15
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
Add comment