Search Issue Tracker
Fixed
Votes
0
Found in
5.3.1f1
Issue ID
756023
Regression
Yes
Large CPU overhead using OpenGLCore
Steps to reproduce:
1. Download and open attached project "Unity 5.3 tests.zip"
2. Make sure the API in player settings is set to OpenGLCore
3. Play the scene and notice overhead in profiler
4. Change API to OpenGl2
5. Play the scene and notice that overhead is noticeably lower with older API
Expected result: Same overhead or smaller with new API
Tested and reproduce on:
Windows 10
Unity 5.3.1p3, 5.4.0b1
Not reproducible:
Unity 5.2.4p1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment