OpenGL Driver Not Accelerated! [Resolved]

[ReX]

Yesterday I upgraded my OS to Windows 10, including the various OS software updates. Since then, I am unable to run GZDooM, which refuses to open; I get the following error message:

R_OPENGL: OpenGL Driver Not Accelerated!

I am running v4.3.3 of GZDooM, and I have DirectX 12.

My guess is, that when I upgraded to Windows 10, the OpenGL drivers got messed up. I did some internet searches for how to determine my version of OpenGL (including here, on the ZDooM forums), and they all require installing 3rd party software, which I want to avoid if possible.

Incidentally, today I downloaded and tried to install the following updates, in the hope that the relevant drivers would be installed:

kb4537572-cumulative-update-for-net-framework, Feb 27 (failed to install)
kb4541335-windows-10-update, Mar 24 (failed to install)

Should I search specifically for the OpenGL drivers I need (e.g., v3.3) and install them? I'm curious why a Windows update wouldn't work.

[Rachael]

Have you tried looking at this? viewtopic.php?f=50&t=55041

[Graf Zahl]

Microsoft provided drivers do not have OpenGL support, they are also mostly old. So get a driver from NVidia, AMD or Intel directly and install that.

[ReX]

@Rachael: Yes, that was one of my search results. However, it didn't seem to give me the answers I was looking for (specifically, how to determine OpenGL version without 3rd party software).

@Graf: Yes, I eventually figured out that MS drivers lack the OpenGL support.

Now here's the rub: My Display Adapter is old - Intel HD Graphics 3000. I spent some time searching around, and discovered several things:

1. Intel HD 3000 official drivers do not really support openGL of version greater than 3.1. This is probably ballacks, as I believe I was running OpenGL 3.3 with Windows 7.
2. In general, it appears that Windows 10 seems to have a problem with using OpenGL v3.3. The recommended solution is to use the drivers for Windows 7 (which is what I had before upgrading to Win 10).
3. I found a link to MS's Update Catalog, and downloaded the relevant zip file.
4. Meanwhile, I checked the computer's Device Manager, and discovered that I already had those drivers (Driver Version 9.17.10.4459) - I should have done this before going though the download, but one learns as one goes.

Bottom line is that I can't think my way through this problem. I definitely don't want to revert to Win 7 just because I can't run GZDooM (although, for a brief bit I was sorely tempted, given my level of frustration at my failure to find a solution). Let me poke around some more and report back.

[Graf Zahl]

1) If you want better OpenGL on that thing you'll need Linux. The Windows driver can indeed not handle anything better, and worse, is broken enough so that you can forget about anything that needs GL3. On Win 7 it was the same.

2) It's not Windows 10, it's that outdated graphics chip.

What kind of computer is that? Is it a laptop with no upgrade option? If so, you are screwed. If you got an expansion slot better consider buying a low end graphics card.

[ReX]

What kind of computer is that? Is it a laptop with no upgrade option? If so, you are screwed. If you got an expansion slot better consider buying a low end graphics card.

It is, indeed, a laptop - HP ProBook 6360b. I don't know if it has an expansion slot, but I'll check.

I use this laptop for my business travel, so that if it gets banged up or lost I won't lose my job-related files (the master versions of which are on my computer at my desk). I do a lot of DooM editing during travel, so I don't want to lose that opportunity. Hence, my desperation to get things to work on this old machine.

On a related note, I ran gzdoom-bin-3-7-2-legacy-x64, but it still gave me the same error message. Don't the legacy versions adjust for this?

But what I'm most curious about is this: Yesterday, when I was using Windows 7, GZDooM worked excellently fine. Today, with Windows 10, it doesn't even start. Why should people bother with upgrading to Win 10 on older machines?

[drfrag]

The vintage build and LZDoom require GL2 so you've not installed the drivers. Or is it still that manifest thing?

[ReX]

Or is it still that manifest thing?

I'm not clear on what this means.

If you got an expansion slot better consider buying a low end graphics card.

It is, indeed, a laptop - HP ProBook 6360b. I don't know if it has an expansion slot, but I'll check.

It would appear that my laptop has no expansion slot.

[Rachael]

I think this is clearly the manifest thing - especially if it worked before the upgrade.

The post I linked has the fix - it basically is a file that edits GZDoom's manifest in order to fool the Intel driver so that GZDoom (and the Intel driver) thinks it is still running Windows 8, where the driver still worked.

Windows 10, by itself, is not to blame here. All it did was reveal a bug in Intel's driver where it refuses to even start if the wrong operating system is detected.

[drfrag]

And what happens if i remove those manifest bits? Is it that much of a deal?

[Rachael]

Remove what bits?

[drfrag]

The win 10 part, i mean issues besides OS detection.

[Rachael]

I don't understand what you're asking.

If you're asking whether it's a good idea to use the WTFI utility on your own executables to modify the manifest, you don't even need to do that - the tool is open source and I believe the manifest replacement is in the source tree, you can simply copy it to your manifest and force all your executables to run in compatibility mode for Windows 8.

However, I have no idea what the side effects are if you attempt to run said executable on Vista or 7.

[Graf Zahl]

The side effects are that other libraries will also be unable to detect Windows 10. We can only guess if some may break or not - the bottom line is that generally it is not recommended.

[drfrag]

Being these legacy builds and since build version number is not very relevant i've removed Win10 compatibility from the manifest. Actually checking for OS version is discouraged and those functions are deprecated as i've read. App behaviour is the same for both 10 and 8 and the classic version still runs so addressed here:
https://github.com/drfrag666/gzdoom/com ... 9855dc5627