@pindapoe said in Pi 5 and MAME:

Hello,

In my experience, there's not a big speed difference between the Pi 3 and 4. However, I did notice a significant performance jump with the Pi 5. Do you think the Pi 5 could run a current version of MAME? Has anyone tried it?

Thanks for reading

Feel free to refer to my compatibility list and observe the Pi5 column for recommended emulator.
https://docs.google.com/spreadsheets/d/1Rq4shU1RUSdcc7cTVWeORMD-mcO6BwXwQ7TGw8f5_zw/

I just started to begin with DSi Emulation, using lr-LemonDS, and came to the point the tutorial ends: games will only start via the DSi-Menu, so "boot directly into rom" has to be disabled in the core-options.
Only difference: i have full access to the DSi-Roms in the /ROMS/DS-Folder from there and dont have to use prestuffed NAND-Files (would also be a fishy way imo, not the way it should work)

And this is an issue:
first of all on the official FAQ-Board it is recommended to keep this option at its default (=off/boot into rom), in special when the DSi-Bios is used.

Secondly the Retroachievements for DSi-Games only launch up when booting directly into the rom, you can see the widget, everythings fine.
Only problem: the screen keeps being white and silent.

Booting into menu works as mentioned, so the BIOS-Files are good for sure.
I can start all my games from there, but without Retroachievements Support, so i hope to find a way to boot directly into the game (as it should work :)).
I allready tinkered with further core-options, but had no luck.
If anyone has an idea it would be much appreciated.

It's a closed source 32bit app. You're on a 64bit OS, so it won't run

It works on the 2010 MAME core in Retroarch.

@nestor1924 said in Has anyone got Paprium working on Retropie?:

@barbudreadmon may that be the reason i cant make it pass level 2? I have a raspberry pi 3b+

I had totally forgotten about something, a 32-bits app normally can't allocate more than 2GB ram, so yeah running that genplus-gx on a rpi3 (hence probably with a 32-bits OS) is definitely a bad idea.

@Plantor07 been literally dealing with this for days with 8bitdo and Stadia. Tried this and it worked for me.

https://github.com/atar-axis/xpadneo#installation

And yes, in hope rather than expectation I did try changing:

config_version=3.6.0

to

config_version=5.7.1

It did not, of course, help, except that instead of dumping to a Workbench 1.3 "insert disk" screen, the game now dumped to a Workbench 1.3 "insert disk" screen in the wrong aspect ratio.

@barbudreadmon
Sorry, when I said I got both monitors working, I meant that Retropie was displaying on both. The left monitor has the game, the right monitor was displaying scripts. I just can’t get the actual game screen to display over 2 monitors. No game play on the monitor on the right even though Retropie seems to be recognizing it.

Thanks!

@mitu thank you man!
you are great! ( as always....))

Well, the OP should just move to MAME current tbh, not only it has support for TATE in both directions, but it probably also has better support for cocktail mode (i highly doubt all cocktail fixes from the past 22 years were backported to MAME2003+).

As for FBNeo, it is not suitable at all for cocktail setups : some games had their 2P mode and cocktail mode tied together, and ended up being un-cocktail-ified so that 2 players could play them without requiring a cocktail setup.

@mitu

I’ve tinkered with clrmamepro before but my results kind of sucked with it. The last time I had to do any of this was with the good tools way back in the original Xbox one days.

Any direction for a good tutorial on how to use Clrmamepro the proper way as I obviously had no idea what I was doing even tho I followed a guide lol.

Any other noob friendly sorting by .dat tool recommendations would also be appreciated, like I said it’s been a long long time since I’ve had to do this or anything like it and things appear to have come leaps and bounds since then

neither of these things (permissions or starting clean) seemed to resolve. I also @ByteThis did not seem to rectify this by only configuring player 1 (but good idea) With a clean install and remapping all the input settings I am getting to where the select and start button only work in the retropie menu (scrolling diffrent consoles exploring settings etc.... But when I launch a rom NONE of the bottons work.

I ran some more jstest output today....

davis@raspberrypi:~ $ jstest --normal /dev/input**/js0**
Driver version is 2.1.0.
Joystick (DragonRise Inc. Generic USB Joystick ) has 7 axes (X, Y, Z, Rx, Rz, Hat0X, Hat0Y)
and 12 buttons (Trigger, ThumbBtn, ThumbBtn2, TopBtn, TopBtn2, PinkieBtn, BaseBtn, BaseBtn2, BaseBtn3, BaseBtn4, BaseBtn5, BaseBtn6).
Testing ... (interrupt to exit)
Axes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:off 10:off 11:off

davis@raspberrypi:~ $ jstest --normal /dev/input**/js1**
Driver version is 2.1.0.
Joystick (DragonRise Inc. Generic USB Joystick ) has 7 axes (X, Y, Z, Rx, Rz, Hat0X, Hat0Y)
and 12 buttons (Trigger, ThumbBtn, ThumbBtn2, TopBtn, TopBtn2, PinkieBtn, BaseBtn, BaseBtn2, BaseBtn3, BaseBtn4, BaseBtn5, BaseBtn6).
Testing ... (interrupt to exit)
Axes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:off 10:off 11:off

So it sees both controllers, but does not detect any button or axis input events. I think It is time to just replace them. Ive had them over a year and the more I think about it the more I think I possibly damaged these things. They used to be mounted in a metal cabinet and the opening I cutout for the control panel was very tight. (see attached called "old") old.jpg

New cabinet.......

new.jpg

I think its time to just replace the usb encoders.

Thank you!!!