Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
3
Found in
2021.3.16f1
2022.1.24f1
2023.1.0a25
2023.2.0a7
Issue ID
UUM-22718
Regression
Yes
[HDRP] Built project screen flickers when using HDRP
Reproduction steps:
1. Open the attached project “FlickerRepro”
2. Build the project
3. Run the built project
4. Look at the built project
Expected result: There are no artifacts on the screen
Actual result: The screen is flickering at random intervals
Reproducible with: 12.1.8 (2021.3.16f1), 13.1.9 (2022.1.24f1), 15.0.3 (2023.1.0a25)
Not reproducible with: 10.10.1 (2020.3.44f1)
Couldn’t test with: 14.0.4 (2022.2.2f1) - Unity crashes when launching the project
Reproducible on: macOS 13.1 (Intel)
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
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.
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 (2023.2.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.
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.