Vmmaker - Dynamic modelines / Static modelines with GM and Retroarch - Help !

[totozero]

Hi mates,

Since Calamity is Vmmaker-maker (doh!), I figured I'd better post here for relevant advice.

Let's explain my issue : I'm trying to setup retroarch on my Astro City as I want to use runahead for genesis/snes cores with crt support.

As far as arcade is concerned, I already have a wonderfully working super res-GM setup and I want to keep it that way, as I have zero interest in running MAME with RA.

However from what I've read on the RA wiki (well... the relevant info is actually... scarce TBH), in order to use switchres with native or super resolutions, one must install static modelines to get correct refresh rate within emulation.

https://forums.libretro.com/t/15-khz-crt-documentation-wiki/15671

Maybe I'm missing a point but I don't get if it's possible to install dynamic and static modelines at the same time with vmmaker ?

Else do I have to install from vmmaker dynamic or native modelines whenever I want to switch from GM to RA and vice-versa, which seems a royal PITA ?

Any help/clarification on the matter would be gladly appreciated !

Cheers,
Xavier.

[Calamity]

Else do I have to install from vmmaker dynamic or native modelines whenever I want to switch from GM to RA and vice-versa, which seems a royal PITA ?

Yes, you can use both simultaneously. VMMaker uses a text file as input for the list of modes. Simply edit it manually and add all the modes you want. E.g. if you use the user_modes_super.ini as a starting point, add for instance 256x240@60, 320x240@60, etc. in it. Maybe rename it as user_modes_mixed.ini or something that allows you to revert to only-super if you want, then use that file as your mode list in order to generate the modes and you're done.

[totozero]

Hi Calamity, thanks for bumping in.

Yeah I've tried it and saw it was working with RA. Problem is now with Groovymame.

Let's say I've made a list containing :

Code: [Select]

## Desktop ##

 640 x 480 @ 60.000000 desktop

## Super resolutions ##

2560 x 240 @ 60.000000 super
2560 x 248 @ 60.000000 super
2560 x 256 @ 60.000000 super
2560 x 264 @ 60.000000 super
2560 x 272 @ 60.000000 super
2560 x 280 @ 60.000000 super
2560 x 288 @ 60.000000 super
2560 x 296 @ 60.000000 super
2560 x 304 @ 60.000000 super
2560 x 320 @ 60.000000 super
2560 x 336 @ 60.000000 super
2560 x 344 @ 60.000000 super
2560 x 352 @ 60.000000 super
2560 x 360 @ 60.000000 super
2560 x 368 @ 60.000000 super
2560 x 376 @ 60.000000 super
2560 x 384 @ 60.000000 super
2560 x 392 @ 60.000000 super
2560 x 400 @ 60.000000 super
2560 x 416 @ 60.000000 super
2560 x 432 @ 60.000000 super
2560 x 448 @ 60.000000 super
2560 x 464 @ 60.000000 super
2560 x 480 @ 60.000000 super
2560 x 496 @ 60.000000 super
2560 x 512 @ 59.000000 super
2560 x 544 @ 55.000000 super
2560 x 560 @ 54.000000 super
2560 x 768 @ 60.000000 super
2560 x 800 @ 60.000000 super

## Custom resolutions ##

640 x 240 @ 60.000000 NTSCp
512 x 240 @ 60.000000 NTSCp
368 x 240 @ 60.000000 NTSCp
320 x 240 @ 60.000000 NTSCp
256 x 240 @ 60.000000 NTSCp
Switchres ends up always picking the low resolution over the super resolution i.e I can't use super res with GM anymore, which causes centering issues on many arcade games.

I don't know how to make GM stick with super res and tell it not to use "normal" low res.

I'm using an HD4650, windows 7 x64 and crt emudriver 2.0 btw, not sure if it's relevant.

Don't know if it's a common issue or if you need a log file to see how is this happening.

Cheers,
Xavier.

[Calamity]

Switchres ends up always picking the low resolution over the super resolution i.e I can't use super res with GM anymore, which causes centering issues on many arcade games.

Simply set -resolution 2560x0 in mame.ini. Here, the zero acts as a wildcard.

[totozero]

Thanks mate,

I recently upgraded from an old version and I thought that new

Code: [Select]

super_width 2560 parameter had replaced the whole resolution setting, which I left on auto.

Cheers,
Xavier.