<!-- Windows 10 -->
<supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"/>
As long as it isn't there, it runs fine.
I found this out after GZDoom compiled without the manifest. This is super weird.
Spoiler: Old post
Okay, so, I can run GZDoom 2.0.05 fine. I can also run g2.1.pre-587-ga95edc3 fine.
However, g2.1.pre-624-7957862 and higher do not work.
The problem is not missing OpenGL 3.x support in my GPU, considering I could run g2.1.pre-624-7957862 and higher before upgrading to Windows 10.
Obviously, something happened between g2.1.pre-587-ga95edc3 and g2.1.pre-624-7957862 that broke it.
RAM: 2 GB (Usually 50 % used up)
CPU: Intel Celeron CPU G530 @ 2.40 GHz
GPU: Intel HD Graphics GPU (Supports OpenGL 3.x. No Windows 10 drivers.)
Storage:
232.76 GB SATA HD (212 GB usable because shitty OEM(?).)
149 GB SATA HD. (The HD's label says 160 GB)
OS:
Windows 10 Single Language 64-bit
1920x1080 monitor
Re: Mysterious "R_OPENGL: OpenGL driver not accelerated!" er
Posted: Thu Sep 17, 2015 7:48
by Graf Zahl
Please post your entire startup log. There must be something more.
Re: Mysterious "R_OPENGL: OpenGL driver not accelerated!" er
Posted: Thu Sep 17, 2015 8:23
by phantombeta
Here's the log from g2.1.pre-1231-g5a7afad:
[spoiler]
Re: Mysterious "R_OPENGL: OpenGL driver not accelerated!" er
Posted: Sat Sep 19, 2015 17:34
by phantombeta
Okay, uh. Someone gave me a build of g2.1.pre-1262-g61e09da. Their build works fine.
However, if I try to run DRD Team's build of g2.1.pre-1262-g61e09da, GZDoom crashes with the "R_OPENGL: OpenGL driver not accelerated!" error.
So, uh. What's going on?
Re: Mysterious "R_OPENGL: OpenGL driver not accelerated!" er
Posted: Sun Sep 20, 2015 16:43
by Gez
I'm curious about this line in your log:
GPU: Intel HD Graphics GPU (Supports OpenGL 3.x. No Windows 10 drivers.)
Re: Mysterious "R_OPENGL: OpenGL driver not accelerated!" er
Posted: Sun Sep 20, 2015 19:30
by phantombeta
Intel has not made any Windows 10 drivers for this GPU. The Celeron G530 is marked as "End Of Life" on Intel's website.
This GPU apparently can use drivers for a Core series' processor's GPU, but the Windows 10 drivers for it can only be downloaded through Windows Update. Windows Update does not list or find the drivers when checking for updates.
Re: Mysterious "R_OPENGL: OpenGL driver not accelerated!" er
Posted: Tue Sep 22, 2015 4:57
by Rachael
Have you tried installing the Windows 8.1 drivers?
It's not always recommended you do things like this but usually it works without issues. As far as I know, Windows 10 should support any drivers from Vista and later (as long as it supports WDDM).
Re: Mysterious "R_OPENGL: OpenGL driver not accelerated!" er
Posted: Thu Oct 01, 2015 23:21
by phantombeta
@Eruanna
I did. If I didn't I wouldn't be able to run Kyle873's build of GZDoom g2.1.pre-1262-g61e09da.
phantombeta wrote:Okay, uh. Someone gave me a build of g2.1.pre-1262-g61e09da. Their build works fine.
However, if I try to run DRD Team's build of g2.1.pre-1262-g61e09da, GZDoom crashes with the "R_OPENGL: OpenGL driver not accelerated!" error.
So, uh. What's going on?
Re: Mysterious "R_OPENGL: OpenGL driver not accelerated!" er
Posted: Fri Oct 02, 2015 6:50
by Rachael
Ok, sorry, I didn't see your post closely enough.
Re: Win10 being listed in the manifest breaks Intel drivers?
Posted: Thu Nov 19, 2015 22:28
by phantombeta
Okay, so I found out exactly what breaks it. This is extremely weird.
(Check the OP)
Re: Win10 being listed in the manifest breaks Intel drivers?
Posted: Thu Nov 19, 2015 23:26
by Graf Zahl
Sounds like just another inept use of Windows's GetVersion function. But inside a driver? That's certainly a first.
Re: Win10 being listed in the manifest breaks Intel drivers?
Posted: Fri Dec 11, 2015 7:38
by Reaver
I realize this may be annoying to ask but im having the same issue and don't really wish to mess with compiling gzdoom or whatever (ill admit, just straight laziness) and im missing playing Aeons of Death, silly mod that only works with gzdoom-g2.1.pre-1196-g02c3828. does anyone have a version of this that'll work on Win10? Thanks!
Re: Win10 being listed in the manifest breaks Intel drivers?
Posted: Fri Dec 11, 2015 9:42
by Graf Zahl
So what am I supposed to do here? If I remove the line from the manifest I'll break the GetVersion function and cut myself off from any potential future handling of OS specific issues. If I don't, it won't work on this particular GPU.
This is not fixable without creating another issue.
Re: Win10 being listed in the manifest breaks Intel drivers?
Posted: Fri Dec 11, 2015 10:20
by Reaver
what a mess, stupid Win10 I wish I could rollback now..
Re: Win10 being listed in the manifest breaks Intel drivers?
Posted: Fri Dec 11, 2015 10:32
by Graf Zahl
Don't blame Windows for Intel's ineptness.
It has been known for many years that developers have problems with version detection - but finding an issue like this in a DRIVER is something I'd never have expected, let alone from someone like Intel...