DRD Team

There are just a windows that open and then close instantly without having the time to see anything and the problem stay there.

blood wrote:When I launch the program nothing happens, I tried to launch it from Command line with or without Admin and it's only say:
"Usage: C:\Users\*****\Downloads\wtfi.exe <file.exe> <...>", the problem is still there.

You need to run it like wtfi.exe path\to\gzdoom.exe, with proper path to GZDoom executable of course.

I managed to launch it, but now they tell me that:
"ERROR: LoadLibraryEx() failed for file path with error code 0x00000002"
"WARNING: File C:\Users\*****\*****\*****\*****\GZDoom\gzdoom.exe has no compatibility record in manifest"

blood wrote:"ERROR: LoadLibraryEx() failed for file path with error code 0x00000002"

This error code means 'file not found'. The path to GZDoom.exe you specified is wrong.

Well it seems that I've managed to launch it with this:
But at the end I get 2 lines that seem to say a failure and a succes
And for me, the crash is still happening half of times, I start to think that my problem isn't the same.

hi everyone i have a problem with 1.9.0 and 1.9.1 the thing is that i can't initialize any of them because it says r_opengl_: driver not accelerated, according to what i have read is a driver related issue, but here is the weird part i use to use 1.8.10 and then changed to 1.9pre found on moddb i have never have problems with that and almost everything works with that but 1.9.0 and 1.9.1 won't run on my laptod, my graphics card is an integrated one, intel hd 1.5 gb, i checked at intel's site and found out i have a 1st gen processor which has no current support and latest official driver is the one i have installed, and here is biggest mistery about this while trying to make udv 1.84 run with pb2.03(a) somehow i manage to initialize the game but everything aside hud and weapon's sprites looked fuzzy and ugly, i erased gzdoom files and dowloaded clean versions of all, 1.9pre, 1.9.0 and 1.9.1, using 1.9pre i can play normally with hd textures but can't use 1.9.0 and 1.9.1 anymore and i don't know how to recreate conditions that allowed me to run them in the first place, so can anyoe help me?

There were several 1.9pre builds, what's the exact version you have? I'm interested in digits after 1.9pre-...

EDIT: And please post detailed info about the CPU, i.e. model number like i7-312 or i3-123M.

hi here is the info you need

os windows 10 32bit up to date

gzdoom-G1.9pre-828-g60ff6c5 found here: http://www.moddb.com/games/doom/downloa ... -19-pre828

intel page info

processor i3 1st gen:
-Processor Number i3-330M
-Intel® Smart Cache 3 MB
-DMI 2.5 GT/s
-Instruction Set 64-bit
-Instruction Set Extensions SSE4.1/4.2

Processor Graphics ‡ Intel® HD Graphics (this is an integrated graphics card, 1.5gb)
Graphics Base Frequency 500 MHz
Graphics Max Dynamic Frequency 667 MHz

if i use 1.9pre i can run almost anything but there are two addons i can't use with pb2.03 smarscav found here http://www.moddb.com/mods/brutal-doom/a ... avenger-v3 and uvd 1.83+ found here http://www.moddb.com/mods/brutal-doom/a ... ki113r-v51 i can run 1.82 normally
it doesn't matter if i can't use 1.9.0 or 1.9.1 i just want to be able to run those two

and i'll include info files mentioned in other thread

Sounds like another case of the 'manifest breaks OpenGL on old Intel' issue. I think I'm going to remove that Win10 entry from the 1.x branch.

sorry about double post but i had serious troubles with internet, here is the other file, and here is an interesting fact i found out recently, i changed to 1.8.10 found in this site and i could run smartscav i could not with 1.9pre

renkoha wrote:sorry about double post but i had serious troubles with internet, here is the other file, and here is an interesting fact i found out recently, i changed to 1.8.10 found in this site and i could run smartscav i could not with 1.9pre

Earlier in this forum thread I posted a tool to fix a similar issue. You can give it a try.

Graf Zahl wrote:Sounds like another case of the 'manifest breaks OpenGL on old Intel' issue. I think I'm going to remove that Win10 entry from the 1.x branch.

Intel's bug affects both branches. Just 1.x builds are used more often with Intel integrated graphics.

_mental_ wrote:

Graf Zahl wrote:Sounds like another case of the 'manifest breaks OpenGL on old Intel' issue. I think I'm going to remove that Win10 entry from the 1.x branch.

Intel's bug affects both branches. Just 1.x builds are used more often with Intel integrated graphics.

That's the point. So far it looks like this only affects old hardware which doesn't benefit from 2.x at all, even if some of it is GL 3 compatible. But it also looks like nearly all GL2.x hardware actually IS affected so keeping this in would mean that the capability of checking for Windows 10 effectively prevents it from being used on Windoes 10.