Software Support > GroovyMAME
New CRT Emudriver/VMMaker/Arcade OSD download, documentation and discussion site
chinagreenelvis:
Perhaps someone here can help me figure this out.
The main reason I can't run Windows in Test Mode is because it inexplicably slows down the Steam Browser Protocol.
I automate Steam Windows using AHK and it relies on being able to run commands like
--- Code: ---explorer.exe steam://open/friends
--- End code ---
You can test this through a browser also:
steam://open/friends
I also need to rely on this protocol for launching some games and running a VR automation app I've coded. You can see what exists of the documentation here:
https://developer.valvesoftware.com/wiki/Steam_browser_protocol
The delay that Test Mode creates with this is maddening and I'm sure there is no way to reconcile it but I figured I may as well ask.
chinagreenelvis:
Alright, possibly ignore those last posts...
I didn't think it was possible and I don't know how I managed it, but I'm now able to use VMMaker to install custom resolutions to my HD 5450 without enabling Test Mode or installing CRTEmudriver.
Possibly its some combination of the atikmdag-patcher and having installed resolutions once while Test Mode was enabled?
I did the following:
1) let Windows 10 Update install the card drivers and CCC
2) used VMMaker to enable EDID emulation using a custom preset
3) restarted after enabling Test Mode
4) used VMMaker to install dynamic resolutions from a custom user_modes.ini
5) restarted after disabling Test Mode
6) saw that the custom resolutions remained accessible
7) used VMMaker to wipe the resolutions and then install dynamic super resolutions from a different user_modes.ini
8) saw that the modes installed successfully
So I'm apparently now fully able to use my main for use with RetroArch and switchres... No idea why this works now when it never worked before.
chinagreenelvis:
--- Quote from: chinagreenelvis on May 24, 2025, 01:21:00 pm ---Alright, possibly ignore those last posts...
I didn't think it was possible and I don't know how I managed it, but I'm now able to use VMMaker to install custom resolutions to my HD 5450 without enabling Test Mode or installing CRTEmudriver.
Possibly its some combination of the atikmdag-patcher and having installed resolutions once while Test Mode was enabled?
--- End quote ---
I can confirm after removing cards, wiping Windows monitor registry info, and using DDU for NVidia and ATI drivers then reinstalling everything that running atikmdag-patcher.exe allows VMMaker to install any number of low resolutions or super resolutions to the HD 5450 in Windows 10, all without booting into Test Mode or installing CRTEmudriver. The AMD driver installed by Windows Update is 15.201.1151.1008, if that makes any difference.
Again, I didn't know that this was possible and haven't seen any documentation that suggests this as an alternative. As far as I can tell, everything works perfectly, but just to be clear - has this been a known workaround? Am I missing something by not having the custom driver installed?
cloud79:
Hi everybody,
I've successfully configured my PC build to work with latest CRT EmuDrivers and VM Maker with my newly refurbished Sega New Net City Arcade Cabinet and CRT Monitor.
I'm using an AMD Radeon ATI R9 380X as GPU to force resolution Modelines that work great with GroovyMAME and SwitchRes.
Unfortunately, after several tests I made, I noticed the DISPLAY ID associated to the ATI card changes dinamically after every Windows restart/shutdown.
And this seems to conflict with GroovyMAME INI file where I statically set the OSD PER-WINDOW VIDEO OPTIONS screen value to the DISPLAY ID of the ATI Card.
This is something required in my configuration, since I'm using a dual monitor setup with dual GPU (one dedicated to the HD LCD and the other to the CRT with ATI Card).
It is possible to set the screen value into GroovyMAME INI file to "auto", but sometimes it is not able to lock the right GPU and raises an exception.
So, is there any way to force GroovyMAME to recognize the right ATI GPU after a Windows restart or to avoid the dynamic change of the DISPLAY ID value??
Thanks a lot in advance!
Calamity:
--- Quote from: cloud79 on August 08, 2025, 05:01:24 am ---So, is there any way to force GroovyMAME to recognize the right ATI GPU after a Windows restart or to avoid the dynamic change of the DISPLAY ID value??
--- End quote ---
The display ID changes when VMMaker restarts the video driver, typically after enabling edid emulation. Once you restart Windows the first time after that, the ID you get is the one that will be valid since then. So use that one to configure GroovyMAME with.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version