Quote:
Originally Posted by RbnJrg
Ok. I'll do that and I will let you know my results.
|
Thanks. Keep in mind that with the method above, the environment variable will only exist for that particular command-prompt session. You can't set the variable via the command-prompt and then launch Sigil via the gui (or a different command-prompt).
Some background behind my line of thinking: the Qt5.6 that's included with Sigil 0.9.10 (and earlier) was custom compiled by me to make use of the ANGLE libraries that are included with Qt--exclusively. In short, the ANGLE libraries included are used in place of the system's own OpenGL implementation. With Sigil 0.9.11+, Qt5.11.2 is the same stock, dynamic version that can be downloaded by anyone. It attempts to 1) use the system's own OpenGL drivers, if that fails (or can't be found), it 2) falls back to the included ANGLE libraries (OpenGL ES), should that fail, it falls back to 3) a software version of opengl optionally provided as a dll in Qt distributions (and I don't provide that with Sigil).
Not all OpenGL implementations are complete in many Windows video drivers, so I'm wondering if there's a failure of some sort happening with the default "desktop" OpenGL on some machines. I'd like to rule that possibility out by forcing the Qt provided with Sigil to use the ANGLE libraries exclusively.