Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3.0p4
Issue ID
995581
Regression
Yes
[VR | Performance] 2017.3 GPU memory usage increased about 100MB when VR enabled and 8x anti alias
Our contact from Oculus reported a performance issue on 2017.3 to XR devs and we XR QA are able to repro the issue.
Basically, comparing to 2017.2, when VR is enabled and entering playmode, GPU commited bytes increased about 100MB. We are not sure if this is by design or bugs, need VR gfx devs to investigate.
Repro steps:
1) Create an empty project using 2017.2.1p3.
2) In quality settings, set anti alias to 8x. In XR settings, enable XR support and select Oculus SDK. Make sure OculusRift is hooked up and ready to use.
3) Open Process Explorer (an open source tool) and find Unity processes.
4) Enter playmode, observe GPU memory usage numbers
5) Open the same project in 2017.3.0p4 and do the same, observe the increased GPU memory usage numbers.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment