Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.1.0f3
Issue ID
932557
Regression
No
Standalone builds running on OpenGl exhibit heavier CPU and GPU usage than on DirectX 11
Steps to reproduce:
1. Download and open the attached project
2. Build for standalone
3. Open a hardware monitoring program (e.g HWmonitor or MSI Afterburner)
4. Run the build under OpenGl(project is set to that right now)
5. Observe CPU and GPU usage
6. Run the build under DirectX 11
7. Observe CPU and GPU usage
Expected results: relatively the same usage
Actual results: vastly different usage
Reproduced on 5.5.5f1, 5.6.3f1, 2017.1.0p2, 2017.2.0b5, 2017.3.0a2
Results on a GTX 970 i7-6700k
OpenGL: GPU usage ~90%, CPU usage ~40%
DirectX: GPU Usage ~75-80%, CPU usage ~15-20%
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
Add comment