Search Issue Tracker
By Design
Votes
16
Found in
6000.0.47f1
6000.1.1f1
6000.2.0a10
Issue ID
UUM-104843
Regression
Yes
Warning “CommandBuffer: built-in render texture type 3 not found while executing (SetRenderTarget depth buffer)“ is present when opening a specific URP project
Reproduction steps:
1. Open the attached project "ReproProj"
2. Observe the Console
Expected result: No Warnings exist
Actual result: Warning “CommandBuffer: built-in render texture type 3 not found while executing (SetRenderTarget depth buffer)“ is present
Reproducible with: 6000.2.0a9, 6000.0.47f1, 6000.1.1f1, 6000.2.0a10
Not reproducible with: 2022.3.62f1, 6000.2.0a8
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Notes:
- CQA could not reproduce on a new URP project
- Reproducible with DX11 and DX12
- User mentioned reproduction with a new URP project
Comments (7)
-
Tnewav
Jul 13, 2025 21:49
It's probably the main camera.... Play with the main camera settings..... Turn from base... To overlay should work..... Then back to base if you want base.......... and turn sky box ... Options in main camera settings to color.... Should work.... Worked for me
-
xtilly5000
Jul 12, 2025 07:35
-
xtilly5000
Jul 12, 2025 07:22
Reproducible with 6000.2.0b7 and 6000.2.0b8 as well, caused by render graph (why does Gizmo rendering require depth buffers, anyways?)
warning thrown in com.unity.render-pipelines.universal@0ace31fce978 from ScriptableRenderContext:Submit() at Runtime/UniversalRenderPipeline.cs:893 (UniversalRenderPipeline:RenderSingleCamera)
-
Delcasda
Jul 09, 2025 01:17
Reproducible with 6000.1.10f1 and I confirm that disabling Gizmos on Game tab makes the error go away
-
xtilly5000
Jun 29, 2025 22:54
Reproducible with 6000.0.51f1 and 6000.0.47f1 when using URP and the new Render Graph API in an empty project while the Game window renders new frames with Gizmos enabled.
If the game window is hidden or gizmos are disabled the warning isn't shown
(Disabling render graph API by using URP compatibility mode in Edit > Projects Settings > Graphics > Graphics > Render Graph fixes the issue)
-
iALEXiii
May 25, 2025 16:32
I also tried 6000.0.49, 6000.1.0f1, 6000.1.4f1
and then even the beta version: 6000.2.0b2.
Problem is there in every version as said earlier.I found another one regarding similar warning:
https://issuetracker.unity3d.com/issues/urp-commandbuffer-built-in-render-texture-type-3-not-found-while-executing-warning-is-thrown-when-game-view-is-open-and-opengl-is-used -
Federfunk
May 16, 2025 02:31
I am able to reproduce this bug in 6000.0.47, 6000.0.48, 6000.0.49, and all versions of 6000.1.x.
Just create a new URP project and enable gizmos within game view.
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
Thanks for reporting your issue.
What’s happening:
- We recently added in the Unity engine an error message to warn that drawing gizmos within a render pass is not allowed, as specific actions like texture loading within a render pass can trigger crashes.
- At the same time, URP was updated to fix its implementation, which previously triggered the same error. The fix is in commit e3e5d668605db7bc31ac7bb0ded0def526f03b3b (https://github.com/Unity-Technologies/Graphics/pull/8137/commits/e3e5d668605db7bc31ac7bb0ded0def526f03b3b).
- You’re using a custom URP that doesn’t include this commit, together with an engine that enforces the rule, hence the error being visible in your Editor.
How to resolve:
- Cherry-pick e3e5d668605db7bc31ac7bb0ded0def526f03b3b (link above) into your custom URP package and rebuild/update URP.
- After aligning URP with the engine, the error will no longer occur.
We will close the issue. Please reopen it if cherry-picking the commit doesn't fix it.