Search Issue Tracker

In Progress

Fixed in 6000.0.23f1

Under Consideration for 6000.1.X

Votes

12

Found in

6000.0.8f1

6000.1.0a7

7000.0.0a1

Issue ID

UUM-74509

Regression

Yes

[URP][OpenGL] CommandBuffer: built-in render texture type 3 not found while executing warning is thrown when Game view is open and OpenGL is used

--

-

*Steps to reproduce:*

1. Create a new URP 3D template project

2. Focus the Game view

3. Observe the Console

*Actual results:* CommandBuffer warning is thrown

*Expected results:* No errors or warnings are thrown

*Reproducible with versions:* 2023.3. 0a18, 6000.0.8f1

*Not reproducible with versions:* 2021.3.39f1, 2022.3.34f1, 2023.3.0a17

*Tested on (OS):* Ubuntu 22.04, Ubuntu 24.04

*Notes:*
* The issue does not reproduce when Vulkan API is used
* The issue does not reproduce when using a built-in pipeline
* Full warning:
** CommandBuffer: built-in render texture type 3 not found while executing  (SetRenderTarget depth buffer)
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)

Comments (5)

  1. alexanderameye

    Oct 16, 2024 21:12

    Also getting this on Unity 6000.0.21f1 on an OpenGL ES 3.0 build in the browser (but not in the editor).

  2. Artemis152

    Sep 21, 2024 20:56

    Happening for me as well, on 6000.0.18f1 using OpenGL 4.5 renderer. Thankfully I don't need OGL anymore for this project.

  3. ohsalmeron

    Jul 30, 2024 02:26

    same warning here on Unity 6000.0.12f1 - Archlinux - OpenGL 4.5

    CommandBuffer: built-in render texture type 3 not found while executing (SetRenderTarget depth buffer)
    UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)

  4. toddw

    Jul 18, 2024 08:18

    Just realized 2023.3.0a17 is an alpha, that's why we're still stuck on 2023.2.20f1.

  5. toddw

    Jul 18, 2024 08:15

    My users are getting a crash with this error in their log of my demo built on 2023.2.20f1. Where is 2023.3.0a17, it's not available in the download archive?? I can't upgrade to Unity 6 because the editor crashes immediately upon open after upgrade. This started happening on Unity 6000.0.7f1 and is still happening in 6000.0.10f1.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.