Search Issue Tracker
Fixed in 2017.2.0f3
Fixed in 5.6.X, 2017.1.X
Votes
0
Found in
5.6.0p4
Issue ID
909148
Regression
Yes
Tiled GPU perf. warning: RenderTexture color surface was not cleared/discarded doing Graphics.Blit on emulated graphics
Tiled GPU perf. warning: RenderTexture color surface was not cleared/discarded doing Camera.Render/Drawing/post_test.OnPostRender Graphics.Blit with graphics emulation of OpenGL ES3.0 or ES2.0
How to reproduce:
1. Open project attached by the user
2. Notice the warning in the console
Notes: Happens on Android platform with Graphics Emulation of OpenGL ES 3.0 or ES 2.0
Reproduced on: 5.6.0p4, 5.6.1f1, 2017.1.0b5, 2017.2.0a1
Not reproduced on: 5.5.3p3, 5.6.0f3, 5.6.0p3
Regression introduced in: 5.6.0p4
Verified with: 2017.3.0a2.
Comments (6)
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
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
jjxtra
Jan 07, 2019 16:46
I'm seeing this in 2017.4. The fix is edit -> graphics emulation -> none. But this shouldn't be necessary. Why is this marked fixed?
Evaldas_Unity
Oct 11, 2018 04:53
I couldn't reproduce this on any fixed version using the original project. If you can reproduce, please submit a new bug report with a minimal repro project. Thank you : )
BravenBitGames
Oct 10, 2018 23:10
Not fixed in 2018.2.2
Piyush_Pandey
Aug 23, 2018 11:59
This issue is still there in 2017.2.0f3
jjxtra
Aug 14, 2018 16:57
As does 2018.2.2. This should not be marked fixed.
devcor
May 19, 2018 08:49
2018.1.0f2 has it as well.