Forum Replies Created
-
AuthorPosts
-
01/19/2016 at 22:06 in reply to: xbox 360 wireless controller works in UI but not in any emulator #114442labelwhoreParticipant
http://elinux.org/RPi_Hardware#Power_Supply_Problems
That guide says it should be 700ma, but that’s wrong. For this project you NEED a 2 amp power supply, nothing less.
This is what I’m using:
This one looks identical, but would probably cause issues:
01/19/2016 at 21:59 in reply to: xbox 360 wireless controller works in UI but not in any emulator #114438labelwhoreParticipantI have a lot more things in mine that won’t be relevant to you, such as a mount command for a usb hard drive, but here’s what it should look like. This is what mine would look like with all the extra crap taken out.:
#!/bin/sh -e _IP=$(hostname -I) || true if [ "$_IP" ]; then printf "My IP address is %s\n" "$_IP" fi sudo chmod +x /dev/uinput "/opt/retropie/supplementary/xboxdrv/bin/xboxdrv" --daemon --detach --wid 0 --led 2 --deadzone 4000 --silent --trigger-as-button --next-controller --wid 1 --led 3 --deadzone 4000 --silent --trigger-as-button --dbus disabled --detach-kernel-driver exit 0
Just FYI, based on the controller light alone, I don’t think we can rule out a power issue.
01/19/2016 at 21:45 in reply to: xbox 360 wireless controller works in UI but not in any emulator #114436labelwhoreParticipantFirstly, exit 0 should be the very last line in rc.local, if it’s missing, add it.
The next thing I see that’s wrong is that you need either this:
"/opt/retropie/supplementary/xboxdrv/bin/xboxdrv" --daemon --detach --wid 0 --led 2 --deadzone 4000 --silent --trigger-as-button --next-controller --wid 1 --led 3 --deadzone 4000 --silent --trigger-as-button --dbus disabled --detach-kernel-driver
or this (not both):
xboxdrv --trigger-as-button --wid 0 --led 2 --deadzone 4000 --silent & sleep 1 xboxdrv --trigger-as-button --wid 1 --led 3 --deadzone 4000 --silent & sleep 1 xboxdrv --trigger-as-button --wid 2 --led 4 --deadzone 4000 --silent & sleep 1 xboxdrv --trigger-as-button --wid 3 --led 5 --deadzone 4000 --silent &
You may also need to add a line that says
rmmod xpad
before either of those lines.However, something else also strikes me as wrong. You say the lights on the controller never light up? not even once? If that’s true, we may be chasing our tails here. maybe it’s not a code issue at all, but a power issue. if you have a power supply that’s not up to par, the pi will act in all kinds of strange ways. this could be one of them.
How many amps is your power supply? it should be at least 2 amps. Test it with a multimeter if you have one. These micro USB power suppplies are typically really cheap, (crappy, made in china) and may say 2 amps, but actually be outputting 1.5.
01/19/2016 at 20:34 in reply to: xbox 360 wireless controller works in UI but not in any emulator #114431labelwhoreParticipantjust as aside, here what the xboxdrv line in rc.local look like for me:
"/opt/retropie/supplementary/xboxdrv/bin/xboxdrv" --daemon --detach --wid 0 --led 2 --deadzone 4000 --silent --trigger-as-button --next-controller --wid 1 --led 3 --deadzone 4000 --silent --trigger-as-button --dbus disabled --detach-kernel-driver
(actually, mine is slightly different, but the extra crap I’m using isn’t important here.)
labelwhoreParticipantI see an extra
default=”uae4arm”
in there. Assuming aue4all isn’t installed that file should look like this:uae4arm=”pushd /opt/retropie/emulators/uae4arm/; ./uae4arm -f %ROM%” default=”uae4arm”
labelwhoreParticipantthat’s actually makes a lot of sense. You need to be using UAE4ALL for this to work. It can be installed from the retropie_setup script.nvm, I got mixed up
labelwhoreParticipantit’s neogeo.zip and should be included with the roms. It goes in the rom folder, unlike with other emulators. Your roms need to stay zipped (the bios too).
To ensure you have he correct roms, walk through this guide:
https://github.com/retropie/RetroPie-Setup/wiki/Managing-ROMs
IMO it’s best to start with the latest rom set you can find (it helps to also have the rollback romset that matches the new set as well) and simply rebuild them to the version you need using that guide. You’ll always have the correct set that way. If you have both the roms and the rollback roms, you can build any version of MAME roms using clrmamepro.
I’ve done tons and tons of testing of MAME. by far the best one to use is lr-mame2003 with mame version .106 roms. You’ll get the largest number of roms to work that way.
labelwhoreParticipantIntructions are on the very bottom of that page. You’ll need to edit /home/pi/.reicast/emu.cfg
When I ran through the setup, the config had the correct hex values, but didn’t work. Manually typing them in fixed it for some reason. I have no idea why.
01/19/2016 at 18:26 in reply to: xbox 360 wireless controller works in UI but not in any emulator #114410labelwhoreParticipantThat means xboxdrv isn’t running. See what happens after running through setup option 1. You may simply need to add that additional line to kill xpad in rc.local.
Alternatively, you can add xpad to the blacklist, which will also keep it from running (and taking over your controller). To do that, add the following line to /etc/modprobe.d/blacklist.conf:
blacklist xpad
EDIT: wait, pos 1 blinking? that’s really odd. These should be the only options according to the xboxdrv manual.
Num Behavior
0 off
1 all blinking
2 1/top-left blink, then on
3 2/top-right blink, then on
4 3/bottom-left blink, then on
5 4/bottom-right blink, then on
6 1/top-left on
7 2/top-right on
8 3/bottom-left on
9 4/bottom-right on
10 rotate
11 blink
12 blink slower
13 rotate with two lights
14 blink
15 blink once01/19/2016 at 18:24 in reply to: xbox 360 wireless controller works in UI but not in any emulator #114407labelwhoreParticipantIn case the light is blinking constantly after you do method one, add this line directly before the xboxdrv lines in rc.local.
rmmod xpad
I haven’t needed that on retropie 3.3, but I did need it on earlier versions.
01/19/2016 at 18:21 in reply to: xbox 360 wireless controller works in UI but not in any emulator #114406labelwhoreParticipantThat would be wireless, so in the lines that you add to rc.local use “wid” instead of “id”. Although, I’m not sure it really makes a difference any more.
01/19/2016 at 18:07 in reply to: xbox 360 wireless controller works in UI but not in any emulator #114402labelwhoreParticipantNot neccessarily, xpad can pick up the xbox360 controller, which will make it work in ES but nowhere else.
Let me ask you this, when the controller is working for you in ES, is the light blinking constantly on the controller?
01/19/2016 at 18:04 in reply to: xbox 360 wireless controller works in UI but not in any emulator #114399labelwhoreParticipantno, if the automatic config isn’t working, you need to do this:
first run this (which should have been done by the automatic install, but running it again won’t hurt. )
sudo apt-get install xboxdrv
then edit rc.local to contain the following lines:
xboxdrv --trigger-as-button --wid 0 --led 2 --deadzone 4000 --silent & sleep 1 xboxdrv --trigger-as-button --wid 1 --led 3 --deadzone 4000 --silent & sleep 1 xboxdrv --trigger-as-button --wid 2 --led 4 --deadzone 4000 --silent & sleep 1 xboxdrv --trigger-as-button --wid 3 --led 5 --deadzone 4000 --silent &
I have tried method 3 on that page, but have not had any luck with it. Only option 1 or 2 have worked for me.
01/19/2016 at 17:47 in reply to: xbox 360 wireless controller works in UI but not in any emulator #114397labelwhoreParticipantWhen you go through this guide, if the automatic set up isn’t working, which manual method have you tried?
https://github.com/retropie/retropie-setup/wiki/Setting-up-the-XBox360-controller
01/19/2016 at 17:36 in reply to: xbox 360 wireless controller works in UI but not in any emulator #114394labelwhoreParticipantI’ve seen issues with a pi I configured for a friend who had a bunch of 3rd party wired xbox 360 controllers. None of them worked for him, even though it worked for me with a 1st party controller and an afterglow xbox 360 controller.
Which controller are you using? Is it a 1st party or afterglow controller? or something else?
(I believe the “Metallics” controllers from gamestop are the same as the afterglow ones.)
labelwhoreParticipantI made some assumptions while reading through the beebem documentation, and some other things about the BBC Micro and Archimedes. It’s probably not supposed to emulate that system as well. My testing certainly seems to indicate that. I was very thorough with the command line options.
labelwhoreParticipantIf it is that difficult, I’m going to go out on a limb and say it’s probably going to be up to you to get added to your pi yourself, since it doesn’t have anything to do with gaming. I say this as a dedicated synth enthusiast.
It seems that only software that can be easily added via script (and so not needing additional maintenance by the good folks here) get added to the install script.
If you’re successful, I for one would like to know what sort of issues you run into. I’ve got another raspberry pi project in the works based on pure data. It’d be cool to have a sequencer running on that pi as well.
labelwhoreParticipantIt’s pretty easy to add software to retropie yourself. Simply install it from command line, then add a a bash script to start it so that it shows up in the ports menu.
labelwhoreParticipantTake a look in the template for the kick rom location, then place the kick file where it’s expected.
That’s the only thing I did that’s not part of the instructions.
If it turns out that the KICK31.ROM is in the right place (and named correctly, it’s case sensitive) and it’s still not working, it’s possible that the game you’re trying to launch needs a different kick rom. While everything I have tried so far works with KICK31.ROM, I haven’t tested everything. You may want to try manually editing the .uae file to point to a different kick rom and see what happens.
labelwhoreParticipantI just popped in here to say thanks once again for this. It works with everything I’ve thrown at it so far.
labelwhoreParticipant[quote=114231]Please tell me how to make a button to turn on raspaberry 2?
[/quote]
Once you get that shutdown script running, the button doubles as a power on, and reset button. ;)labelwhoreParticipantI’ve got beebem working. No sound though, and controls are obviously not consistent.
I couldn’t get it to launch archimedes games at all though. If anyone figures that out, I’d love to hear how you did it.
labelwhoreParticipantI’m using 0.6.2, but from the post, it looks like there weren’t any updates for pi since 0.6.2.
From the update, it looks like there might be some joystick fixes coming soon though. I don’t know if that effects me, I’ve only done a very little bit of testing.
labelwhoreParticipantMan, this theme is gorgeous! Thanks for all your hard work!
There are like 50 systems on my pi, not all scraped, but still no white screen. I duplicated a couple systems from the theme to cover the additional ones I needed.
labelwhoreParticipant[quote=113968]/home/pi/RetroPie/roms/amiga/KICK31.ROM[/quote]
Oops! Now that you say this, I remember why I did what I did with the kick roms. I replaced the symlinks with the rom files because I wanted to keep the rom folder ‘clean’.
Sorry for the misdirection.
labelwhoreParticipantThat’s what it says, but I had the same problem until I moved the file. I suspected the symlink was not pointing to the right place, but just deleted it and placed the file where the symlink used to be. That worked for me.
I just started fresh on retropie 3.3 jessie. Previously, I hadn’t messed with Amiga much due to the funky way to launch roms. So I have no idea if prior versions worked out of the box or not.
labelwhoreParticipantPress F4
hit another buttton to keep Es from relaunching
type: cd /home/pi/RetroPie/roms/ports
hit enter
type: sudo chown pi:pi kodi.sh
hit enterTo explain what’s going on here:
‘cd /home/pi/RetroPie/roms/ports’ get you into the directory where kodi.sh resides
‘sudo’ gives the user you are currently logged in with root permissions, which we need to run the chown command.
‘chown’ is the command to change ownership of a file, in this case kodi.sh.
‘pi:pi’ refers to the pi user.
labelwhoreParticipantdid you put the BIOS in the BIOS folder?
labelwhoreParticipantThe trouble is, the emulator seems to be looking elsewhere for it. I’m not at home, so unfortunately I don’t have access to my pi to be able to say for sure where I put kick13.rom. If I remember correctly, I put it in the same folder as the emulator itself.
labelwhoreParticipantThe latest version of Kodi for Raspbian Wheezey is 14.2, I believe. I think you need Jessie for 15. However, I can confirm that it works flawlessly in Retropie 3.3 Jessie. (That’s the reason I started fresh recently with 3.3) The retropie script will install Kodi 14.2, then you need to upgrade to 15 once it’s installed.
So install Kodi from the experimental menu, then run these:
sudo apt-get update sudo apt-get upgrade
labelwhoreParticipantThat happened to me too at first, your kick13.rom is most likely in the wrong place. Moving it to where the emulator needs it fixed the issue. (I think I actually ended up deleting a symlink and placing it in the folder where the symlink was. IDK where the correct location is, because I had one in the BIOS folder all along.
labelwhoreParticipantlabelwhoreParticipantThere’s another thread around here that accomplishes this. I just did it on retropie 3.3 Jessie, and it works great.
labelwhoreParticipantThey’re working for me. This is a pretty funny thing to emulate, but I’m so glad somebody did it. Those game and watch games can fetch quite a few bucks second hand.
I had to do quite a bit of searching to find he right roms. The correct set seems to have been converted for some other emulator to .mgw files. They work great once you get the right set. Now only if they’d scrape correctly.
labelwhoreParticipantAs long as it’s optional. I’m using this as an opportunity to teach myself more about Linux, so I kind of like doing the leg work.
-
AuthorPosts