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
- Crash on PrepareDrawShadowsCommandStep1 when entering the Play Mode in a specific project
- Physics Layer Collision Matrix's Layer names, checkboxes and hover highlights become misaligned when the Editor's UI Scaling gets changed
- Light/shadow information on an edge of a Terrain tile creates a seam with an adjacent Terrain tile when baking a LightMap
- "Missing types referenced from component UniversalRenderPipelineGlobalSettings on game object UniversalRenderPipelineGlobalSettings..." warning is thrown after switching the Platform to tvOS
- “Metal: Error creating pipeline state (Universal Render Pipeline/2D/Sprite-Lit-Default): Vertex attribute BLENDINDICES0(5) of type uint4 cannot be read using MTLAttributeFormatFloat2 (null)“ when setting GPU Skinning to GPU after opening the project
Add comment