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
ChrisLoh
Apr 07, 2016 06:31
Hi guys, I'm getting this issue all the time, even for almost completely empty scenes.
I suspect a 3rd party asset (from the Unity Asset store) is causing our problem.
Perhaps we can see if we have asset packs in common that might be causing it.
Might it be:
- Stylized Nature Pack?
- A touch gesture pack that has left residual scripts in common folders?
I have a lot of asset packs that are integrated so am loathe to disconnect them one by one if it can be helped.
Does anyone else use any of the above? Or are there any other suggestions on 3rd party packs that might be causing the problem?
theolagendijk
Apr 05, 2016 15:12
Often getting this error in 5.4.0b13 play mode and it freezes my Game preview. Only solution I have found is to restart Unity.
lup
Mar 31, 2016 16:48
Sorry, I meant Unity Version 5.4.0b12.
lup
Mar 31, 2016 16:46
I'm also having this issue in 5.4.0b1. It happens about every 10 minutes and makes the scene preview unresponsive and requires a complete restart of Unity to fix. I'm on Mac OS X El Capitan 10.11.1.
I get the following errors in the console when it happens:
!::HasAsAttachment(GLESRenderTargetSetup(m_PendingFramebuffer), rbid)
!::HasAsAttachment(GLESRenderTargetSetup(m_CurrentFramebuffer), rbid)
!attach.color[0] || !attach.color[0]->backBuffer
!attach.depth || !attach.depth->backBuffer
Echo____G
Mar 29, 2016 08:09
I meet the same problem and still not solve it.....
fastgamedev
Mar 26, 2016 05:59
Getting this error intermittently in 5.4.0b10. No idea why it's happening.
p-seba
Mar 24, 2016 14:42
Irregularly getting this error in 5.4.0b9. It freezes my scene and I have to stop it and play again.
ChrisLoh
Mar 13, 2016 10:16
I get the same error message in a simple scene with several quads, on each of which is material using a PNG with transparency (used to depict static 2D characters). Sprites/Default shaders are used and Unity 5.4