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
- ArgumentExceptions are thrown when an exclamation mark is written as the first character in the search window
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
Add comment