Interlaced resolutions are slow in Win10 and Win8 but not in Win7

[R-Typer]

Hello!!!

I have a working groovymame 0.168 setup in windows 7 x64 and everything works just perfect!

I have decided to move to win8.1 and/or win 10 just to gain extra speed in pcsx2 (playstation emulator). CrtEmu drivers installed perfectly and everything works just fine in Win8.1 and Win10 except for the games that use interlaced resolutions.

For example all vertical games, Like DoDonPachi or CrackDown etc. They seem to be slowed down and sound is being distorted. It's same on both Win 8.1 and Win 10.

I have read there is an issue with ddraw and interlaced resolutions. Could this be it? If so how is it possible that it works just fine in Win7?

I have installed latest CrtEmu drivers for HD4850, have latest groovymame 0.168 build, super resolutions are enabled, resolution 2560x0 and cleanstretch 2 added to mame.ini and so on. As I said, it works perfectly in Win7.

Any hints on how to make interlaced resolutions work on Win 10?

Thanks in advance!!!

[Calamity]

I have read there is an issue with ddraw and interlaced resolutions. Could this be it? If so how is it possible that it works just fine in Win7?

That was a different issue: ddraw crashing when switching between interlaced and progressive modes. It's was fixed in GroovyMAME long ago.

The issue you're seeing is specific to Windows 8 and above, and it's the reason why GM is not yet fully supported for those systems. However, I recently found a workaround that kind of works. It requires installing the Microsoft Application Compatibility Toolkit and enabling NoGDIHWAcceleration for the GroovyMAME executable.

It's an straightforward process once you know what to do, but better follow this step-by-step guide (just do the same they're doing there but for the GM executable):

http://steamcommunity.com/sharedfiles/filedetails/?id=188843066

Beware this is only for Windows 8 / 10. Don't use this with 7. It's not perfect however: if you bring out the menu or the speed percent the speed will drop again.

Another approach is to always force -video direct3d per game, combined with -frame_delay, and possibly -vsync_offset to remove stating tearing.

[R-Typer]

That's great! Thank you Calamity!!!