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 --- Bug Reports --- Site News

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


Author Topic: About daily use of frame_delay & vsync_offset controls (a knobs vs auto thread)  (Read 1850 times)

0 Members and 1 Guest are viewing this topic.


  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6620
  • Last login:Yesterday at 11:15:44 am
I think I've fixed the issue, the feature will be added to 0.205. This is the final behaviour:

- The frame delay slider is only saved if you change it from its 'default' value.
- By 'default' value, GM takes the one from the .ini files (remind the .ini priority hierarchy)
- E.g., if frame_delay=1 in mame.ini, the slider will show "1", and won't be saved unless you change it.
- If you change the default value, it'll be stored in the game's cfg.
- The slider will always have higher priority than command line or any .ini. It's done it this way to be coherent with the behaviour of the rest of sliders that do save currently in baseline (brightness, gamma, etc.).
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 or pasting it.

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