Build Your Own Arcade Controls Forum
Software Support => GroovyMAME => Topic started by: mamenewb100 on July 28, 2013, 10:48:01 pm
-
I'm having an issue in GroovyUME .149 when trying to play any TG16 game. Switchres thinks the TG16's Resolution is 1088x242. Even though online it says its supposed to be 256x240 or 256x224. The Reslist.txt file in VMMaker says it is supposed to use 336x224.
So I tried the old -v -md 4 > romname.txt and it doesn't recognize the -md command anymore, so I just used the -v command.
Also whenever I manually try to change to any other resolution in command line it says "resolution not available". Even though I do have them. I used to be able to manually change resolutions but most of the time it won't let me now.
-
Hi mamenewb100,
UME (MESS) only reports one resolution per system. Most systems are multi-resolution so this is a bit of a problem for SwitchRes. Fortunately GroovyMAME supports dynamic video mode change, so although not all resolutions are reported by the XML, GroovyUME can switch to them on real time when a certain game requests them. The problem is, however, that VMMaker can't create all of them beforehand because they're not reported in the XML, so chances are some of these resolutions are not available. The best solution if you're going to do a serious use of GroovyUME is to use magic resolutions. This will allow GroovyUME to virtually create any imaginable resolution on real time, so you don't have to care any more whether a certain resolutions is available or not.
Anyway, if you want to force GroovyMAME into picking a resolution, you must use the whole format: width x height @ refresh, e.g. 256x240@60
For the refresh, make sure to use the one reported by ArcadeOSD for that resolution.
-
Well that was a silly mistake. It wouldn't change resolutions because I was putting in double refresh, instead of original. Putting in @60 worked. Problem is that must be taking the 1088x256 resolution and compressing it to whatever I change the resolution to, because the picture is distorted when changing to any other resolution.
I didn't want to use magic resolutions because of the limit of 60 modelines it creates. When I can successfully use 80 with Hyperspin. I like to be able to modify existing modelines for emulators that don't have scaling and double refresh capabilities. But I mainly only need them for NES/SNES emulators because emulation of these systems is still poor in MESS. If those resolutions are kept in magic resolutions, then I probably don't need the extra modelines anyway.
-
Hi mamenewb100,
Inside vmmaker.ini, you can define independent methods for calculating modelines either for XML source (MAME/MESS) or manual source (ReslList.txt). So for instance, you can calculate your modelines in ReslList as "static", preserving the resolution & refresh for use with normal emulators, while converting anything that comes from XML to a magic mode table in the 1234 x height format. This way you have the best of both worlds.