Search Issue Tracker
Fixed in 5.4.0
Votes
33
Found in
5.4.0a5
Issue ID
750405
Regression
No
[OSX] RenderSurface attachment asserts on various projects, in 5.4 beta builds
Steps to reproduce:
1. Open Unity;
2. Open attached project;
3. Open "1.unity" scene;
4. Notice that there are 3 planes in the scene with 3 different Shaders having uniform arrays parameters and script, processing those parameters at runtime;
5. Enter Play mode;
6. Zoom in/Zoom out by scrolling mouse wheel in the Scene view;
7. Wait for some time (10-20 seconds).
Actual result:
Weird errors appear in the console:
attach.color[0]->backBuffer == attach.depth->backBuffer
!attach.color[0] || !attach.color[0]->backBuffer
See attached actual.png screenshot.
Notes:
- Reproduces only on OSX (10.11.4), OpenGL4.1 (GLCore) mode;
- Doesn't reproduce on Windows 10;
- The issue doesn't reproduce every time;
- The other possible symptom of this failure is that Game View becomes unresponsive and following assertions appear (in addition to abovementioned ones):
!::HasAsAttachment(GLESRenderTargetSetup(m_PendingFramebuffer), rbid)
!::HasAsAttachment(GLESRenderTargetSetup(m_CurrentFramebuffer), rbid)
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
- MeshRenderer.sortingLayerID cannot be changed when change is being done in a built Player
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
Enrico-Monese
Jun 28, 2016 14:39
Nope wasn't the Graphics jobs. Actually just changing one thing in the Player Settings fixes it for one time. You play it and it works, play again and it's broken again. But if you change something in the settings then you have another round without errors.
This is strange
Enrico-Monese
Jun 28, 2016 14:34
Enabling graphics job seems to fix it
Enrico-Monese
Jun 28, 2016 14:32
Still there in b22
FF1878
Jun 20, 2016 22:46
!attach.depth || !attach.depth->backBuffer
Same thing on 5.4.0B21.
The solution is to Default the Layout.
novaVision
Jun 09, 2016 20:41
That's true - still exists in b20
eco_bach
Jun 05, 2016 21:59
ditto :Still present in 5.4.0b20. <OSX El Capitan>
For a quick workaround use Window > Layouts to switch it to something else (and back again).
greenland
Jun 05, 2016 02:00
Still present in 5.4.0b20.
For a quick workaround use Window > Layouts to switch it to something else (and back again).
ttchance
Jun 01, 2016 11:45
Using Unity 5.4.0.b19 and this still happens.
Also to people restarting Unity: There's a temporary work around by just switching Unity tab.
Make sure you have an alternative tab adjacent to the Game window, such as Animation or Asset Store (Don't think Scene works). (You just need to refresh the OGL context, which is done via Maximize or switching tab)
onimitch
Jun 01, 2016 11:42
This is not fixed, we are still seeing it in 5.4.0B19
Keepabee
May 30, 2016 09:15
The "!attach.color[0]" error repeatedly occurs on beta Editors up to 5.4.0b19 on OS X 10.11.5, I'll try to post a separate issue report soon, since I don't recognize anything said about Rendersurface that would make sense with what we are doing - the Game window just stops rendering at some random frame even if the game is not running (in which case it'll just draw grey background) in Editor. This happens many times a day, almost once every whenever between one to twenty minutes, requiring a reboot before the Game window can display anything again, causing huge problems to checking UI layout designs or basic runtime testing anything in Editor.