VOGONS

Common searches


First post, by Good Ol' TarviS

User metadata
Rank Newbie
Rank
Newbie

Does anybody else have Windows 8.1? No matter which output or game or cycle settings I use, any game always slows down to a crawl (and seems to pulse slightly faster and then slightly slower)

The only exception is if the output is ddraw in window mode, or surface. It works fine in those, but it's not optimal because I'd prefer linear filtering especially for aspect correction.

direct3d mode in builds that use it also works perfectly smooth in Windows 8.1, but the only one that works is the one in Daum's build, and I'd rather use a cleaner build if possible.

Does anyone else have Windows 8.1 and have issues with general slowness or is it just me?

Reply 3 of 6, by ripsaw8080

User metadata
Rank DOSBox Author
Rank
DOSBox Author

As mentioned in the linked thread, the DWM service may be involved, and that certainly is part of Windows 8. However, Windows 8 presents some challenges in disabling DWM, but supposedly it can be done with tools like PSSuspend applied to the service that keeps restarting DWM after it is killed.

Reply 5 of 6, by Good Ol' TarviS

User metadata
Rank Newbie
Rank
Newbie

I can confirm DWM is not causing it.

I've suspended winlogon and killed DWM.exe and confirm that it stays closed, yet any output other than ddraw still runs slowly. Furthermore, DOSBOX runs like a dream on the same machine in Windows 7 even with DWM enabled.

I have confirmed that there are no AppCompatFlags set in the registry.

I have discovered that setting frameskip to 1 makes the game run at a perfectly stable rate, but of course choppier.
The problem is...the CPU is an i7 running TIE Fighter at 320x200, so it really shouldn't be necessary.

I'll try messing with drivers to see if that's the cause, but on my i7 Laptop with just the integrated Intel graphics the same thing happens. It's something Windows 8 specific that's causing this.

Are there any log files that could help figure out what's going on? There's nothing in stdout or stderr (blank) that suggests a problem.

Also, to clarify, it's not just general slowness, but like clockwork it gets periodically much slower (slow enough to see each frame being drawn from top to bottom) every second, and then back to "normal" (but still too slow) speed. ddraw and custom builds using direct3d outputs are the only outputs not affected, yet even ddraw is not viable because if the windowed/fullscreen resolution is any higher than 640x480 or so then it gets very slow as well, due to Windows 8's ddraw emulation.

EDIT: Okay, I figured it out! It's caused by Nvidia video drivers forcing vsync. It gets even worse if it's an Adaptive setting. So if anyone else has Windows 8 and a slow DOSBOX, turn that off.

Reply 6 of 6, by kolano

User metadata
Rank Oldbie
Rank
Oldbie
Good Ol' TarviS wrote:

EDIT: Okay, I figured it out! It's caused by Nvidia video drivers forcing vsync. It gets even worse if it's an Adaptive setting. So if anyone else has Windows 8 and a slow DOSBOX, turn that off.

Hrm, that's a shame, Adaptive Vsync had seemed to be working well for me (at least in Windows 7). Can you confirm a presumption I'm making from your posts? Specifically that Adaptive Vsync works fine under Windows 7, but doesn't under Windows 8. Or was it just that you were running different drivers under the different OSes?

Eyecandy: Turn your computer into an expensive lava lamp.