Finally! \o/

DosFreak wrote:

Everyone start testing and reporting your DirectDraw and <DX7 games!

If this ever works on W9X and GL 1.1 (what dx>gl wrapper does?), I'll try wrapping it to the PowerVR MiniGL

I noticed Fallout works fine on it. Now if only the bsnes crt shader could be ported to it! 🤣

Fallout 1 demo works too
Windows 7 64bit
Run in Windows 95 compatibility mode.
DXGL fixes Windows 7 color issue

yet another wrapper that doesn't fix Moto Racer 😒
😜

Quake2 works, but Hexen2 and WinQuake doesn't, since Scitech MGL is a jerk

Ooooohhhhh, I see we could play our old 32 bit games like say starcraft for diablo 1 with out all technicolor spew (rainbow color glitch). If i'm understanding this right. If so this is awesome.

This issue is fixed on Windows 8 (at least for the few games I have tested) but yeah this and the other ddraw fixes/wrappers work pretty good at fixing that issue for Windows 7.

might have to try 8 with classic shell addon.

Too bad this doesn't work with Steam overlay.

leileilol wrote:

Too bad this doesn't work with Steam overlay.

does it cause problems with other programs? or can you not play your games using it with steam overlay?

Wow! I am stunned.
Just tried it out on a game and worked perfectly.

RayForce (DirectDraw) fullscreen 1280x960 @ 60FPS
Perfect scrolling and rock solid 60FPS.
WinXP32, ATI HD4670 AGP. DXGL v0.4.0
Results:
Video Card VSync OFF and WITHOUT DXGL = 600+FPS (640x480@75Hz)
Video Card VSync ON and WITHOUT DXGL = 600+FPS (640x480@75Hz)
Video Card VSync OFF and WITH DXGL = 100+FPS (1280x960@60Hz)
Video Card VSync ON and WITH DXGL = 60FPS (1280x960@60Hz)

Will try some more games out tomorrow.
This looks very promising indeed!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Edit1:
Raiden II doesn't want to work with this .dll
The game by default always starts in a window and then usually you have to go through the game menu and tell it to go fullscreen every time you start the game. With this .dll it just crashes as soon as game is run.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Edit2:
Can somebody please explain how to get a shader working with this?
Or is it not fully implemented yet?
Is it possible to use something like a HQ2x.fx or Cartoon.fx shader?

Thanks.

I'm gonna have to try this on a machine some time. maybe i could play the older command and conquers in 640x480 with rainbow throw up, same with start craft and diablo 1.

Damn, I'm too tied up testing DirectX8 D3D games at the moment so haven't been able to look at DXGL really.

Just tried RAYSTORM and it wouldn't run with DXGL. Wouldn't run with D3DWindower, DXWind, or DDraw to DDraw wrapper either. Guess the RAYSTORM wants to keep to itself and not share with anything else.

Damn shame, that game is screaming out for 1280x960.

If you want to know; when RAYSTORM is run with DXGL an error? box pops up with something like 'primary display driver DXGL hardware accelerator...' YES/NO if you click YES it exits out to desktop. If you click NO it changes to ''primary display driver DXGL hardware accelerator with Transform and Lighting...' YES/NO. If you click YES it exits out to desktop. If you click NO it just cycles back to the previous boxed message and so on...

gutted 😢

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Edit1:
Just tried 'Darius Gaiden' (DirectDraw) with no luck. Game did not crash and there
were no error boxes. It seems that the game took no notice of any DDraw hooks.
I also noticed the games .exe executed a loader instead of going straight into the game.

This made me think; what if there was another .exe even if hidden and I was right.
There was a file called 'Darius.bin' of about 3MB.
I renamed it to DariusG.exe and ran it. The game came up straight away!
I then configured DXGL to use that DariusG.exe instead.
I then ran DariusG.exe and everything worked fine so now I can use custom resolutions.

Interesting to note that this PC port of 'Darius Gaiden' appears to run at 50FPS. So, it
would be best to have monitor in a resolution of 50Hz or a multiple like 75Hz or 100Hz, etc... instead of 60Hz

Been using this for a while and from what I gather this utility is still very much in the 'preliminary stages'. I can really see the future potential though, once the functionality/usability gets more complete.

Correct me if I'm wrong; but it looks to me that DXGL output's to the same resolution that your desktop is in. I also noticed that DXGL is not compatible with all resolutions and crashes with no error messages. For example; sometimes does not like 1152x864.

Hopefully in the future, users will be able to manually specify what resolution DXGL will output.

Bumping this, it fixes Jane's Fighter Anthology's color issue (which usually requires explorer.exe to be terminated as the default solution), however seems the ddraw.dll mutes the sound, no sound at all as the side effect.

Do you think it will be possible to raise output resolution for old windows games with locked resolution?

Example: Typing of the dead (locked at 640x480)

Myloch wrote:

Do you think it will be possible to raise output resolution for old windows games with locked resolution?

Example: Typing of the dead (locked at 640x480)

My guess is that DXGL won't make it possible (and in most cases it isn't possible), but perhaps he will offer your choice of scaling algorithm and filters eventually.

To be certain, you should probably ask the author via his email form or forums, because he does not visit here (yet).

Your opinions about dxgl? I think it's the best general purpose wrapper (for ddraw at least), with dgvoodoo2 as a co-winner, which I find more compatible for direct3d games. I just love how latest Dxgl can crank up internal resolution for a lot of games to obtain really crisp output, compared to dgvoodoo2's blurry output. But I think direct3d still needs a lot of work: all old direct3d games I tried don't even start (crash to desktop)!

I think there's a bit of irony in having a DX->OGL wrapper for 'compatibility', seeing as in the early days of 3D acceleration, we had OGL->DX wrappers for compatibility, seeing as OGL support wasn't very widespread. And in fact, even today we still have this, in WebGL. All major browsers translate WebGL (essentially an OGL dialect) to Direct3D on Windows.