Search Issue Tracker
Active
Under Consideration for 6000.6.X
Votes
0
Found in
6000.0.69f1
6000.3.11f1
6000.4.0b11
6000.5.0a8
6000.6.0a1
Issue ID
UUM-136596
Regression
No
Material is not blitted onto the screen when the Camera is rendering to a Render Texture
How to reproduce:
- Open the “BlitToScreenHDRP.zip“ project
- Open the “OutdoorsScene“ Scene
- Open Window → Analysis → Frame Debugger
- Enable the Frame Debugger
- Observe the Frame Debugger and the Game view
Actual result: Game view is black (not rendering anything), and Frame Debugger Output is blank (same color as the background)
Expected result: Game view and the Frame Debugger Output are red
Reproducible in: 2023.1.0a1, 6000.0.70f1, 6000.3.11f1, 6000.4.0b12, 6000.5.0a8
Reproduced on: Windows 11 Pro (25H2)
Not reproduced on: No other environment tested
Notes:
- Only reproducible while the Camera is rendering to a Render Texture
- Does not reproduce on Windows Standalone Build
- Not reproducible in URP
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
Add comment