mame2003-plus: hundreds of new games, improved input, features, new bugs - now with runahead support

dankcushions

@Clyde haha, ok cool! it even says to restart in the option text ;)

Clyde

@dankcushions Yes, but there is a Restart entry in the Quick menu. I thought the text meant that one.

zenobiaflex

I am loving the new 2003 plus; so far, I am happy to report that the ROMs I have tried so far are all functioning much better than when I was mucking around with the original 2003. Having sound work in DK is really wonderful.
One thing I noticed is that the copyright warning that pops-up seems to be on by default. When I went into the retroarch-core-options.cfg file, I noticed this:

mame2003-plus-skip_disclaimer = "enabled"

mame2003-plus_skip_disclaimer = "disabled"

The second occurs several lines down, but additionally, the latter use an underscore after the word "plus" while the former uses a dash after plus. Now I am not sure which is correct. The file actually has the first few with a dash and the latter with an underscore (see below for a paste from the file)

mame2003-plus-dcs-speedhack = "enabled"
mame2003-plus-samples = "enabled"
mame2003-plus-skip_disclaimer = "enabled"
mame2003-plus_brightness = "1.0"
mame2003-plus_dcs_speedhack = "enabled"
mame2003-plus_dialsharexy = "disabled"
mame2003-plus_display_setup = "disabled"
mame2003-plus_enable_backdrop = "disabled"
mame2003-plus_four_way_emulation = "original"
.
.
.

Now I am not sure which is correct. I assume it is the dash, but the odd thing was that the file in my case showed it as enabled in the first case and disabled in the latter, but it seemed to be reading the latter. I just set all instances to enabled, but have not checked to see what works just yet. Anyone know which is correct or why the cfg file is variable?

markwkidd

@Clyde said in mame2003-plus: hundreds of new games, improved input, features, new bugs - now with runahead support:

@dankcushions Yes, but there is a Restart entry in the Quick menu. I thought the text meant that one.

Maybe the text should read "Resart core"... that seems like a good idea.

markwkidd

@zenobiaflex If it wouldn't cause you any particular issues, I would suggest deleting all of the mame2003-plus options in your retroarch-core-options.cfg and run the core again.

Earlier in its evolution there was a slight name change involving that dash/underscore character and for whatever reason you have some entries with the old name scheme still in your file.

When you clear them all you should only get the valid ones repopulated automatically.

markwkidd

@Clyde said in mame2003-plus: hundreds of new games, improved input, features, new bugs - now with runahead support:

@dankcushions Yes, but there is a Restart entry in the Quick menu. I thought the text meant that one.

That text in the core options now reads Restart core. Thanks.

UDb23

Anyone tried the new implementation of vectors WITH a retroarch overlay ?
Does it impact performance ?

markwkidd

@UDb23 said in mame2003-plus: hundreds of new games, improved input, features, new bugs - now with runahead support:

Anyone tried the new implementation of vectors WITH a retroarch overlay ?
Does it impact performance ?

nayslayer who authored the patch said they tested it with RetroArch overlays with no trouble. I don't think they were using an rpi but they were being sensitive to low power in all regards on the implementation

UDb23

@markwkidd thanks.
If I find time will do some testing tomorrow, both on performance and on best overlay size @1080p.

Riverstorm

@zenobiaflex said in mame2003-plus: hundreds of new games, improved input, features, new bugs - now with runahead support:

Now I am not sure which is correct

The underscore is correct. The same for the warnings which I had to add manually due to it not saving correctly in RGUI. Samples are a dash.

UDb23

@markwkidd
Updated from source lr-mame2003 (Retropie 4.4.2 on Pi3 b+, no overclock) and started testing new Vector support.
In Tempest for any multiplier over 2x (tried 3x and 4x) the game screen gets corrupted, meaning lines (vectors) are missing.
See picture below:

Tried with and without antialiasing. Restarted rom multiple times, still same issue.
Also tried restart from inside the RGUI menu.

dankcushions

@UDb23 what's your display resolution? can you take a shot of your video settings page?

UDb23

@dankcushions
1080p. Will get the settings images and post.

UDb23

@dankcushions
Here are the shots. Set to 3x multiplier. Game screen area seems to be the usual for core provided aspect ratio @ 1080p.

dankcushions

@UDb23 i noticed those sort of artefacts when i didn't increase my beamwidth corresponding to the scale. did you increase it? i think probably it should be automatic along with the scale...

also, note that 1080p would not cope with tempest at 3x, which is 900x1200, so you may get scaling artefacts there, also.

markwkidd

@dankcushions said in mame2003-plus: hundreds of new games, improved input, features, new bugs - now with runahead support:

also, note that 1080p would not cope with tempest at 3x, which is 900x1200, so you may get scaling artefacts there, alos.

I think that the combination of relatively small beam width plus RetroArch downscaling from 3x back to 1080 seems like a good hypothesis.

UDb23

@markwkidd @markwkidd
Thanks for the tips. Will try and let you know.

UDb23

@markwkidd
Further testing results:
Tempest
multiply 2x , beam width 2, antialias ON -> works fine (thanks !)
same as above but multiply 3x now (at least to me) looks even better than 2x.

Omega Race:
multiply 3x , beam width 2, antialias ON -> works fine

Note:
Apparently vector settings are "per core" and not "per game": when you edit vector settings in Omega Race you find them changed also in Tempest and viceversa.

Not sure but probably a "per game" option would be nice (or would it already work by saving game remap ?)

markwkidd

@UDb23 When you are in the RetroArch Core Options part of the Quick Menu, you should see a command at the top of the list with a name along the lines of Save game settings.

If you select that command, the core options you have altered will be applied only to the current game. Ironically I helped write the English name of that command, and that's the part I can't remember.

Edit: Thank you for your testing & especially for providing notes.

I'm tracking the idea of a "minimum bead width clamp", thanks @dankcushions . What would the rule be? Something like this?

/* after core options are all read from frontend) */
if ((int)beam_width < resolution multiplier)
  beam_width = (float)resolution_multiplier;

dankcushions

@markwkidd sounds good to me! i suppose maybe the beamwidth should be set before the multiplier (so beamwidth of 1 = 1 in 1x multiplier, and 2 in 2x multiplier), but that might involve digging into mame's vector code which probably isn't fun!