Unity 5.1.2f1 freezing on startup when using -force-gles20 flag

Unity Engine
1

Hello… This seems to have been an ongoing issue now, and it’s only seemed to happen since I updated to Unity 5… Any time I try to use an openGL backend, (Latest attempt was to get the GLES2.0 flag working) the editor opens, but then, instead of loading everything, it’s a white window, the disk usage shoots up to 100%, and the system itself completely locks up! At least today I was able to shut unity down before I got impatient enough to press the power button!

So, in any case, is there a reason my system’s doing this? I haven’t had the chance to check the editor log for anythign yet.

System specs:

  • CPU: Intel Core i3
  • GPU: Intel HD Graphics 3000
  • RAM: 4GB
  • Actual machine model: Dell Latitude E6220
2

Bumping this, as I now need to use the gles20 flag to debug something!!! :hushed:

3

Same in 5.1.3?

4

Haven’t tried that one. I have seen however that ALL of the 5.x cycle releases have done this on my computer. (This was with the -force-opengl flag more so, and now with the -force-gles20 flag!)

5

hmm Wait till 5.2 (should be tomorrow according to our roadmap) if you’re still seeing it in 5.2 can you report it as a bug from 5.2 and post the number.

6

Ok then. I am yet to give 5.1.3 a try. (It’s installed however)

EDIT: I have improvement! :slight_smile: it’s no longer locking up, but now unity just crashes. Might have to usea game engine of mine to check the GL extensions. Won’t belong… :smile:

EDIT2: Bug reporter popped up while i was typing last edit, I might as well pop a bug report in if my machine has the correct extensions to use gles20 flag.

7

Ok, confirmed that ARB_ES2_Compatibility extension is actually missing from my machine, sorry for wasting your time! :frowning: Hopefully my next computer will have the capability…

8

Ok, did a test to see if legacy OpenGL 2 backend would work- WTF?! It went and did it again, only this time, the disk usage of the SYSTEM process shot up through the roof when I switched backends!

I have a feeling part of windows 8.1 must be doing this, not Unity… :rage:

9

Ok, I noticed that OpenGLCore fixes were included in 5.2, so i will test once it’s finished downloading.

Also, a side-note: will unity still work with visual studio 2013? 2015’s a bit too big to install yet…

10

Ok, crashing and freezing no longer happens, however, I can’t switch to GLCore or even OpenGL2 on intel HD 3000 chip! It just falls back to DirectX

Should I file a bug?

11

The best way to fix freezing is end Task the Not Responding program. If the Caps Lock can turn on and off, Windows is still working, but another program may not be responding and causing the computer to freeze. Press Ctrl + Alt + Del to open the Windows Task Manager. Check Dell Latitude E6220 Manual for full detail.

12

I think I know what the issue back then was; it turns out intel had stopped official support for the OpenGL driver since Windows 7, and it meant the Intel HD 3000 on anything above Windows 7 had a bugged OpenGL 3.3 implementation.

I had real issues on Windows 10 with that laptop due to that, so a note to all Intel HD 3000 owners that GLCore isn’t compatible with machines running one of these Second-gen chips and either Windows 8.1 or Windows 10

Also, on the same laptop, Debian 9 with latest Mesa (13.4 at time of writing this) runs GL 3.3 Unity Games fine.

Nowadays, I use a Toshiba NB550D for Windows development, as it has better compatibility with Windows 10

Also…

I don’t know who you are but I am well aware of how to end my own programs, thank you. Probably NOT a good idea to post stuff like this here.