Software Support > GroovyMAME
Updated driver for AMD APU (Radeon HD 6410D)?
Calamity:
Well, it would be great if you could test this for us.
The idea is to use your up-to-date drivers (Catalyst 11 or whatever) with your new hardware, and follow the 'magic' resolution route explained in this post:
http://forum.arcadecontrols.com/index.php?topic=110905.msg1209299#msg1209299
(of course get the latest GM instead of the one there)
In order to be able to install the modelines, you'll need to edit vmmaker.ini and enable the option 'AnyCatalyst'.
Then try GM with that, I can't guarantee anything, you can even blue-screen your system (if this happened, you may need to restart in safe mode and reinstall the video driver), but whatever the results this test will be really useful.
ahofle:
OK I'll give it a shot.
Can you explain how this works behind the scenes? Without the custom CRT_EMU driver, what would I be missing? I assume the hardcoded bogus 320x240 and 400x300 resolutions will still be there and won't allow me to have a true 15khz 320x240? How about emulators other than GM? Would I just not have any 15khz resolutions for those?
Calamity:
You're assuming right, but the 'magic' resolution hack should bypass the harcoded doublescan, as we're fooling the driver into thinking the resolution is 1234x instead of 320x or 400x, and thus it shouldn't trigger the doublescan flag. However we're using the right x value for the modeline data, as the driver doesn't check this!
On the other hand, the 60 modelines limitation is not a problem if we can produce nearly infinite modelines out a bunch of 16-20 wildcard resolutions (only the height is fixed). You can still use the extra space to produce normal modelines for the rest of emulators, adding them to ReslList.txt, just don't use 320x but 321x.
ahofle:
OK I ran vmmaker, but I don't think it did anything. After a reboot, I don't see any of the 1234x resolutions in arcadeOSD or windows. I've attached my ini file (renamed to txt). Let me know if you spot anything wrong in there. Here is the output from vmmaker:
-------------------------------------------------------------
:: VideoModeMaker :: - version 1.3b - by Calamity - 2008/2011
-------------------------------------------------------------
monitor_specs line ignored
Catalyst 0 found!
53 different video modes found.
Generating dynamic mode table... 29 redundant video modes found.
Reducing mode list... 0 video modes dropped.
24 modelines generated.
Finished. Press any key...
Calamity:
Oh sorry, I forgot to mention you have to enable 'UpdateRegistry' option too.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version