Search Issue Tracker
Fixed in 4.5.X
Votes
0
Found in
4.3.2f1
Issue ID
584901
Regression
Yes
OpenGL ES 2.0 emulation is not available in the editor when it is started with "-force-opengl" flag
This is a regression from Unity 4.2.2f1. When Unity editor is started without any flags, or with "-force-d3d11" flag, the "Edit -> Graphics Emulation -> OpenGL ES 2.0" option is available and is selected. If the "-force-opengl" flag is used, the "Edit -> Graphics Emulation -> OpenGL ES 2.0" option is grayed-out, it is impossible to select it and "No Emulation" is selected instead.
Reproduced with:
Unity Version 4.3.3f1 (c8ca9b6b9936)
Unity Version 4.3.2f1 (0517a5ae8669)
Unity Version 4.3.1f1 (cebd4d9b5122)
Unity Version 4.3.0f4 (e01000627d60)
Reproduction steps:
1. Run Unity editor with the "-force-opengl" flag
2. Open any project
3. Notice that "Edit -> Graphics Emulation -> OpenGL ES 2.0" option is grayed-out and it is impossible to select it
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Look Dev constantly regenerates the default Volume Profile when set to "None" instead of using the default one
- Look Dev errors are spammed when opening a new HDRP project when Look Dev was added to the layout in the previous project
- URP Scene Templates are not editable when first opened from the New Scene dialog
- Look Dev window flickers when resizing the window after docking it
- UI breaks when Multiplayer Center window section divider is moved too far
Add comment