Dynaverse.net

Taldrenites => Dynaverse II Experiences => Topic started by: Bonk on June 13, 2009, 09:37:44 pm

Title: Possible fix for Vista Dynaverse
Post by: Bonk on June 13, 2009, 09:37:44 pm

Could this be it? So simple...

In your system directory make a copy of dplayx.dll and rename the copy to dplay.dll. That is all. Play OP.

Tested once only, I hope I haven't gotten people's hopes up but this looks pretty good.

Lemme go try again, it better work or I'm going to the bar for last call.

Title: Re: Possible fix for Vista Dynaverse
Post by: KBF-Crim on June 13, 2009, 09:44:20 pm

cool!

Title: Re: Possible fix for Vista Dynaverse
Post by: Bonk on June 13, 2009, 10:06:33 pm

OK, two other things:

Vista Basic Color Scheme (Not Aero)
Windows Firewall Off

and no video card driver "stretch to fit desktop" effects. (not sure if that is a factor - but it looks better)

With these settings two successful tests, no significant lag. Making third test...

It has fooled us before...

Title: Re: Possible fix for Vista Dynaverse
Post by: Bonk on June 13, 2009, 10:47:42 pm

Well not quite. Poop. Still getting the intermittent map movement lag. Seems better though. This is so elusive... I wonder what would happen if I just dropped that dx9 dplay.dll in... (famous last words...)

Title: Re: Possible fix for Vista Dynaverse
Post by: FCM_SFHQ_XC on June 14, 2009, 01:38:04 pm

what if you add in all the other tiny little tweaks we did to Vista before which showed some slight improvement in the performance of Vista?

Title: Re: Possible fix for Vista Dynaverse
Post by: Commander Maxillius on August 24, 2009, 02:05:39 am

Vista D2 fix:

Go buy a cheap old box at a garage sale/thrift store/surplus store and drop an old copy of windows on it.  98 will work fine if you can find a disk.

Title: Re: Possible fix for Vista Dynaverse
Post by: marstone on October 18, 2009, 12:19:23 pm

Bonk or anyone working on getting OP on Vista/7

Have you tried changing the setting in qsdebug.ini?  I found a part as follows:

;--------------------------------------------------------------------
;
;
[D3D]
debug=0   ; set this to 1 if you want to use hardware emulation layer (slow)

[Software3D]
debug=0   ; set this to 1 if you want to use GDI instead of DirectDraw when in software mode


It would appear that changing these flags you would switch from DirectX and use GDI instead so you wouldn't be having these DX10 issues.  With the newer machines the slower run times would be more then made up for by the speed increases of the past ten years.  So software emulation might be a usable path.

If you have seen this, sorry for wasting time. (don't have a system to test this out on so have to just throw it out here)