The NEW Build Your Own Arcade Controls
Software Support => GroovyMAME => Topic started by: Paradroid on August 31, 2018, 11:21:48 pm
-
Hi pals.
I'm trying to setup a cab using Windows 10 Pro version 1803 and an XFX HD 4350.
I was able to eventually install the driver (had to use Safe Mode otherwise it would always blue screen) and have installed modes using vmmaker.
No problems changing the desktop resolution on my CRT using vmmaker but I can't actually enter any of the modes to edit timings. When I try, the screen goes black for a few seconds and then switches back to the windowed arcade_osd view.
Has anyone else tried W10 1803 yet?
I'm using CRT Emudriver 2.0 (12.6)
Cheers,
Dale
-
There's a setting in 1803 called "focus assist" that has caused some issues with various emulators/games. Try disabling it.
-
Try disabling it.
Thanks for the tip. I'd already taken care of that so that's not it, unfortunately.
Interestingly, I can edit some modes (e.g. 2560 x 256) but not others (e.g. 320 x 240). Weird.
-
Bummer. I was hoping that was the fix. Unfortunately I don't know what else to try. Could it have something to do with the card being a 4000 series?
I had a lot of trouble with windows 10 and crt emudriver so I went back to 7.
-
I had a lot of trouble with windows 10 and crt emudriver so I went back to 7.
Yeah, there do seem to be a few quirks, hey?
However, I'd like to persist and hopefully get a decent build to update my W7 cabs with (upgrading to SSDs in the process).
-
I can't help with your issue but can share my experience with Win10x64 1803. (Setup: Intel i5 4690s CPU + Intel H87 Chipset + Radeon HD 4350 + LCD Monitor)
1) Like you I got the blue screen when installing CRT Emudriver 2.0 legacy. Thanks for the tip with Safe Mode. Now I could at least install the driver.
2) Despite running as Admin, GroovyMame somehow cannot write into the registry:
Switchres: saving system mode
Switchres: updating Failed saving registry entry DALDTMCRTBCD1920x1080x0x60
: error updating video timings
[snip]
Switchres: restoring Failed saving registry entry DALDTMCRTBCD1920x1080x0x60
It works with modeline_generation=0. Still trying to figure out what's wrong...
-
Calamity mention before that ArcadeOSD is legacy, and that it runs at all on Win10 is... not luck, but still lucky. No idea about the other issues.
-
Please make sure the driver that's installed is actually mine, check the digital signature of the file atikmdag.sys that's present in your system.
I haven't tested GroovyMAME nor the CRT Tools in 1803 yet. Arcade OSD uses DirectDraw, I've meant to modify it to use D3D since long, and it's time to do it finally. Could you check if there are DDraw related errors in the log that Arcade OSD creates?
Maybe part of the problem is that 12.6 is too old for 1803.
-
2) Despite running as Admin, GroovyMame somehow cannot write into the registry:
Switchres: saving system mode
Switchres: updating Failed saving registry entry DALDTMCRTBCD1920x1080x0x60
: error updating video timings
[snip]
Switchres: restoring Failed saving registry entry DALDTMCRTBCD1920x1080x0x60
It works with modeline_generation=0. Still trying to figure out what's wrong...
Housemusic, your issue is probably unrelated, and anyway I'd need a full log rather than a small bit to make any sense of it. You'd better open a separate thread and we can go on there.
-
Oh wait, is this the latest Win 10 update, the really big one? It totally removed my video drivers, so i had to reinstall crt_emudriver and setup VMM again - although i've done that so many times now it's pretty quick. I used V10, with the V12 tools, to keep the interlaced filter. It's far, far slower switching resolutions now.
EDIT: actually, no it didn't remove crt_emudriver, i don't think. It did remove all my video modes, though, and removed EDID emulation, so i had to plug in an LCD. Even then it would only start up in the crushed letterbox mode that normally happens when you don't disable fast startup, even when i kept restarting. Actually, i couldn't get out of that letterbox format. So i just re-installed.
-
It's far, far slower switching resolutions now.
Yes! I noticed this also. :(
I haven't had a chance to dig any further into this yet but it would be good to eventually understand where all the new pain points are.
-
It's far, far slower switching resolutions now.
That's sad. I don't think it's fixable.
With regards to "letterbox", assuming it's caused by a bios patched with ATOM-15, the new trick to restart the video driver (Win + Ctrl + Shift + B) should fix it.
-
It's far, far slower switching resolutions now.
That's sad. I don't think it's fixable.
With regards to "letterbox", assuming it's caused by a bios patched with ATOM-15, the new trick to restart the video driver (Win + Ctrl + Shift + B) should fix it.
Cheeers. TBH, when i think about it, i went to install the driver and it said it wasn't already installed, so the update probably *did* scrub the driver completely.
-
check the digital signature of the file atikmdag.sys that's present in your system.
Yes, I've confirmed this. The name 'Calamity' was right there once I located the file and checked the properties.
Arcade OSD uses DirectDraw, I've meant to modify it to use D3D since long, and it's time to do it finally. Could you check if there are DDraw related errors in the log that Arcade OSD creates?
The weird thing is that it's not totally broken: I can edit some modes but not others.
I couldn't find the log you mentioned: do I need to tell Arcade OSD to produce this somehow or is it always generated? If so, where can I find it?
-
I forgot Arcade OSD doesn't create a log, but if you press "D" it brings out the debug console where you can check if there are ddraw errors.