Main > Software Forum

Skip Startup Frames reborn as MAME Plugin

<< < (7/11) > >>

Sky25es:

--- Quote ---If you can post which games were and weren't working with vsync on, that might help Jakobud refine the plugin.
--- End quote ---

A couple of games with the issue:

88games
gaiden
galaxian
gradiusb
gradius2
pacman
galaga
salamand


--- Quote ---EDIT:  Both settings work and save properly in mainline MAME.

Both settings can be turned off in MAMEUI and stay off when you "F3" (Reset) or "Shift" + "F3" (Hard Reset), but they are not saved when you exit the game and restart.  As you mentioned, editing the options.cfg file does not make any difference.

There are definitely differences in LUA script handling between mainline and MAMEUI.  For example, the defenderlr plugin works in mainline, but errors out when you launch Defender or Stargate in MAMEUI.
--- End quote ---

As you said, there must definitely be some problem with MameUI...

PL1:
Asked Robbbert about it.  Hopefully he can provide some insight or advice.
https://github.com/Robbbert/mameui


Scott

PL1:
Robbbert explained why the MAME version check in the defenderlr plugin fails but the one in skipstartupframes plugin doesn't.

--- Quote ---The reason for that particular failure is because the version number is a number or a string in MAME, but only a string in MAMEUI. You'll note that MAMEUI's version number is 0.273.1, which is a not a number but can only be a string. MAME's version of 0.273 could be considered a number or a string, as needed.

--- End quote ---
There are other MAME forks that could return version numbers that would be a string, but not a number such as NegaMAME version "0.273-1".
- Maybe plugin authors can use the first 5 digits of the version to run the check -- not sure how to code that, though.   :dunno

No word yet on what could be causing the problem with the ssf "black out screen" or "mute audio" settings not saving on game exit with MAMEUI.


Scott
EDIT: Just got another update from Robbbert.

--- Quote ---After some investigation I found that the version in MAME is a string. LUA doesn't really care, so if it looks like a number then it can be abused to be a number. So authors should really treat it as a string. I've made a bunch of changes in MAMEUI so that LUA will give the short version (0.273), and so the shaders should work. Wait a few hours for it to build, then you can get it from github. (haven't tested it myself)

I need to update ARCADE64 and HBMAME with these changes as well, but that can wait.

--- End quote ---
EDIT2: Here's Aaron's version check code update for the defenderlr plugin.
It changes from this number check . . .

--- Code: ---if tonumber(emu.app_version()) >= 0.254 then

--- End code ---
. . . to this string check.

--- Code: ---if emu.app_version() >= "0.254" then

--- End code ---
https://github.com/AaronBPaden/defenderlr/commit/1897ee6c7bf7e997f629591ff84be1d5bd2417d4

PL1:
Did some more testing on the "black out screen" and "mute audio" settings not saving.

When you launch MAME or MAMEUI, both of these settings are always enabled.

These two settings can be changed while in a game, but they do not save like the other settings do.

With MAME, the settings will persist in any other game you launch until you exit MAME.

With MAMEUI, the settings will persist until you return to the MAMEUI game selection page. The settings will persist in MAMEUI only if you change games using the Select New System entry in the built-in MAME menu.

Even editing the plugin's options.cfg file does not allow you to disable these settings.

Shouldn't the default or custom values for these settings save somewhere like the options.cfg (for defaults) or ssf_custom.txt file? (for custom per-game settings)

I know it's an edge case, but picture a user that wants the plugin to work as usual for most games and wants to see the DECO Cassette countdown speeding by instead of a 13 second black screen so guests won't wonder if the system has crashed when those games launch. Should these settings be configurable on a per-game basis?


Scott
EDIT: Issue fixed in release v2.1.0.

Jakobud:
I am just getting caught up on this. I am investigating those settings not saving as well as the version check string/number thing.

Also in the future, if you have a bug report, it is helpful to report it here: https://github.com/Jakobud/skipstartupframes/issues

I will most likely see it sooner. Also some other good advantages to posting them on there so I can link fixes to the issues and link to lines of code etc.

Thanks!

Navigation

[0] Message Index

[#] Next page

[*] Previous page