[labelwhore]

I recently started fresh with retropie 3.3, so I have to go through this again, sadly. Reicast was working perfectly for me previously.

I tried what was suggested above; adding the hex values to controller_XboxGamepad(userspacedriver).cfg. That fixed most of my buttons, but the start button still does not work.

here’s my controller_XboxGamepad(userspacedriver).cfg:

[emulator]
mapping_name = Xbox Gamepad (userspace driver)
btn_escape = 0x13a

[dreamcast]
btn_a = 0x130 
btn_b = 0x131 
btn_c = 0x136 
btn_d = 0x137 
btn_x = 0x133 
btn_y = 0x134 
btn_z = 0x13d 
btn_start = 0x13b
axis_x = 0x00 
axis_y = 0x01 
axis_trigger_left = 0x0a 
axis_trigger_right = 0x09 

[compat]
axis_dpad1_x = 0x10
axis_dpad1_y = 0x11
axis_dpad2_x =
axis_dpad2_y =
axis_x_inverted = no
axis_y_inverted = no
axis_trigger_left_inverted =
axis_trigger_right_inverted =
axis_dpad1_y_inverted = no
axis_dpad1_x_inverted = no

[labelwhore]

You will end up with problems with your SD card, trust me. I’ve killed a few that way. However, you don’t need a mausberry circuit if you have a soldering iron.

This works well:
http://iot-projects.com/index.php?id=raspberry-pi-shutdown-button

[labelwhore]

Reicast is very playable, but not every game will work.

[labelwhore]

This game doesn’t work well in reicast either btw. I can get it to work for a few mins, but then the screen will go black.

[labelwhore]

Yes, they would have to be built to run on the PI. A quick google search tells me that hasn’t happened yet.

[labelwhore]

^^ it ended up being my roms. I don’t know what happened, but new roms fixed it.

[labelwhore]

I’m having this issue with the latest image. My roms worked previously (on 2.6), so I don’t think it’s a rom or BIOS issue.

Sorry for the necro post, but I want to help keep the forums clean. :P

[labelwhore]

My understanding is that 15.1 is the last release for wheezy. Retropie uses wheezy.

[labelwhore]

Either way, how’s this running in a Pi2? Is it pretty smooth?

There seemed to have been a lot of issues when i started watching that thread i linked to.

[labelwhore]

does PPSSPP include all of the latest tweaks? https://github.com/hrydgard/ppsspp/issues/7479#issuecomment-152888850

Did you get it working? and if so, how well?

[labelwhore]

My earlier post was slightly wrong, the resistor I’m using is between the GPIO pin and 3.3v. I just double checked.

[labelwhore]

The resistor value actually doesn’t matter that much for the shutdown circuit. Just about any resistor will work. I think I used 220 Ohm, but I just picked it out of a bag of random resistors. I’m using just a single resistor between the GPIO pin and ground 3.3v. Both the reset button and this simple shutdown circuit do work on the PI2, I’m using both.

[labelwhore]

The first one. It’s pixel art, it should be pixelated.

[labelwhore]

I swapped the BG on the game select screen and the colors in the colorpi theme to match what I have in kodi. After that it looks fantastic!

[labelwhore]

[quote=104287]mess is a configuration nightmare. outside of the colecovision (which hopefully in the future will be supported with lr-bluemsx) which systems would it offer that retropie doesn’t already have?

[/quote]

So what you’re saying is Mess is a mess?

lol, sorry. Somebody had to do it.

[labelwhore]

Emulationstation absolutely does have the capability for sounds when scrolling through the list of games. I had it working on 2.3, but have a different theme on 3.0 and haven’t figured out how to make sounds work with the new theme.

All I had to do for 2.3 was to name name my .wav file as coin.wav and drop it into a folder with the rest of the theme files.

*Edit: here are some details that should help get them working. http://emulationstation.org/forum/index.php?topic=6981.msg8745#msg8745

[labelwhore]

I’ve just been using a momentary switch and a pull up resistor connected to a couple unused pins on the GPIO, this triggers a script that issues the shutdown command.

It’s probably the simplest, least expensive option IMO.

In case my PI ever freezes, I have another momentary switch connected to the reset pins on the PI as well. this one is for emergency use only, because it has the same risk of corrupting your SD card, but has come in handy a couple times.

Here’s a solid article about your options:
http://www.raspberry-pi-geek.com/Archive/2013/01/Adding-an-On-Off-switch-to-your-Raspberry-Pi

[labelwhore]

Just confirming that ecmtools works well, if you can’t find roms in the correct format.

[labelwhore]

The neo-geo and mame BIOS need to stay zipped. Also, if I remember correctly, those two go in the same folder as the roms rather than in the BIOS folder.

[labelwhore]

There are sites that have every BIOS for the project. I can’t list them here, but there’s one that comes up first on almost any google search for BIOS and roms.

[labelwhore]

3.0 is so easy to set up and has so many improvements over 2.6. You’re going to be kicking yourself if you wait. It’s night and day compared to set up on 2.6.

[labelwhore]

I’m a huge Neuromancer fan, just stopping by to say I love your username Dixie. :) Unfortunately, I have no suggestions for you though.

[labelwhore]

https://github.com/RetroPie/RetroPie-Setup/wiki/Setting-up-the-XBox360-controller

In my case, I’m doing it in rc.local, but if you’re using the init.d script, you’ll have to modify that.

[labelwhore]

You need to initialize xboxdrv using the –dpad-as-button flag and use the mappings I provided. This will screw up the mappings of your other emulators, so you’ll have to remap those, but it’s the only way to get reicast to work with an xbox 360 controller.

look here for how –dpad-as-button works http://pingus.seul.org/~grumbel/xboxdrv/xboxdrv.html

and here’s the mapping I’m using. https://www.petrockblock.com/forums/topic/configuring-controllers-in-reicast/#post-99160

check my posts in this thread for more details.

[labelwhore]

Nope, I tried it, but DS runs like utter crap. I doubt it’ll ever be able to run well on a PI2, unfortunately.

[labelwhore]

Nice project!

I just started something similar with a 3D printed case. I’ll actually be using one of those cheap usb snes controllers and soldering the leads directly to the pi rather than messing with the GPIO pins, maybe something like that would be an option for you.

Kind of like this (although I’ve found a way to keep the controller PCB in-tact with my build):
https://learn.adafruit.com/pigrrl-raspberry-pi-gameboy/buttons

https://learn.adafruit.com/pigrrl-raspberry-pi-gameboy/wiring-buttons

[labelwhore]

With a problem of this nature, I’d suspect a power issue. Have your tested the controller with a pc?

[labelwhore]

It’s super easy to make a switch. You only need a SPST NO switch and a pull up resistor.

[labelwhore]

It certainly seems like it should work with dpad-as-axis (the default setting) as well. The only reason I set my controller up with dpad-as-button in the first place, is because I made an arcade controller out of an xbox 360 controller which uses the dpad for the stick that I wanted to use with MAME/FBA. Anyway, it sounds like you’re on the right track to fix it.

[labelwhore]

Huh. I hadn’t noticed that because most of my emulators are set up to use dpad-as-button. I think I only have FBA/NeoGeo using dpad as an axis which I mapped from within the emulators.

The good news is, that’s not hard to fix for the retroarch emulators, you just have to shift the button assignments in retroarch.cfg. You’ll probably have to remap controls in MAME as well.

[labelwhore]

Of course. Take a look at this page, particularly the Config Slot Options section. Since I assume you are using the init.d script to initialize xboxdrv, the steps to use this option will be different than mine. But I’ll show you how I’m using it regardless.

http://pingus.seul.org/~grumbel/xboxdrv/xboxdrv.html

I’m not at home, so I don’t have everything in front of me. However, in rc.local, I’m initializing xboxdrv kind of like this (I think the second ‘–id 0 –led 2’ can probably be removed):

xboxdrv --trigger-as-button --id 0 --led 2 --dpad-as-button --deadzone 4000 --silent --next-config --trigger-as-button --id 0 --led 2 --deadzone 4000 --silent &

Notice the --next-config seperating the different modes. One has --dpad-as-button the second mode does not. So what that does is when I start up my pi, by default my dpads act as buttons, then if I hit the xbox button, the dpad acts as a hat switch or axis, hit it again, and it goes back to acting as buttons.

Idk if other controllers have a similar option, but if they don’t, this one option makes the xbox 360 controller, the best controller for the Pi IMO.

[labelwhore]

xbodrv has an option to be able to switch controller modes. By default, the function uses the xbox button, but you can assign it to another one.

If you set that up, you can have a controller mode specifically for Reicast. I’d have to dig into the xboxdrv documentation again though to explain further.

[labelwhore]

I’m initializing xbodrv with the –dpad-as-button, and –trigger-as-button flags. If you’re not doing that, my settings in emu.cfg won’t work for you. I’m not using the init.d script, I could never get it to work correctly, and it also makes it more difficult to play with the controller modes that are available through xboxdrv. I find it handy to be able to switch the button config on the fly for different emulators such as Vice.

What I did to come up with those settings is take a look at the controller section in retroarch.cfg, and use that as a guide to help create the same settings in emu.cfg. Setup wasn’t exactly the same as in retroarch.cfg. I mentioned somewhere above that the dpad had some directions swapped, so lookout for that.

[labelwhore]

sudo chown pi:pi /path/to/your/folder

[labelwhore]

same solution. You need to run retropie_setup.sh from the terminal.

TBH, the problem sounds really odd. if reinstalling ES doesn’t do it, I really have no other guesses other than to try fresh from the latest image.

[Author]

Posts