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
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
- [Android] Light2D visuals stacking over frames when using RenderGraph
This is a duplicate of issue #1384429