[DavidBowman]

I did do that as well. I saw your replies on that bug report, so I figured maybe someone may know if I missed something simple. I guess not.

That’s not really a problem, and I definitely understand the beta nature of some of these emulators. Thanks for your help.

[DavidBowman]

Thank you for the reply, Herb. I appreciate your ongoing support of the project.

I should have mentioned that I tried that already. Unfortunately that doesn’t want to work for me. I tried that setting two ways (with and without quotes):

rewind_enable = "false"

and

rewind_enable = false

Both of those above the #include line. I also verified it was set through the Retroarch menu as well. Rebooted, no change.

It hangs on a black screen until I exit back to EmulationStation.

Did I miss something simple somewhere?

Thanks again.

[DavidBowman]

I didn’t read your updates. Disregard this post. :(

[DavidBowman]

W.O.W.!!

Can I buy one? I kid, but seriously: sell this to me!

[DavidBowman]

There’s an option in the RetroPie setup to give ownership of all of the ROM folders back to the pi user. Perhaps the folders themselves don’t have the proper permissions / ownership? I’m only guessing since I honestly don’t know for sure.

Maybe run a file system check on the SD card if possible?

Barring that, it might just be easier to backup all of your save files, ROMs, etc. to a safe location and reinstall everything (I know this isn’t anyone’s favorite exercise, but SD cards are screwy sometimes and starting clean does have its advantages).

Good luck! Maybe someone more knowledgeable than I can chime in.

[DavidBowman]

I would think you could do this with a script that detects the receiver has been plugged in (maybe polls lsusb?) and then in turn swaps (i.e. renames) controller config files (and maybe does the reverse upon disconnect).

I’m not enough of a linux guru to give you all the commands you’d need, but I know this is doable. There are probably more elegant ways of doing this than constantly polling something (memory, CPU use), but unfortunately I have to defer to the real experts that know how. Perhaps you could add it to the Emulation Station menu the way kodi has been added and just run it manually when you need to switch. Not as automated, but much easier, I’m sure.

Edit: Here’s a copy-paste for you:

This explains how you could run a script made by you (say /usr/local/my_script) when you plug a specific USB device.

1. First run lsusb to identify your device. Example:
$lsusb
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 040a:0576 Kodak Co.
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

2. After doing this you know that
– the vendor ID of your device is 040a
– the product ID of your device is 0576

3. Now is time to create your UDEV rule:

sudo nano /etc/udev/rules.d/85-my_rule.rules

4. And add the text

ACTION==”add”, SUBSYSTEM==”usb_device”, SYSFS{idVendor}==”040a”, SYSFS{idProduct}==”0576″, RUN+=”/usr/local/my_script”

Explanation:
When the usb_device product identified as 0576 of vendor 040a is added, run /usr/local/my_script
Note that ‘==’ and “!=” are comparators, while = and += are assingments

^ That will probably work, I would think.

[DavidBowman]

I’m not sure about the zero file size. Maybe it’s zero kilobytes because it’s less than a single kilobyte?

It might be a file permissions issue since this just happened to me with Mario Kart 64 (right after I got the final gold cup on the last 150cc circuit too!). I don’t know exactly how it happened (user error somewhere, I’m sure), but changing the file ownership back to the pi user fixed it.

Drop down to a terminal (F4, or ssh in) and change directory to your where your ROM and .SRM file are located, then do:

sudo chown pi [name of game].*

Let us know if that solves it.

[DavidBowman]

For ease of configuration, go with Microsoft OEM parts. Mine work without fuss, but the reviews on the non-OEM USB receivers are… well, they’re not great. They either work or they don’t, with the same reciever getting both kinds of reviews.

Oh, and they’re like $10 cheaper (at most) than the OEM receiver, so I’d just go OEM if you wanted the 360 controller (I personally find the 360 controller more comfortable than the dual shock ones, and I see far more “help me!” threads for getting bluetooth and the ps3/4 controllers to play nicely. YMMV).

[DavidBowman]

Press Control + C and you’ll get the prompt.

[DavidBowman]

[quote=104412]
If you have an Xbox 360 controller I can show you how I have mine set up, it works perfectly in the emulators in ES and in Kodi, I can switch back and forth
[/quote]

I for one would be interested in your solution if you’d be so kind as to share.

Thank you!

[DavidBowman]

Just saw this on the reddit sub:http://www.reddit.com/r/RetroPie/comments/3hcysl/bluetooth_adapter_for_360_controller/

So I guess it may work, but I stand by my original opinion that the cheap ones aren’t as good.

[DavidBowman]

I would just buy the official one. The generics may work, but you are greatly increasing the probability of having config problems, plus they are only of spotty reliability (check the reviews for 3 stars and below on those). For $7-9 less than the official adapter, I wouldn’t bother.

Just my opinion, but one formed around some general research on what works best “out of the box”, which is why I’m not going with a PS3 controller and bluetooth dongle. Lots more “help me” posts with those than the 360 controller, which seems to enjoy a more stable, preconfigured setup as a whole. I may be very wrong about that though as all the underlying software keeps getting better and better!

[Author]

Posts