Search Issue Tracker
By Design
Votes
0
Found in
2017.2.0a1
2017.3.0f3
Issue ID
1008138
Regression
Yes
Collider2D gizmo position does not match updated object’s transform position and lags behind by one frame
Steps to reproduce:
1. Open attached “Collider2DPosition.zip” Unity project
2. Open “Main” scene
3. Select “Collider2D” object in Hierarchy
4. Observe “Collider2D” object’s Box Collider 2D outline in Scene view
Expected results:
Collider2D gizmo always matches the position of the object
Actual results:
Collider2D gizmo position does not match the updated object’s transform position and lags behind by one frame
Reproduced in: 2018.2.0a2, 2018.1.0b9, 2017.3.1p3, 2017.2.2f1, 2017.2.0a1
Didn’t reproduce in: 2017.1.3p2, 2017.1.0a1
Regression introduced in: 2017.2.0a1
Note: Issue is present with every type of 2D collider components
By design:
This gizmo shows the real shape positions which aren't immediately changed when the transform changes but is actually updated during the simulation step.
Call Physics2D.SyncTransforms() to force synchronization in outside Play mode in script with [ExecuteInEditMode] attribute.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment