Search Issue Tracker
Fixed in 5.4.0
Votes
0
Found in
5.4.0b9
Issue ID
778870
Regression
Yes
If scaling GO using Vector3 with zero z or Vector2 then its child Rigidbody will have its position multiplied by that vector
Steps to reproduce:
1. Open attached project
2. Project has two scenes: "BugScene" and "NormalScene". Difference is that sprites in "BugScene" use Rigidbody2D while sprites in "NormalScene" do not
3. Open "BugScene"
4. In hierarchy, expand "RootObject" and select "Child02"
5. In inspector, notice that it has Rigidbody2D. Also, transform X = Y = 2
6. Run scene and in game view click "Set Scale" button
7. Notice that sprite is scaled and moved to X = Y = 6. Also, if sprite is selected notice that BoxCollider2D and actual sprite locations differ
Workaround: Use Vector3 with Z = 1
Not reproducible: 5.3.4f1
Reproduced with:
5.4.0b1 (if sprite is moved in scene view then BoxCollider2D and sprite location becomes the same),
5.4.0b10 (BoxCollider2D and sprite location is same only when transform X = Y = 0)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Memory leak when a lot of UI elements are spawned and despawned
- Warnings are not logged in the Console window when using external code analyzers
- Errors “TLS Allocator ALLOC_TEMP_TLS, underlying allocator ALLOC_TEMP_MAIN has unfreed allocations, size 288“ appear constantly when Prefab is open
- Crash on PPtr<Shader>::operator or NullException errors spammed in console when calling Dispose() on null GraphicsBuffer with baked Reflection Probes
- “EndRenderPass: Not inside a Renderpass” and other Render Graph errors in the Player when Render Graph is enabled and Overlay UI is used
Add comment