Editor error : !attach.depth || !attach.depth->backBuffer

Unity Engine
1

Hi guys,

Just tried my current project in the latest Unity Beta 5.4.0.b17 and I have two errors thats seems to happened randomly (but I’m pretty sure t’s not) and made Unity stop working as expecting - forced me to restart every time it happened. Those errors are :

!attach.depth || !attach.depth->backBuffer
and
RenderTexture warning: Destroying active render texture. Switching to main context.

I work on Macbook pro Retina 13" - OSX El Capitan 10.11.3

Thanks

2

I’ve gotten this error (the one in the topic’s title) a few times now as well. They happen in play mode in the editor. I haven’t found any ways to reproduce it. Seems to happen out of nowhere. It then messes up the play view by freezing whatever it was rendering at the time. Exiting and entering play mode doesn’t redraw the game view thereafter.

I’m also using OS X El Capitan.

3

I get this too. Usually I can toggle out of Game view to Console, and that clears it. I don’t need to restart or anything. I think it’s an OpenGL error related to he Editor.

1 Like
4

Ok - I’ll tried to toggle out Game view to Console because it was very annoying to close and restart Unity something like 20-30 times yesterday !

5

Fixed internally, but wending its way towards the release branch.

1 Like
6

Still getting this error in beta 19.

7

Yep still an issue in 5.4.0B19

8

I can confirm the error (Game view freezes randomly on play) and that hiding Game view by toggling in and out to another tab (console) works as a workaround.

9

In beta 21, I’m receiving a similar error:

!attach.color[0] || !attach.color[0]->backBuffer

Color instead of depth.

10

Note: still getting the depth version as well. This happened when I was changing the z value of a GameObject with a sprite renderer from 0.0 to 1.0 in the editor.

The game view’s pixels became uninitialized garbage.

Getting this error to the point of the editor being nearly unusable.

Edit: I’m using Mac (OS X El Capitan).

11

I’ve been switching back and forth from PC to Mac. This is definitely only showing up on the Mac. Nothing similar on PC…

2 Likes
12

Have the same problem in editor - scene goes to black.

13

Still happens in beta 22.

14

Fairly sure they’re just gonna’ ship it in this condition, unless they’re deliberately leaving this broken because it’s part of something required for beta testing but not production release.

2693586--190592--Screen Shot 2016-06-24 at 1.36.04 PM.jpg
2693586--190592--Screen Shot 2016-06-24 at 1.36.04 PM.jpg2560×1600 651 KB

Here’s what happens if you resize the Game View once it goes black.

15

Has anyone filed a bug report on this? It is such an intermittent error, that I have not found a reproducible test case. Now I am working mainly on PC where it’s not an issue, but it’s a pain when I get back onto the Mac if it’s still there. A search shows no open case, so I don’t think Unity is aware of this problem:

http://unity3d.com/search?refinement=issues&gq=attach.depth

Shows the most recent issue as resolved, but I don’t think it is the same thing. If someone files a bug report, I’d gladly upvote it.

16

Still in b23…

1 Like
17

Ugh… Back to working on a project with my MacBook and the error is back!

!attach.depth || !attach.depth->backBuffer

Happened the 2nd time I played and seems to be more frequent than I ever remember it.

18

Looks like the expected backport from mainline never happened. Working on it, but it might miss RC1. Should make RC2 though.

19

Hey I found a pretty quick (hacky) fix for this.
Save your layout (even after the error has popped up) then just load that layout.

20

Just happened to me in 5.4.0f1:

!attach.color[0] || !attach.color[0]->backBuffer

Very annoying!