Search Issue Tracker
Not Reproducible
Votes
0
Found in
2017.2.0f3
Issue ID
972708
Regression
No
Forcing OpenGL or OpenGLES on a standalone build produces error
How to reproduce:
1. Open Unity
2. Open any Unity project
3. Build it as a Windows Standalone Build
4. Try running it while using '-force-glcore' or '-force-gles'
Expected result: Unity runs the game
Actual result: Unity displays an error message.
Error message:
Failed to initialize player
InitializeEngineGraphics failed
Reproducible with - 5.6.4p3, 2017.1.2p3, 2017.2.0p4, 2017.3.0b11, 2018.1.0a7
Reproduced on:
- PC
- Windows 10 64bit
- Intel(R) Core(TM) i5-6400 CPU @ 2.7Ghz
- 16GB RAM
- NVIDIA GeForce GTX 1050
- Windows 10 Pro 64-bit
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment