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
- GPU utilization increases by 20% on Meta Quest headsets when Render Graph is enabled on 6000.0.16f1 and higher
- Value on Slider (Int) control in UI Builder displays as default when saving UI Document
- Color mismatch in UI Builders Library panel when the Editors theme is set to Light Mode
- [Android ] "AndroidJNI.ToBooleanArray" returns a random non-zero value instead of "IntPtr.Zero" when the method argument is null
- Non-HDR color picker opens when selecting material color with HDR enabled
Rod-Galvao
May 20, 2016 21:23
Same Here. Mac OS X 10.11.4.
It happened while running the scene "12_Train" from Curvy asset.
Somaar
May 20, 2016 17:34
Also got this error in Unity 5.4.0b17 personal on Mac OS X El Capitan.
Was using a camera with script below to manipulate the camera with trackpad gestures (two finger mouse wheel simulation).
Soon afterwards this error appeared, according to the steps to reproduce the mouse scrolling is involved..
void OnGUI()
{
if (Event.current.type == EventType.ScrollWheel) {
Vector2 touchDeltaPosition = Event.current.delta;
x -= touchDeltaPosition.x;
y -= touchDeltaPosition.y;
}
mrpinebox
May 13, 2016 12:11
Seeing this in 5.4.0b17 personal on Mac OS X El Capitan. Game view freezes but can restore by closing tab and reopening tab in Window -> Game.
Error messages:
!::HasAsAttachmetng(GLESRenderTargetSetup!::HasAsAttachment(GLESRenderTargetSetup(m_PendingFramebuffer), rbid)
!::HasAsAttachment(GLESRenderTargetSetup(m_CurrentFramebuffer), rbid)
!attach.color[0] || !attach.color[0]->backBuffer
!attach.depth || !attach.depth->backBuffer
rmb303
May 09, 2016 23:02
I've also started to get this issue using 5.4.0b17.
I was using the latest 5.3 version until yesterday, and never saw the "attach.color..." errors until now.
Running on Mac OS X 10.11.4.
HUIYA
May 08, 2016 08:20
I have same issue.
I get the error in console,
!attach.depth || !attach.depth->backBuffer
and "Game" Scene Fozen, but works fine "Scene" in Editor.
OS : OSX - El Capitan 10.11.4
Unity : 5.4.0 b17 - OpenGL 4.1
pbeni
May 05, 2016 15:48
Getting Similar Error: !attach.depth || !attach.depth->backBuffer
Seems to happen randomly in play mode. I do not need to do step 6 to reproduce.
I'm on OS X 11.11.4, MacBookPro (Retina 13, Early 2015)
Intel Iris 6100
Using Unity 5.4.0b17 (and many previous versions of unity)
danp
Apr 30, 2016 03:15
Still happening in 5.4.0b16.
zedaidai
Apr 29, 2016 14:46
Same error with 5.4.0b16.
!attach.color[0] || !attach.color[0]->backBuffer
and game view frozen.
I have to restart Unity to fix the game view.
on yosemite 10.10.5
rubendejong25
Apr 13, 2016 14:48
uninstall this to avoid this errors and then update your pc programs and reinstall when its done
ChrisLoh
Apr 13, 2016 08:27
Upgrading Unity to 5.40b13 appears to resolve this issue.
I no longer seem to get the error (fingers crossed).