Search Issue Tracker
Duplicate
Votes
0
Found in
5.1.0f2
Issue ID
698575
Regression
Yes
Unity 5.1.0b3+ crashes after clicking "Require ES3.1"
Unity 5.1.0b3+ crashes after selecting "Require ES3.1" in player settings
To reproduce:
1) Create new project in Unity 5.1.0b3+ (or port project from 5.0 to 5.1.0b3+)
2) Go to Edit->Project Settings->Player
3) Go to Android tab->Other settings
4) Uncheck "Automatic Graphics API"
5) Remove OpenGLES2 from list
6) Check "Require ES3.1" - Unity crashes immediately
Workaround: Open project in 5.1.0b2 and do all the steps. After that it works normally in all other versions.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
This is a duplicate of issue #696814