@sleve_mcdichael Regarding non G-Net games, I was also trying to get Guardian Force (grdforce) and Soukyugurentai / Terra Diver (sokyugrt) to work in MAME 2010. I had poor results in 2016, and according to the following compatibility list 2010 should be able to run them at some capacity:

https://buildbot.libretro.com/compatibility_lists/cores/mame2010/mame2010.html

However when I try to load these games in 2010 the emulator freezes. These are stvbios games which seem to have mixed results in MAME. Yet some, such as Shienryu, will even run in MAME 2003-Plus. Just curious if anybody had success with those particular two.

Fbneo was updated to include the new accurate blitter delay function that MAME implemented. I haven't tested it on my Pi 4 yet, but from what I've read, it seems every CV1k game just needs CPU set to 50% now. I'll report back with my personal experience once I have a moment to test them.

https://github.com/libretro/FBNeo/commit/ba134d1c7f1d5bb57be7ec8e4056ad743c27353c

@roslof Thanks Roslof. I didn't know your spreadsheet already reflected an overclocked Pi.

Nothing here:
933e1f42-a621-4781-a983-41c06fdf791d-image.png

Here:
4dab9d7a-4e9d-426d-968a-bdf89ad1056d-image.png

@kenmetro said in Mame2010 or Mame2016 romset, which one should I keep?:

also have complete set of both Mame2010 and Mame2016. I don't want to keep both romset on my HDD and waste a lot of storage space for nothing. Could anyone suggest which romset should I keep for future use?

Keeping on-point, when possible, 2016 should trump 2010. For one thing, you could 7zip 2016 ROMsets and they'll work nicely. If you have any questions about compatibility, refer to my Arcade Recommendations List. You'll note that lr-fbneo is highly recommended, but you'll also note 2016 vs. 2010 compatibility for other ROMsets.

Hope this information is useful. It is also highly optimized, in case you just don't want multiple variations of some of your games. Or don't care about the 300+ Mahjong games, or gambling/casino games.

@mitu
I've never tried before to install 2016 before yesterday. I just recently finished getting the matching romset and wanted to give it a go.

I'm reading the PR and I see there is a potential fix but it hasn't been incorporated into libretro if I'm reading this right. I'll see if I can work out how the fix can be incorporated but I'm still learning the terminology workings of github.

@dankcushions Yep, that was actually helpful! Thank you!

Here's what I did to make it all work.

Your cheat.7z file has to be in this folder:
/home/pi/RetroPie/BIOS/mame2016/cheat

You can get the cheat file here:
https://github.com/libretro/mame2016-libretro/tree/master/metadata

Load up a game in lr-mame2016 like "Donkey Kong" for example, and then go into options and "Enable Cheats."

Screen Shot 2021-03-02 at 8.00.47 PM.png

You then need to RESTART the game (It does not say restart required in the options, but you have to restart) and then when you load up the game again, press TAB on the keyboard to get to the MAME Menu:

Screen Shot 2021-03-02 at 8.02.10 PM.png

And then you can be just like Billy Mitchell and cheat to your hearts desire! :P
Screen Shot 2021-03-02 at 8.02.43 PM.png

I've tested it in quite a few games as so far so good!

Thanks again for the help!

@jiryn said in Sound Issues with System 32 Games in MAME2003, 2010 and 2016 (Jurassic Park):

@barbudreadmon
Interesting, and I never use the controllers in bluetooth mood, they are always hard wired to the console with USBC
Never tried overclocking, just use it stock for the most part.

More interested in the best em ups anyways, but Jurassic Park was always a fav.

The Sega system 32 graphical rewrite circa MAME97-98 will always cause performance issues on lesser devices,
as @barbudreadmon suggested quite often this can cause skipping and or other sound issues. MAME2003
is one of the fastest cores and apart from that it uses the faster although slightly more imperfect system 32
video code from before the big rewrite i mentioned above.

So it might be your best bet to get the best performance on your device of choice and may sort your sound problems
when playing Jurassic Park it's worth a try at least.

@roslof
I have the exact same problem but I can't find mame 2016 folder under the bios folder on my image-virtualman 128gb arcade but it must be there as it is an option to use to open the rom file!
Any idea why, or where it could be??

M

@jiryn map dpad and analog to UI under input general.

Mame2003 does not natively support analog so you'll need to use analog to digital after mapping your dpad.

Mame2003-plus does natively support analog

Make sure you're mapping (up dpad and up analog) to everything you want to be able to use either on.

@GongStar the output of dmesg might be useful after the build fails. You are right there is nothing else in the log - I thought there might be something. Not sure of the issue if you have plenty of free space on card, and no overclock.

@Clyde

Your absolutely right Clyde , I should post a question about it here

Thank you also for the documentation for the mame 2016

Appreciate that ;)

I confirm the same issue. Also, controls appear unasigned under the retroarch quick menu option, unlike other mame versions (2003, 2010). The only way to remap controls is via the tab menu, but secondary mouse buttons do not work

I just tested with 1944.
Mame2010 saves the hiscore.
Mame2016 doesn't.
Unfortunately mame2010 only recognizes 1 joystick.
So it must be due to the mame2016 configuration (?).

@MBRetrocade said in HELP! Can’t alter MAME2016 controls:

@MBRetrocade said in HELP! Can’t alter MAME2016 controls:

Hello everyone, so all of the sudden I am getting —- in the control input slots in MAME2016 and MAME2003. These are also uneditable. I would really like to get some game controls configured, so any help would be extremely appreciated! Thank you

This is on Retroarch 1.8.5, and I did not see any error messages. I am just unable to change any of my controls suddenly. I also tried re-installing (assuming that I did something) from binary and it did not help. I did not update the system during this.

Here are my
Details:
Raspberry Pi 4B w/4GB ram, 64bit processor
Power Supply used: MODEL DCAR-RSP-3A5C, INPUT 100-240V AC, OUTPUT: 5.1V 3.5A
RetroPie version: Raspbian GNU/Linux 10 (buster) - Linux retropie 4.19.97-v7l+
Built From: RetroPie-Setup version: 4.6.1 (4464b474)
USB Devices connected: SNES controller, USB keyboard
Controller used: SNES controller, USB keyboard

Please note: I did switch to a PS2 USB controller during the process of going through my arcade games & configuring the emulators. It did let me change the controls at first and I did not update anything so I cannot understand why I am suddenly getting three dashes in the input slots - - -

Also note: Mame2003 works up I cannot go up down left or right.

SOLVED, a MAME 2016.rmp file was generated in
configs/arcade/mame2016 and over wrote my controls. I deleted the .rmp file and now I have my controls working again.

Hot Damn, it looks like its working, Thanks guys.....You are the best!!!!!!