Build Your Own Arcade Controls Forum

Software Support => GroovyMAME => Topic started by: bent98 on August 02, 2014, 02:43:08 pm

Title: Issues using new VMmaker 1.3c vs 1.3b
Post by: bent98 on August 02, 2014, 02:43:08 pm

I have enclosed both the 13b and c ini files and a copy of dkong run with both vmmakesrs. I ofcourse rebooted to ensure the vmmaker  took effect.,


You will notice 1.3c dkong did not produce the desired effect.

I made adjustment to the .ini to match up with my oldini file from a few years back. I think you helped me with it. Theres one spot that jumps out at me.


1.3b:

; Minimum resolution values (these will be used instead of lower values)

   XresMin = 184
   YresMin = 192

;   XresMin = 512
;   YresMin = 400

1.3c:

; Minimum resolution values (these will be used instead of lower values)

   XresMin_XML = 184
   YresMin_XML = 192
   YresRound_XML = 4

   XresMin_Custom = 512
   YresMin_Custom = 160
   YresRound_Custom = 0

Title: Re: Issues using new VMmaker 1.3c vs 1.3b
Post by: bent98 on August 02, 2014, 03:53:56 pm

It helps when you read. :)   This fixed the Hyperspin issue. ModeTableMethod_XML = 2.

Title: Re: Issues using new VMmaker 1.3c vs 1.3b
Post by: Calamity on August 03, 2014, 01:06:29 pm

Ok it looks like you already figured it out, anyway, as you see there are pairs of options with _custom and _xml endings. The _custom ones affect the resolutions taken from ReslList.txt, while the _xml ones affect the resolutions obtained from MAME xml.