Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.30f1
2022.3.9f1
2023.1.13f1
2023.2.0b9
2023.3.0a5
Issue ID
UUM-48977
Regression
No
Wrong transform is returned when accessing prefab’s transform by using “transform.root” if “transform.parent” has already returned the desired transform reference
How to reproduce:
1. Open the attached “SnappingGameObject.zip” project
2. Open “SampleScene” Scene (Assets > Scenes)
3. Enter Play Mode
4. Press “1” on keyboard
5. Using WASD keys, move near the edge of the platform
6. Observe the result
Expected result: Capsule GameObject snaps to the round platforms
Actual result: Capsule GameObject doesn’t snap to the round platforms
Reproducible with: 2021.3.30f1, 2022.3.9f1, 2023.1.13f1, 2023.2.0b9, 2023.3.0a5
Reproduced on: macOS 13.4.1 (Intel)
Not reproducible on: No other environment tested
Notes:
- reproducible in the Editor and Standalone Player (macOS)
- not reproducible if changing the “PlayerTowerHandler” script’s 70th line “hitInfo.transform.root” with “hitInfo.transform.parent”
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
- 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
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.