Search Issue Tracker
By Design
Votes
4
Found in
2017.2.0p2
Issue ID
996119
Regression
No
Tiled GPU perf. warning appears when multiple cameras with Allow MSAA are present in the scene and Viewport Rect is not default
To reproduce:
1. Download and open attached "bug.zip" project.
2. Open "MSAA_perf_warning" scene.
3. Select "Back Cam" GameObject.
4. Change Its Viewport Rect X or Y values to be anything but not 0. For example set Y to be 0.75.
5. Notice that "Tiled GPU perf. warning" warning appears in the console.
Expected result: No warning appear in the console.
Actual result: "Tiled GPU perf. warning: RenderTexture color surface (1080x1920) was not cleared/discarded. See TiledGPUPerformanceWarning.ColorSurface label in Profiler for info" warning appears in the console.
Workaround: Have only one camera in the scene with "Allow MSAA" enabled.
Reproduced with: 2018.2.0a1, 2018.1.0b6, 2017.3.1f1, 2017.2.1p3, 2017.1.3p1, 5.6.5p1. 5.6.0a1.
Notes: In 5.5 where allow MSAA option was not yet introduced everything works as expected. Warning seems to appear only when Platform is set to Android. Issue does not reproduce if platform is set to WebGL or Standalone. In some cases, when ViewPort Rect values are set to be specific numbers, for example set Y to be 1, then warning does not appear, but when scene view is focused error appears "Screen position out of view frustum".
By design: warning to warn about potential performance cost on mobile tiled GPUs, in Editor warning can be suppressed by disabling Graphics Emulation.
more info: https://docs.unity3d.com/ScriptReference/RenderTexture.MarkRestoreExpected.html
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment