Build Your Own Arcade Controls Forum
Software Support => GroovyMAME => Topic started by: krick on August 21, 2014, 05:29:10 pm
-
I was wondering if it would be useful to identify each of the common use cases for GroovyMAME and then try to put together unique step-by-step setup guides for each case.
For example, off the top of my head, I can think of several scenarios that each require different setup steps for GroovyMAME:
1) Windows XP, arcade monitor, CRT_EmuDriver + compatible ATI card
2) Windows XP, arcade monitor, CRT_EmuDriver + compatible ATI card, Hyperspin frontend
3) Windows XP, arcade monitor, ArcadeVGA
4) Windows XP, LCD monitor
5) Windows XP, NTSC television
6) Windows 7, arcade monitor, CRT_EmuDriver + compatible ATI card
7) Windows 7, arcade monitor, CRT_EmuDriver + compatible ATI card, Hyperspin frontend
8) Windows 7, arcade monitor, ArcadeVGA
9) Windows 7, LCD monitor
10) Windows 7, NTSC television
There's other variations as well. I know some people are using Powerstrip for whatever reason.
Also, there's various types of arcade monitors beyond standard-res 15KHz models (dual/tri-sync) that require additional steps to set up properly.
I think it would be useful to try to identify all the possible setups and then create a flowchart showing the setup steps as well as creating individual customized setup guides for each scenario.
-
I was wondering if it would be useful to identify each of the common use cases for GroovyMAME and then try to put together unique step-by-step setup guides for each case.
I have envisioned something like that since long, but I never find the time/mood to get down to it. Believe me that the lack of documentation of GroovyMAME causes me endless frustration.
-
Is there a generic guide? Even just basic installation steps?
Also not always sure were to get the latest version of Groovymame and CRT_EmuDriver. Can someone point me in the right direction?
Thanks
-
Can someone point me in the right direction?
It can always be found in one of the sticky posts at the top of the forum: GroovyMAME/GroovyUME 0.154 - SwitchRes v0.015b (http://forum.arcadecontrols.com/index.php/topic,135823.0.html)
-
1) Done. http://forum.arcadeotaku.com/viewtopic.php?f=10&t=24216 (http://forum.arcadeotaku.com/viewtopic.php?f=10&t=24216)
2) Begone vile fiend.
3) Lets just poke out one eye while we're at it.
4) Unwashed heathens only.
5) USA! USA!
6) Okay, yeah this one needs doing. Once CRT_Emudriver is out of beta and VMMaker is fixed up with pending changes.
7) See (2)
8) See (3)
9) See (4)
10) See (5)
I jest. XP vs Windows 7 there is no difference, it's just a bit more awkward to install the driver in 7 and the compatible cards are a bit more limited. NTSC/PAL just require different monitor presets, and LCD doesn't even need CRT_Emudriver - it's just a two INI settings to set the monitor and aspect ratio. Unless you want to use HLSL, which at the moment is personal preference throughout.
Now that someone's made a start at the wiki I might take a poke at the real basic settings that need changing for the different scenarios. Even in the most complex case there are only a handful of changes that need to be made to VMMAKER.INI and MAME.INI for Groovy to work properly.
-
hi cools, thanks for your guide in the link above which i used when i first set up groovymame, but, is it correct about saying after installing crt_emudriver, that you shouldnt reboot? you say to run vmmaker before the reboot, i didnt think that would work correctly as you need to reboot first for the crt_emudriver registry changes to take effect? (or am i confused as usual, it's possible :))
-
is it correct about saying after installing crt_emudriver, that you shouldnt reboot? you say to run vmmaker before the reboot, i didnt think that would work correctly as you need to reboot first for the crt_emudriver registry changes to take effect?
I'm not sure about XP32, but with XP64, there's definitely an issue where the registry changes don't get applied correctly, even after rebooting. This requires you to run VMMaker later. However, I don't know if it matters if you run it before or after rebooting.
-
my setup was with xp64.
if i remember, i got a 'no suitable video card found' type of message when trying to run vmmaker, until i rebooted so that the crt_emudriver install could fully complete.
-
1) Done. http://forum.arcadeotaku.com/viewtopic.php?f=10&t=24216 (http://forum.arcadeotaku.com/viewtopic.php?f=10&t=24216)
For anyone using a clean install of XP x64, I recommend that you create a create a new CD/DVD image with 5eraph's Windows XP x64 post-SP2 Update Pack slipstreamed in. It will save you from having to do several hundred windows updates after installing windows.
http://www.ryanvm.net/forum/viewtopic.php?t=6400 (http://www.ryanvm.net/forum/viewtopic.php?t=6400)
-
I tested my instructions twice on different hardware and didn't need to reboot either time.
-
I tested my instructions twice on different hardware and didn't need to reboot either time.
if some others report the same problem i had maybe it is worth changing the line:
7. Run C:\VMMAKER\VMMAKER.EXE.
to
7. Run C:\VMMAKER\VMMAKER.EXE. If you get the message: No compatible video drive found (registry update disabled) reboot your computer and run VMMAKER.EXE again.
-
Regarding the need to restart the system after installing the driver and before running vmmaker:
VMMaker relies on the system recognizing the card already as \\.\DISPLAY1 (or \\.DISPLAY whatever number) in order to retrieve the registry key where the driver stores its settings.
If you're installing the driver for the first time, chances are that \\.\DISPLAY1 doesn't lead to the proper registry key before restarting the system.
For this reason, VMMaker won't be able to find a compatible driver, and will display the "No compatible video drive found (registry update disabled)".
Once you restart the system and the driver is loaded, it will map \\.\DISPLAY1 properly.
This is valid for XP. However when doing tests I've noticed that if I reinstall the driver in W7 for a second time, the system loads the driver without the need to restart. In this case, the device is mapped as \\.\DISPLAY7. Changing the display number in vmmaker.ini to this value makes it possible to run VMMaker before restarting. But despite this particular case, as a general rule you should restart the system before running VMMaker for the first time.
The fact that the specific package CRT Emudriver 9.3 x64 doesn't include the proper modelines and requires you to run VMMaker is a known silly bug I should have fixed long ago. I'll see if I can fix it and pass it to Krick for his ftp.