there is an add-on for plex on kodi, it works well

@Halvhjearne
That's the thing I didn't want to do, but...

So I saved all the data from my Pi, formatted the USB key, and installed a fresh version of retroPie: I was able to configure the controller.
Then I updated the system and RetroPie, tried again to configure the controller: it worked this time again.
I restored all the games now, and it's still working.
I don't know what was the problem, but now it's gone

Thank you all

Had a similar problem with an old Ipega GamePad. Pair with BlueTooth with some re-connect issues, but worked with jstest and evtest.

Adding the udev rule helped with emulationstation, but only the left joystick works in RetroArch.

Running RetroPie 4.5.1 with updates. Any suggestions?

@Efriim said in Sega 6 button controller mapping (with shoulders):

EDIT: Actually I don't know much about the different updates occured, apparently a man named Francois is the one who developed the strong Kronos branch. I think some of these updates have made it upstream(?) of yaba-sanshiro and thus reflect much better emulation.

devmiyax is the author of yabasanshiro, he forked it from yabause after getting some of his PR to yabause rejected (iirc), main features for this fork are dynarecs for arm/aarch64 cpus and a gles3 renderer => that's what you want on SBC & phones FCare (François) is the author of kronos, he forked it from yabasanshiro after getting some of his PR to yabasanshiro rejected, main features are a cached interpreter and a modern gl renderer => that's what you want on pc

@KN4THX said in Sega 6 button controller mapping (with shoulders):

That runs pretty good

The videos are using my libretro port of yabasanshiro, i would recommend using the standalone version instead : due to how standalone works, i couldn't get an important feature speed-wise (async rendering) to work in the libretro core.

Have you read the https://retropie.org.uk/docs/Spinners,-Trackballs,-Lightguns,-and-other-Mouse-Devices/ page ?

@zxardas Please add more info about your system, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first. What controller/gamepad are you using ?

@melbmatt50

Hmm...
bios.gg in the BIOS folder.

Try disabling threaded rendering in retroarch.
Launch run-command, make sure there are no setting that look awry, perhaps resolution; launch with verbose mode enabled, and try to get the log from /dev/shm/ posted to pastebin here.

@shavecat
editing the es_systems.cfg to remove ".iso" from the amiga console is one way. Below the <system>amiga</system> tags.
/etc/emulationstation/es_system.cfg
override at >
/opt/retropie/configs/all/es_systems.cfg

Changing the file name to a unix hidden file, then reflecting the changes in the all of .cue/.whd/.conf/gamelist.xml
./.Syndicate (1995)(PAL)(Track1)[!].iso

Or for the hidden tag to function in emulationstation. Kiosk or Kids mode must be enabled. I think:
ES Menu > System (or UI?) > gamelist mode (or ???) > Enable Kiosk mode.
↑ ↑ ↓ ↓ ← → ← → B A to exit kiosk mode.

Replacing the Mini vMac binary with version 36.04 completely fixed the issue.

If you too have this issue and you do not want to go the compiling route, then you can simply grab the binary here and replace your /opt/retropie/emulators/minivmac/minivmac with this one : https://www.macintoshrepository.org/25178-mini-vmac-for-raspberry-pi-retropie

Does anyone have any idea why the mapping for the up motion on joystick would be different for player 1 than player 2? This problem only occurs on ultimate mortal kombat. I'm sure the joysticks are wired properly.

RetroPie is not a standalone OS, the image for the Raspberry Pi it's based on Raspbian Lite, so if your sound works in Raspbian, then it should work in RetroPie.
For the error message you posted (lvl10: VolumeControl::init() - Failed to attach to default card!), try changing the sound settings in Emulationstation - change the Audio device to PCM and restart Emulationstation - see if you get the same error.

@mburry83

the way it says in the docs might not work anymore, i had to add it to grub or it would not accept it:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbhid.quirks=0x16c0:0x05e1:0x040"

@Spectreman - As @arcadez2003 pointed out it does work well on mame2003 and mame2003-plus using ROM moonwlkb the other [parent/clones] hang.

I've seen that there's a Python front-end for Mupen64 that has a GUI where you can select different cheats, but I'm guessing it just loads them before starting the emulator the same as the CLI you posted.

https://github.com/mupen64plus/mupen64plus-ui-python

@dabone Thanks! that worked!

OK, I hereby confirm that removing all the NULL characters from the /opt/retropie/configs/all/emulators.cfg file fixes the issue! Thanks!

Ok, so I just figured it out. For some reason my controller was player 2 so I switched it back to player one using https://www.google.com/amp/s/amp.reddit.com/r/RetroPie/comments/6003hk/switch_controller_player_number/ and it was a big help

Update 2:

What a rollercoaster!

So I made some guesses on the joystick ID (above), and got advmame to start long enough to let me map controls. I pulled the trigger, and found it was showing up as j5. I wiggled the gun around, and it showed up as j4. Armed with that knowledge, I went back into advmame-1.4.rc and updated those lines.

Back into duck hunt and... SUCCESS! Sort of. I had movement, and it didn't drift, but it also was clearly moving in 4 directions. Like a joystick.

So I went back to gunconf, set the gun for mouse mode, and went back into AdvMame. Nothing worked (which I expected), but I was able to do that mapping trick and learn that both buttons and movement was showing up as j6. I made the appropriate changes to the rc file, and.. nothing.

Buuuuut, I did learn something about how the rc files works, so I decided to throw caution to the wind and make some changes.

I went back into the rc and set it up this way again:

device_mouse raw device_raw_mousedev[0] /dev/input/mouse0 device_raw_mousedev[1] /dev/input/mouse1 device_raw_mousedev[2] /dev/input/mouse2 device_raw_mousedev[3] /dev/input/mouse3 device_raw_mousetype[0] ps2 device_raw_mousetype[1] ps2 device_raw_mousetype[2] ps2 device_raw_mousetype[3] ps2

I set the lightgun mapping back to "auto", and fired up duckhunt again, and it was a QUALIFIED SUCCESS!

The lightgun is now working (as in, it moves in the right direction at the right time), but there is clearly a calibration and/or sensitivity issue. The gun functions inside a very small area, which I suspect is about the resolution of duckhunt, rather than the resolution of the monitor.

I attempted to calibrate inside of duckhunt, but that's a frustrating experience since the crosshairs bounce all over the place, and I can only guess where I'm supposed to be aiming. Hardly ideal for what I'm trying to make happen here.

I am going to re-calibrate in 4:3 using gunconf, and then play with the sensitivity settings to see if I can get it to match up.