Search Issue Tracker
Won't Fix
Won't Fix in 2021.3.X
Votes
0
Found in
2021.3.38f1
Issue ID
UUM-70749
Regression
Yes
The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
How to reproduce:
1. Open the “FrameDebuggerTest.zip“ project
2. Open the “main“ Scene
3. Enter the Play Mode
4. Open and Enable the Frame Debug Window
5. Observe the Game view
Expected results: The Resolution Material is applied on a Render Texture displayed in the Game view
Actual results: The Game view is blank
Reproducible in: 2021.3.22f1, 2021.3.38f1
Not reproducible in: 2021.3.21f1, 2022.3.27f1, 2023.2.20f1, 6000.0.0f1
Reproduced on: Windows 11 Pro (23H2)
Not reproduced on: No other environment tested
Note: The issue is not reproducible if the "Use MSAA" or "Bind" checkboxes on the “Main Camera” GameObject in the “FrameDebuggerTest” script are disabled before entering Play Mode
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:
The issue seems to only be reproducible in version 21.3. It appears to have been resolved in 22.3 and is not an issue in Unity 6. Please consider upgrading to a more current version of Unity.
Resolution Note (2021.3.X):
The issue seems to only be reproducible in version 21.3. It appears to have been resolved in 22.3 and is not an issue in Unity 6. Please consider upgrading to a more current version of Unity.