Search Issue Tracker
Won't Fix
Won't Fix in 2022.3.X
Votes
0
Found in
2022.3.2f1
Issue ID
UUM-45658
Regression
No
SetGlobalFloat always sets the value to 0 on specific AMD GPUs when entering the Play Mode
Reproduction steps:
1. Open the attached project “AMD_Scene”
2. Open Scene “Assets/Scenes/StaticSceneLoader.unity”
3. Enter the Play Mode
4. Observe the Scene view
Expected result: The Scene view has a visible skybox with green > red gradient
Actual result: The Skybox appears for one frame before subsequently drawing black
Reproducible with: 2022.3.2f1
Reproducible on: Windows + Radeon RX 580 Series; R9 390
Note: Reproduces in the Player
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
- After converting a Built-in project to URP render texture related errors are spammed that can lead to Game view being rendered on top of Scene view
- UI Builder slider value lags and stutters when sliding/modifying certain property values
- "Reset UI Builder Layout" functionality inconsistently changes Canva Size when "Match Game View" is enabled/disabled
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
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.