Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2021.3.X, 2022.1.X
Votes
0
Found in
2020.3
2020.3.30f1
2021.3
2022.1
2022.2
Issue ID
1419924
Regression
No
Errors are thrown when changing Quality Level via code on HDRP
How to reproduce:
1. Open the user attached "HDRP postprocessing.zip" project
2. Open the SampleScene Scene found in the "Assets/Scenes" folder
3. Enter Play Mode
4. Press the 1, 2, or 0 number keys on your keyboard
Expected result: No errors
Actual result: "RTHandle.Initialize should only be called once before allocating any Render Texture..." is thrown
Reproducible with: 10.8.1, 10.9.0 (2020.3.33f1), 12.1.6 (2021.3.0f1), 13.1.8 (2022.1.0f1), 14.0.2 (2022.2.0a11)
Couldn't test with: 7.7.1 (2019.4.38f1) - Missing namespaces after downgrading
Note:
- Code used for the reproduction is dependent on HDRP so testing with URP is not possible
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
- Input from the "Backslash" key is not detected in the Web Player when using the Japanese 106/109 key keyboard
- High "Total" value of the "TerrainManager.CullAllTerrains" when generating terrain
- UI Layout rebuild triggered by a rounding error when using TextMesh Pro
- Sprite Shape Corners and Edges are invisible when a closed Sprite Shape is used
- Script icon Gizmos cause lag/performance issues in Scene view even when the Scene Camera is not pointed at Gizmos
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a15