@drog1998 There might have been a misunderstanding about my suggestions, they were to either :

use a recent version of retroarch with the "Core provided" aspect ratio (aspect_ratio_index = 22) which is the default and recommended value if you are stuck with an older version of retroarch, use mame's TATE mode if it's available in mame2010 (instead of manually rotating through Setting > Video > Output > Video Rotation) if you are stuck with an older version of retroarch and TATE mode is not available, set the aspect ratio manually to 3:4 (alongside the manual rotation from Setting > Video > Output > Video Rotation)

If setting the aspect ratio manually to 640:480 (which is equal to 4:3) ends up with retroarch displaying it as 3:4, then you are using a recent version of retroarch (older retroarch wouldn't rotate it to 3:4 automatically, which is the bug i mentioned).
In that case, my recommendation is to let the core decide the correct aspect ratio by using "Core provided". The problem with enforcing an aspect ratio as you are doing is that some games are not meant to be played with a 4:3 (rotated to 3:4 or not) aspect ratio.

The only remap I saw was for saves. Here is my runcommand.log file:
https://pastebin.com/7v67SJe0

the last line of the file (shown below) repeats well over a thousand times but I cut almost all of them out of the log file i put on pastebin for sanity's sake.
[libretro INFO] [MAME 2010] 'maincpu' (FFA649F0)[libretro INFO] [MAME 2010] (no context): unmapped program memory word write to 01D01070 = 0000 & FFFF

Thanks!

@mitu yes, you are right

@lamaman1971 Aside from MAME2003+, MAME cores have a very shallow libretro implementation preventing some stuff from working properly, which is why it's recommended to prefer MAME2003+ or FBNeo with the appropriate romsets if the game you are trying to play is supported.

You might be able to force the values you want by directly editing MAME config files, but i wouldn't be able to help with the details, and i don't recommend asking the MAME team for help about this.

@bollwerk said in MAME 1G1R/ No FIller dat for Arcade Roms:

Be forewarned - with some arcade games, one clone works better than the original/main.

Indeed, see these lists for examples:

https://github.com/superjamie/lazyweb/wiki/MAME-Clones-Worth-Playing https://hyperspin-fe.com/forums/topic/406-mame-clones-worth-playing-a-complete-hopefully-list/

Hi we wrote a complete guide on how to setup both a spinner and a trackball at the same time, so that the configurations are persistent and will apply to a whole game folder.
The idea is to set up a default retroarch config for mame/fbneo that will configure one of these devices as the default mouse (for example, the trackball), and create then just a file for rom folders that will be spinner specific.

For example, you have a roms/mame folder -> all games in there will work with the trackball by default, thanks to the global default config. Then you have roms/mame/spinner then for this folder, you will have to generate a retroarch "content configuration file" that will apply just for this folder, and set the mouse_index to the one of the spinner.

Trap: the retroarch menu will not let you save mouse_index configs, but will create the config files. You will have to add manually a line with player1_mouse_index = 2 for example...

We wrote a detailed guide (in french, use deepl.com to translate) with screenshots, etc. And we use it on several Retropie arcade cabinet that we built, that have both trackball and spinner in the control panel.

Trackball and Spinner persistent configuration guide HOWTO (Google Doc, french)

alt text
alt text

I 'solved' it by adjusting the controls in the RGUI. I just remapped the option of test menu to a coin insert since I can't remap it to another key. Not a real solution but for me in this case an acceptable workaround.

@lupin it may well be a generic thing that would affect the official retropie image also but they are not supported here because we don't know what has changed under the hood, and also do not want to encourage the distribution of illegal material under the retropie name, etc. the image maker calling it 'official' is particularly egregious...

@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.

@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.

@kounabi22
Meh...
I'll stick with a permanent preference for the PS2 version.
It's a game from 2000, yet the Graphics are The Tip of Everest!
Too bad PS2 Emulation is a train-wreck that's yet to be cleared up.

@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.

@escc1986 this topic was already posted in 2017, https://github.com/libretro/mame2010-libretro/issues/38

You'll find MAME 2010 in the "optional" packages in RetroPie setup. It isn't installed ex-factory.

@McJones9631 https://retropie.org.uk/docs/Updating-RetroPie/#updatinginstalling-individual-packages

it's in the "optional" section

@Darksavior said in Mame 2015:

I'm not sure how well system16/18 is emulated in fbneo

Afaik system16 is fine, system18 is a different matter (among other things, i kinda remember there are tile priority issues) and would require a major rewrite to be glitch-free.