Search Issue Tracker
Won't Fix
Won't Fix in 2022.3.X
Votes
0
Found in
2022.3.55f1
Issue ID
UUM-96355
Regression
No
Silent crash when opening a project with a HD Dynamic Resolution Component and a UHD Graphics card
How to reproduce:
1. Make sure the only graphics card enabled is the integrated UHD
2. Open the project “IN-93529_DR_Cloud_issue”
3. Observe the crash
Reproducible with: 2022.3.55f1
Not reproducible with: 6000.0.36f1, 6000.1.0b4, 6000.2.0a1
Reproducible on: Windows 11 (10.0.26100 Build 26100), specifically integrated UHD Graphics card
Not reproducible on: Mac (Big Sur 12.5.1) UHD Graphics card
Notes:
- Potentially crashes with other low tier intel graphics cards such as Intel Iris Xe, but unable to test it
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.