Software Support > GroovyMAME
Groovymame partially working without CRT Emudriver installed?
emubastard:
--- Quote from: Calamity on March 08, 2016, 11:58:21 am ---Very explanatory topic subject :)
Yes, GroovyMAME can work to some extent using default drivers. This is because the AMD ADL api is present and usable. What CRT Emudriver does is to patch the drivers so you can install more than 10 modelines, and changes take effect on the fly. It's a big long to explain: official drivers also support on the fly changes but the native function takes too long to complete to be usable, because it has to rebuild all the mode list etc. When you use -video d3d9ex the native call is used because we do need it to convert e.g. 640x480@60 into 640x480@30, so GroovyMAME is actually installing that new mode without any additional software. The issue with this is that it's slow, but if you have a short modelist as is your case you probably won't notice it.
You can also use VMMaker without CRT Emudriver to add other modes. However note the limit is 10 modes.
The reason why you're getting 50% speed for R-type is unclear. Please post a log so I can check.
--- End quote ---
Trying to wrap my head around this.
I use d3d9ex in order to get interlace working. It takes about 4 seconds from launch to execution of the rom when I play an interlaced game. I hear the USB beeps and boops like a device is being installed. That doesn't seem particularly bad to me.
Is it possible for groovymame to reserve one modeline to install all the various modes it will use on the fly for running games? Sure would be a nice option for using official drivers, especially if you have a mixed use system or cabinet that plays newer games as well. Maybe this could end the modeline limit issues by just continually reprogramming one modeline over and over as needed.
Personally I don't switch in an out of games every second so a 4 second delay isn't hurting me, and I'm using d3d9ex anyway.
Calamity:
--- Quote from: pakoman on March 11, 2016, 07:58:32 am ---I tried to add custom resolutions to plain Catalyst 15 drivers and so far:
-VMMaker allows to create an EDID and to add custom resolutions.
-Everything above 480 lines is rejected by the driver.
-It only allows around 5 custom modes
-I can only use the added custom modes if I use the TV as secondary screen extended desktop with the laptop built-in screen as main primary one. I can use them as desktop resolution so they work.
-If I only use the TV, the custom modes can’t be used. So there’s no point for mame, unless…
-If I use both screens and force Mame to use the 2nd screen with –screen //./DISPLAY 2. It actually runs on the 2nd screen –TV- but doesn’t pick the custom resolution even with –resolution 2560x512 command line.
Maybe it works better with something above 31khz, but that’s not quite interesting. Is this all can we achieve with plain drivers?
--- End quote ---
I guess you mean anything below 480 lines is rejected.
Anyway, this setup *should* work, even with regular drivers. I mean, having the VGA as \\.\DISPLAY2, and an emulated EDID on it, is the proper way to do it.
You need to be careful as to where you install the custom modes. Make sure you pick the right output (\\.\DISPLAY2). The method we use for HD 5000+ cards applies custom modes only to a given output, contrary to legacy cards where all custom modes got messed across different outputs. Note that right after installing an emulated edid, the display numbers are garbled. What I do is to exit the current session and log in again, this restores the usual numbers which are preserved on different sessions.
Besides, keep in mind turning given a mode from progressive to interlace is not possible unless you use -video d3d9ex, and even then it's not usually a good idea. This is the problem with the rtype log you posted, it's trying to produce an interlaced mode out of 720x480-31kHz. This is because you're using the native driver modes as a base. Instead, install proper 15 kHz modes on the VGA output, and just use them (assuming this is possible at all).
pakoman:
Thanks for your help, very kind as always :)
Yes, I mean below, my mistake.
It seems that the only modes I can add are 2560x512, 2560x496 and 2560x480 with super resolutions.
Or 768x512 id I use user_modes.ini.
All other modes are rejected.
With Catalyst 15 it makes no different having the HDMI connected or not and I tried all combinations of Outputs, so I guess this is the best I can achieve with plain drivers. So |I guess plain drivers are not best for this, unless you don't mind using interlaced resolutions -which I hate-.
ArcadeOSD and VMMaker work great, can emulate EDIDs and so...but the drivers are quite limited :(
Calamity:
--- Quote from: emubastard on March 12, 2016, 08:51:31 pm ---Is it possible for groovymame to reserve one modeline to install all the various modes it will use on the fly for running games?
--- End quote ---
That is not possible. What could be done is to create modes on the fly as required, then delete them on exit, as the Linux build do.
However the problem is, slowness aside, that regular Catalyst drivers won't accept modes below 480p. CRT Emudriver has a specific patch for this.
It'd be nice patched drivers wouldn't be required for this. Anyone from AMD reading this? Please remove the limitation. Anyway I don't think anyone apart from us is using this API.
pakoman:
--- Quote from: Calamity on March 16, 2016, 12:13:26 pm ---However the problem is, slowness aside, that regular Catalyst drivers won't accept modes below 480p. CRT Emudriver has a specific patch for this.
--- End quote ---
Is possible to easily patch other Catalyst versions or that's why you are using that specific version?