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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment