Groovymame 1942 -ps -monitor lcd -video d3d Make sure to set up your desktop resolution to the LCD's native resolution. This should work with any card supported by PowerStrip. Notice that you don't need CRT_Emudriver for this. So this is ideal for using with LCD monitors which actually support variable refresh rates (not all of them do). It only updates current desktop resolution by now, so it can be tweaked to any desired refresh rate on the fly. So this produces resolutions from 400 to 1024 vertical lines.Įxperimental PowerStrip support has been added. Notice that I set the virtual lines limit value to 800, as this has the side effect to limit the vertical minimum resolution to 400 (800/2). 1024 (active lines limit) limits the vertical resolution to the one accepted by the monitor. In order to cover its whole range I needed to use this line: I've been testing with a SVGA CRT monitor which supports up to 1280x1024.

Just set up your monitor properly, using a monitor_specs line if necessary, both in vmmaker.ini and mame.ini so VMMaker calculates the right resolutions for your monitor and GroovyMAME knows which ones to pick up. ) is performed automatically so you don't have to mess with options anymore. Selection of scaled resolutions by any factor (x2, x3. Remind to set this options to zero (vmmaker.ini) as we don't need to list roms data from MAME's xml anymore: Then run VMMaker to install the new resolutions and restart. Make sure you use the new ReslList.txt file. In order to setup your system for this method, download the new VMMaker 1.3b, edit vmmaker.ini as usual with your monitor type. It would be good to test the same for the other two combinations: GroovyMAME already checks this for us.īe aware I've only tested this with this two setups (which are my current ones): The other limitation is that the 'magic' resolution must be bigger than the one we want to create, otherwise the OS won't reserve enough memory for the mode. That's why, by default, I've implemented the most conservative method. If yres value doesn't match it will cause a serious crash in Catalyst 6.5. The reason is that it only works for Catalyst 9.3. You may be wondering why not to use dummy values for both xres and yres, so we could do with only one magic resolution. So we can create all resolutions used by MAME out of that list. Then, for instance, in order to create resolution 320x240 we use the 1234x240 resolution and recalculate it with the right values on the fly.

423 mame hyperspin