Search Issue Tracker
Fixed
Fixed in 6000.0.1f1, future release
Votes
0
Found in
2023.3.0a3
6000.0.0b11
Issue ID
UUM-15955
Regression
No
Gizmo does not update correctly when moving a Box Collider 2D and Time Scale is less than 1
Reproduction steps:
1. Open the user’s attached Project
2. Open the “Asset/SampleScene” Scene
3. Click Edit > Project Settings > Time
4. Observe the value of the TimeScale
5. In the Hierarchy Window select the “Square” GameObject
7. In the Scene View, enable Gizmos and move the “Square” GameObject
8. Observe the Collider movement in the Scene View
Expected result: Collider 2D Gizmos moves with the same speed as GameObject
Actual result: Collider 2D doesn’t move as GameObject
Reproducible with: 2020.3.40f1, 2021.3.11f1, 2022.1.19f1, 2022.2.0b9, 2023.1.0a13
Reproducible on: Intel macOS 12.6
Note: When TimeScale is not equal to 1 all none 2D Colliders move correctly with the GameObject, but 2D Colliders only do the same when TimeScale is set to 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
- 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 (fix version 6000.0.1f1):
Fix for this issue is available on Unity 6000.0.1f1 and above