Software Support > GroovyMAME

Manually adding 321x240

(1/1)

ahofle:
I need to manually add a 321x240@60 resolution in vmmaker for some non-MAME emulators (and because windows overrides my 320x240 with a fake 31khz one).  I assume I just need to add the modeline to reslList.txt and rerun vmmaker?  I know a modeline was posted around here somewhere but I can't seem to find it.  I'm using the magic resolutions patch.

Calamity:

--- Quote from: ahofle on February 21, 2012, 01:09:57 am ---I need to manually add a 321x240@60 resolution in vmmaker for some non-MAME emulators (and because windows overrides my 320x240 with a fake 31khz one).

--- End quote ---

This shouldn't happen. Are you still using the patched drivers or trying with plain Catalyst?


--- Quote from: ahofle on February 21, 2012, 01:09:57 am --- I assume I just need to add the modeline to reslList.txt and rerun vmmaker?  I know a modeline was posted around here somewhere but I can't seem to find it.  I'm using the magic resolutions patch.

--- End quote ---

That won't work because x resolutions are rounded to 8 multiples by the modeline generator. Actually, the feature of using fake label numbers as 321, 322, etc. is reserved by the generator for the cases where it needs it (disambiguation of video modes with very close refresh rates), so you can't manually do it.

However, you can use Winmodelines to manually add that modeline. Make sure to use the 321 label for the numbers between quotations and that will do the trick.

ahofle:
I'm using the patched driver with the magic resolutions.  My reslList.txt does not contain a 320x240@60 resolution, only 320x240@50.  So it sort of makes sense that I don't have that resolution.  Do I just need to add 320x240@60 to reslList.txt and then rerun vmmaker?  I've attached my list as well as a screenshot of ArcadeOSD.

ahofle:
I changed the '50' to '60' in reslList.txt, ran vmmaker and rebooted and all is good now!  The fake 320x240 is gone!
Is the 320x240@50 a typo? 

Calamity:

--- Quote from: ahofle on February 21, 2012, 11:09:23 pm ---I changed the '50' to '60' in reslList.txt, ran vmmaker and rebooted and all is good now!  The fake 320x240 is gone!
Is the 320x240@50 a typo? 

--- End quote ---

I see. The problem was there was no 320x240@60 defined, so the 'fake' one was actually the default 320x240 mode defined by the driver.

The 320x240@50 was defined for PAL Megadrive games but I'll probably remove those in next release.

Navigation

[0] Message Index