Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
13.1.2
Issue ID
1391529
Regression
Yes
Frames are not cleared when HDR, MSAA, Opaque Texture and Depth Texture are off and Post Processing is disabled
Reproduction steps:
1. Open the user's attached project
2. Enter Play mode
3. Move with WASD keys
Expected result: Frames are cleared
Actual result: Frames are not cleared
Reproducible with: 13.1.2 (2022.2.0a1), 13.1.3 (2022.1.0b2),
Not reproducible with: 7.7.1 (2019.4.34f1), 10.8.1 (2020.3.26f1), 12.1.3 (2021.2.8f1), 13.1.1 (2022.1.0a16)
Note: Enabling any one of HDR, MSAA, Opaque Texture, Depth Texture, or Post Processing will cause the frames to be cleared again
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
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
This is a duplicate of issue #1384429