Thanks for all your help everyone. This has helped me learn a lot!

It looks like maybe I could mess with mame.ini if I want to try to configure this, though I haven’t quite yet determined if that works for lr-mame2003.

Anyway, seems like maybe the right way to play this particular game is with a different emulator anyway!

Thanks.

@mitu said in It's possible to integrate Samurai Showdown Perfect in Retropie?:

EDIT: samsh5fe titlescreen is still 'Samurai Showdown V Special', maybe it's not the 'perfect edition'.

Fullname of samsh5fe is "Samurai Shodown V Special (Final Edition, location test version)", it is indeed what some people refer to as "Perfect Edition". The word "Perfect" feels kinda counterfeit though, afaik they simply removed some gameplay elements from "Samurai Shodown V Special" (probably making the game more casual in the process) to make room for a story mode.

Except if you are using a non-merged romset, you'll probably need its parent samsh5sp.

@fcibx6r1un said in It's possible to integrate Samurai Showdown Perfect in Retropie?:

From what I understand the "Perfect" edition of the game is an emulator that runs the "Special" edition, and overlays it with new content. It isn't a self-contained ROM.

To be more precise, the commercial emulator from "Samurai Shodown Collection" uses some quirks to replace the title screen and to add an english translation to the story mode. FBNeo use the raw romset and doesn't have any of those quirks.

@sth3204 3rd party images are not supported in this forum.
You could either ask the seller of your bartop or install the official image from this site to get help.

How many games and files do you have on the external drive ?

Once EmulationStation creates the gamelists for each system, you can turn on the 'Parse Gamelists Only' option and on the next restart it will not re-scan the disc/folders.

@mitu Thanks a lot. I gave it a few tries, using only one Xinmo, changing usb ports, no overclocking, wiring differently but it keeps on assigning new gamepad numbers to my controllers.

With only two controllers connected through one Xinmo I can make some games work correctly nevertheless, but as soon as I connect all 4 it's a mess all over the place when I launch the first game.

@saccublenda Thanks. Don't have a keyboard plugged on my bartop so I will use the Quick menu / options solutions...I can live with that.

Thanks.

@mitu you are totally right. I switched to carbon and everything sounds great. Thanks for the help.

I added 6 new all_in1 plug & play consoles runned by xavix.cpp driver. They need frameskip = auto. With that, they run well. The list is in "Tutorial: Handheld and Plug & Play systems with MAME" is updated with those six consoles.

namcons1
namcons2
taitons1
taitons2
tak_geig
tomcpin

I add those plug & play in my gamelist.xml and downloaded images. see : https://drive.google.com/drive/folders/1bfuYF7Ij_dhNc9b8bVCS6I22XiEmP7rv?usp=sharing

For lr-mess, I added a gamelists and images for pockstat and updated svmu with more games.

The NesPI 4 SATA controller is affected by the issue detailed in https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=245931. There's a workaround for it, described in that topic.

@retrus said in My first retropie construct:

@zering
I want play as many games i can. From atari to PS1.

You won't need a fan and heat sinks for that. Those are only necessary if you overclock your Pi, and the Pi 4 can play all 8 and 16 bit consoles as well as most PS1 and even Arcade games up to the early 2000s perfectly fine with with its stock clock speed of 1.5 Ghz (maxmum, as the Pi will dynamically change its speed based on demand, running normally only at 600-800 Mhz). In my experience, N64 is 50:50 with stock speed, whereby a good number of games may require overclocking.

That said, my Pi 4 can handle moderate overclocking to 2 GHz in its passively cooled aluminium case Argon Neo. The same company offers another case called Argon One that can be cooled passively as well as actively with a fan. Both got many positive reviews.

@mitu i installed the latest precompiled binary from retropie setup script. but at least everything works now again and i do not even know what to do with this multitap thing.. not a funktion that i am missing now :)

@thorndike said in Joystick configuration on Atari Fight Stick:

First, when configuring the joystick through emulationstation which set of configuration options should I use to configure the joystick? The first set of directional inputs, or those farther down in the configuration menu?

You can use both to navigate EmulationStation, but most games expect something similar to a D-Pad (the first), so I'd use that.

I am currently using the first set of directional inputs but the joystick is very sensitive. If using the other directional inputs don't make a difference is there a way to adjust the sensitivity of the joystick?

You can try to increase the deadzone for the joystick using evdev-joystick , a command line utility.

@uberlumby said in Retro pie script update failure:

@retropieuser555 good tip I'm just trying to update emulation station I did it manually no big deal I'll reset once retroarch 1.9.0 gets supported officially.

Why did you get 1.9.0 same reason? I got it because retro achievements popping up would freeze on 1.8.8

I was trying to fix a problem I found recently where lots of lr-mupen64plus-next games have various achievements listed as "unsupported". Thought it might be due to using the older retroarch, but unfortunately it didn't fix it.

@jan_l said in How to prevent the controller configuration from popping up:

How to prevent the controller configuration from popping up when the new handle is inserted

RetroPie doesn't do that. If this is the same system as the one you've posted in https://retropie.org.uk/forum/topic/28624/, then you're not using RetroPie.

There's an overview of the audio settings which should be used with the Pi's on-board sound in this sticky. It's probably related to incorrect settings - see 1., once you have the correct audio settings, the message should disappear. it might be related to 1. Is the audio played directly by your TV or is it routed to the home cinema ? Any messages logged in /dev/shm/runcommand.log ? Are you using Steamlink over WiFi or wired ? What's the resolution of your display ?