Search Issue Tracker
Won't Fix
Won't Fix in 2022.3.X
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
- 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:
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.
Resolution Note (2022.3.X):
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.