@jmebd said in Can't get Kodi to run with Retropie 3.7:

I ended up ssh'ing into mine and "sudo apt-get remove kodi" then "sudo apt-get update", "sudo apt-get upgrade" then finally "sudo apt-get install kodi" and it finally let me boot to kodi but had that move to the left ordeal going on still with the kodi dashboard and freaking out acting like it exited out of kodi and reloaded it. Played wack-a-mole with a keyboard holding down the right cursor until I could get it timed right to push cursor down and was able to get into settings, input, and disabling the "joystick and gamepad" entry in kodi and now it's acting fine....just not with the 360 controller......BUT....I never did any manual keymapping (editing anything to set what keys did what because I didn't understand all of that yet).

So, the stuff above able to actually let me and others use the 360 controllers without any crazyness going on now?

Move your /home/pi/.kodi folder to "start fresh" and see if it isn't any problem with your current settings.

Also the problem with XBOX 360 controllers was already fixed. You just need to reinstall Kodi via the Experimental Menu.

ok thanks, got it!

So mine maybe just a timing and mis-config. I had some left over .cfg files from when I set up the controller via the USB cable. I wiped those out and all appears to working now. (Well almost. The controller doesn't work in any of the games.)

Pulled down a config from:
https://github.com/libretro/retroarch-joypad-autoconfig/blob/master/udev/8Bitdo-SNES30-GamePad-Bluetooth-Mode(START).cfg

Works.

You will need to wait until that version of the firmware is packaged up (Unless you want to risk using rpi-update)

@RetroTARDIS Raspian Wheezy is no longer supported, Please backup and perform a fresh install

I would do as it says.

@dankcushions said in Mame help:

@Meneer-Jansen you're going to make me link to the wiki again, aren't you? :) that answers all your questions: https://github.com/retropie/retropie-setup/wiki/Managing-ROMs

the full mame 0.78 romset is 8GB.

Ooops! Indeed al the info I need is there. Now all I have to do is to get RetroPie working again. It seems like my SD card has been corrupted for the n-th time (topic link).

Thanks @glennlake . I too am worried I might overheat my pi. I have heatsinks, but that is about it. I decided I will plug my Monitor into the control socket and the Pi into "Constant", speakers into the slaved sockets. I am going to install a power button onto the pi and the monitor has auto sleep mode. So when the pi is turned on the screen comes on and that triggers the speakers. When I turn off the pi, the tv goes into low power mode, shutting down the speakers. That's my plan anyway.

@dankcushions Ah thanks for looking into it already! It does add to the nostalgia for sure, hope it can be implemented at some stage :)

add "usbhid.quirks=0x289b:0x0002:0x040" (without quotes) to the end of the line in /boot/cmdline.txt. it will split the controller into two. Check out anything about the Xin-mo arcade controller to get more info, a lot of the same stuff applies

i have 4 controllers attached to all 4 ports my powered hub but i occasionally plug controllers into the pi itself (i have 1 spare USB on that), and it's fine. all the ports are the same AFAIK.

Great work :)

Hey Richard, got the same issue with the XBox360 wireless controllers only working in emulationstation menu and not ingame. Opened a thread about this not too long ago. The first controller I think is registering as the third or second one in emulationstation, even though the solid green light is showing it as the primary one. That is why the games won't respond. This is what I found from my experience. Still waiting for a solution though...

Thanks for your quick reply. That is definately not the answer I was looking for. Just got the adapter shipped from Ebay. But I will try it out on a windows computer to check it out.

@Ornitorick Ah, yes. The default Kodi action when you exit for the Raspberry Pi in a TV which has CEC, is to turn off the TV.
You can change to not turn off the TV where you said in System -> System -> Input Devices -> Pheriperals -> CEC and changed to not turn off the TV.

Also keep in mind that if you have the RPi powered by an USB port of the TV, with the default option, since the TV will be turned off, it will cut the energy to the RPi.

Thanks for the link wetriner - wish I had checked this earlier as I was able to resolve it just before checking the forum!

The method I followed appears slightly different. It took going to to the "/configs/all" directory editing the autoconfig.cfg file. Changed the setting on the the "mupen64plus_hotkeys" from 1 to 0. And then going to the mupen64plus.cfg file and changing the "joy mapping stop" to "J0B10". Ensuring to save the both files before exiting. I again was required to use the command lines as the file would not save remotely from windows.

I nearly have my controller working 100% across all emulators except for Dreamcast - just cannot find a solution to get trigger buttons working. :(

So I finally figured this out. Turns out I needed to add 'evdev' as a module in /etc/modules, and then everything is hunky dory.

Here's where I finally found my solution: https://github.com/adafruit/Adafruit-Retrogame/issues/21

Hopefully someone else will find this useful.

Here are a few games, where the entries are unfortunately wrong:
advance wars 1
advance wars 2
metroid fusion
metroid zero mission
pokemon ruby/saphire/emerald
naruto ninja council 1-3
final fantasy tactics advance
dragonball z: legacy of goku 1
wario land 4

so if you can save your save files (not "save state") please post the part of your game_config.txt file