Search Issue Tracker
Fixed in 6000.0.15f1
Fixed in 6000.0.X, 7000.0.0a8, future release
Votes
0
Found in
6000.0.9f1
Issue ID
UUM-74914
Regression
Yes
[URP] Warnings "CommandBuffer: temporary render texture not found while executing" is constantly logged when any of the Lighting Debug Views are active in the Rendering Debugger
Steps to reproduce:
- Create a URP Project
- Open Game View
- Open the Rendering Debugger (Window > Analysis > Rendering Debugger)
- Select "Lighting" and choose any of the debug options from any of the dropdown menus
Actual results: Warning "CommandBuffer: temporary render texture not found while executing (SetGlobalTexture)
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)" is constantly logged in the Console and cannot be cleared when any of the debug options are active for Lighting
Expected results: No Warnings are logged when using debug views
Reproducible with versions: 2023.3.0b1, 6000.0.9f1
Not reproducible with versions: 2021.3.40f1, 2022.3.36f1, 2023.2.20f1, 2023.3.0a19
Tested on (OS): Windows 11, macOS Sonoma M1
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