[URP][OpenGL] CommandBuffer: built-in render texture type 3 not found while executing warning is thrown when Game view is open and OpenGL i... (#4415)

Issue Tracker
1

Topic automatically created to discuss [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

2

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.

3

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

4

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&)

5

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

6

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

7

Started getting this in 6000.1.0f1 when I added a Debug.DrawLine. Works fine until I put in the DrawLine.

8

Only happens when I try to enable the gizmos in the game view with that DrawLine I mentioned.

9

Sorry. I have to revise my previous statements. Even without the Debug.DrawLine it happens if I try to enable Gizmos in the game view. I haven’t gone through and tried disabling all of them individually yet, but something in that default list must be doing it.

10

I went through and unchecked everything from the gizmos menu that I could (“Selection Outline”, and “Terrain Debug Warnings” wouldn’t allow me to change them) and still get the error if I try to turn on Gizmos for the game view.

11

I have the same in 6000.1.0f1. It’s a fresh project, but also indeed only happens when enabling gizmos.
I just tried upgrading to 6000.1.4f1 and still get the same warning

12

Yes do get the same even with unity 6000.1.4f1 and 6000.049f1 which I just installed after deleting former versions of 6000.1 and 6000.0x and reinstalling the unity hub.

13

And I created 2 completely new projects 1 in each editor version hoping it resolves. The tried to see if it would be solved after restaring these projects. But no untfortunately not resolved.

14

and not on Unbuntu but windows 11

15

Same error just started popping up in 6000.1.4f1

16

Started having this issue today with 6000.1.6f1 reinstalled both unity and unity hub no resolve.

17

6000.1.6f1 same thing