If I am wrong, obviously I am open to being corrected. All because one Intel engineer thought it would be a genius idea to lock the drivers to a specific kernel version of Windows - and then the company refuses to hotfix that out. So in the end, with focusing on legacy compatibility, some sacrifices have to be made on the modern side - and what is sacrificed is something GZDoom can keep and focus on, instead. Sure, it isn't ideal, but honestly I can't think of a better one, and while I can't speak for him I do doubt that he is interested in distributing two versions of LZDoom - one for the broken Intel drivers and one for everyone else. I think drfrag's solution was appropriate mostly because it focused on LZDoom which itself focuses on legacy hardware. Some people can do the properties sheet just fine, though - and if they can, more power to them, that method definitely could be encouraged for them. How eager are you to walk someone through getting to the properties sheet to enable this? I am trying to see from an end-user's perspective, and honestly I think if I was pretty green with navigating the operating system in general, since I would at this point already be familiar with downloading tools, I'd rather just let a tool do the work for me, because downloading the tool is a procedure I'd naturally already be more familiar with, than looking at the properties sheet. If it does work, I would assume "turn on compatibility mode" is easier than "download this tool" or "download this other version."īlzut3 wrote:If it does work, I would assume "turn on compatibility mode" is easier than "download this tool" or "download this other version." Assuming that's a viable solution anyway. In my opinion this working as intended would be more important than a few people running hardware not supported by their OS not having to go into properties and work around a driver bug. The version check functions are discouraged since people get version checks wrong all the time, but GZDoom uses it for reporting the version of Windows (i.e. Given that we have code to read CPUID it may even be easy to show the message only to Sandy Bridge users. Although I don't think there's a good automatic solution, changing the error message when running under Windows 10 to include a note about 2nd generation Intel processor graphics would likely help (users don't read, but I personally get a kick out of when they copy and paste a message which contains the exact solution in it). Drfrag wrote:I meant how do users know that they must use a compatibility mode when they get the OpenGL not accelerated error?Īhh.
0 Comments
Leave a Reply. |