Reply 40 of 101, by jclampy
You may change Directx version Hook to" Directx1~6" and Emulation to "Primary Surface" in Dxwnd Option, it should work for most games. If not simply send a question to http://sourceforge.net/p/dxwnd/discussion/. Hope that help!
Hey cloudstr, thanks heaps that got the game into a window.
Now I'll have to test the framerate out.
I noticed you mentioned:
It seem that a new ver released today make a game faster than a first fix ver, weird , and enable ForceBltNoTearing make Dxwnd not work: "could not initialize directx" while an older version work well !
Could you please explain why mix this .dll with DXWind and do you need to rename the .dll?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Edit1:
Ok, can't get a FPS readout, not from FRAPS or a video driver tool.
It does feel kind of like the proper speed, but I got no readout so...
One thing I am notice is tearing in the scrolling. Turning VSync on
in my video driver almost got rid of it but not quite. Is this why you
were using this .dll with DXWind?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Edit2:
Yep, this .dll does clear up the 'tearing' issue I noticed with DXWind.
Unfortunately I still can't get a FPS readout with DXWind yet...
I'll investigate further...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Edit3:
Still can't get an FPS readout in DXWind yet.
I am trying to make a visual guestimate and reckon it is running a bit
slower than 71FPS. Maybe DXWind is capping it to 60FPS even when
using this .dll but I won't be sure without some solid proof.
Also I can confirm what cloudstr said in regards to new version of .dll;
enable ForceBltNoTearing make Dxwnd not work
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Edit4:
I tried using the old version of the .dll with DXWind to see if I could
see what 'enable ForceBltNoTearing' does and I couldn't see any
difference. I wonder if perhaps it wasn't actually working properly at
all in the older version and now it does. But it is DXWind's end that
does not like this new .dll using a now 'functional' 'ForceBltNoTearing'?
I mean, maybe the problem is not with the new version of .dll?
Just another way to look at it.