To me it sounds like a strange thing that ddraw is slower than even overlay, considering it's a hardware-accelerated mode. I've tested it only in Build engine games, but surely this shouldn't be the case? I see plenty of people recommending ddraw as the fastest output mode, but in my case it isn't...
What OS are you running? I think ddraw is gutted on newer versions of Windows.
W7 64-bit, actually. This might be the reason.
ddraw should be faster than surface. If you scale the display output for the games (normal2x, normal3x etc.), ddraw scaling is offloaded to HW. If you don't scale, then ddraw is on-par with surface. But, modern CPUs do move pixels quite fast these days. Perhaps, the diff is negligible. On older/slower retro level HW, ddraw/overlay has significantly lower CPU usage compared to surface, and the CPU cycles saved can be put into increasing DOSBox cycles.
Actually normal2x is no longer hardware scaled for some time now. It would be blurry if it would be hw scaled...
Tried playing with the "fulldouble" setting by chance?
wrote:Tried playing with the "fulldouble" setting by chance?
Yep, I always do.
