Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.26f1
2022.3.1f1
Issue ID
UUM-37955
Regression
No
Transform Component is not accessible inside the Player when RuntimeInitializeOnLoadMethod is used
Reproduction steps:
1. Open the attached “ASDQWE” project
2. Open the “Assets/Scenes/SamplScene.unity” Scene
3. Enter the Play Mode
4. In the Game View, observe the text and the pink triangle Sprite
5. Exit the Play Mode
6. Build the Player (File > Build And Run)
7. Observe the Player
Expected result: A pink triangle Sprite and the text “hello (0.00, 0.00, 0.00)” are visible in both the Player and the Game View
Actual result: An error message “something broke at: …” is visible in the Player instead, resulting in a discrepancy between the Game View
Reproducible with: 2021.3.26f1, 2022.3.1f1, 2023.1.0a22
Not reproducible with: 2023.2.0a16
Fixed in: 2023.1.0a23
Reproducible on: Intel MacOS 13.3.1
Note: In the 2020.3.48f1 and 2021.3.26f1, and 2022.2.21f1 versions, the triangle is not visible inside the Game View
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
- NullReferenceException is thrown when assigning an Object to a custom DebugUI.ObjectField in Rendering Debugger
- Crash on D3D12CommonShader::ApplyGpuProgram when attaching material which samples "_UnityFBInput0" to "Full Screen Pass Renderer Feature" Component
- SpeedTree meshes and objects count differs when comparing the numbers in the Player with the Editor
- Model and Prefab Preview icons are not updated after upgrading associated Materials to URP
- Game view is rendered white when viewing the Editor with HDR display and Post Proccesing is enabled on the Main Camera with 2D URP
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.