Main Restorations Software Audio/Jukebox/MP3 Everything Else Buy/Sell/Trade
Project Announcements Monitor/Video GroovyMAME Merit/JVL Touchscreen Meet Up Retail Vendors
Driving & Racing Woodworking Software Support Forums Consoles Project Arcade Reviews
Automated Projects Artwork Frontend Support Forums Pinball Forum Discussion Old Boards
Raspberry Pi & Dev Board controls.dat Linux Miscellaneous Arcade Wiki Discussion Old Archives
Lightguns Arcade1Up Try the site in https mode Site News

Unread posts | New Replies | Recent posts | Rules | Chatroom | Wiki | File Repository | RSS | Submit news

  

Author Topic: Issues using new VMmaker 1.3c vs 1.3b  (Read 1699 times)

0 Members and 1 Guest are viewing this topic.

bent98

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 477
  • Last login:February 02, 2019, 03:35:00 pm
  • Hyperspin Moderator
Issues using new VMmaker 1.3c vs 1.3b
« 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

bent98

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 477
  • Last login:February 02, 2019, 03:35:00 pm
  • Hyperspin Moderator
Re: Issues using new VMmaker 1.3c vs 1.3b
« Reply #1 on: August 02, 2014, 03:53:56 pm »
It helps when you read. :)   This fixed the Hyperspin issue. ModeTableMethod_XML = 2.


Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 7466
  • Last login:August 08, 2025, 06:55:05 am
  • Quote me with care
Re: Issues using new VMmaker 1.3c vs 1.3b
« Reply #2 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.

Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead of pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi