I installed the new version RetroPie_OpenELEC_Dual-Boot_v7_SS, I proceeded according to this video https://www.petrockblock.com/forums/topic/video-guide-for-ps3-wireless-controller-on-retropie-3-final/ but my PS3 wirelles gamepad works only in the menu, does not in any ROM (Megadrive, PSX, Nintendo) is not working. The previous installation Retropie 3.0 RC everything worked OK.
In /opt/retropie/configs/all/retroarch-joypads/PLAYSTATION(R)3Controller.cfg

input_device = "PLAYSTATION(R)3 Controller"
input_driver = "udev"
input_b_btn = "14"
input_y_btn = "15"
input_select_btn = "0"
input_start_btn = "3"
input_up_btn = "4"
input_down_btn = "6"
input_left_btn = "7"
input_right_btn = "5"
input_a_btn = "13"
input_x_btn = "12"
input_l_btn = "10"
input_r_btn = "11"
input_l2_btn = "8"
input_r2_btn = "9"
input_l3_btn = "1"
input_r3_btn = "2"
input_l_x_plus_axis = "+0"
input_l_x_minus_axis = "-0"
input_l_y_plus_axis = "+1"
input_l_y_minus_axis = "-1"
input_r_x_plus_axis = "+2"
input_r_x_minus_axis = "-2"
input_r_y_plus_axis = "+3"
input_r_y_minus_axis = "-3"
input_enable_hotkey_btn = "0"
input_exit_emulator_btn = "3"
input_menu_toggle_btn = "12"
input_load_state_btn = "10"
input_save_state_btn = "11"
input_reset_btn = "14"
input_state_slot_increase_btn = "5"
input_state_slot_decrease_btn = "7"

EDIT: Problem solved
https://www.petrockblock.com/forums/topic/retropie-openelec-kodi-dual-boot/page/7/

Smithers Hi, I have a big problem with a recently installed RetroPie_OpenELEC_Dual-Boot_v7_SS, does not want me to work wireless PS3 gamepad. The menu works OK, but no ROM (Megadrive, Nintendo, PSX) is not working. I’ve set up your in this video https://www.petrockblock.com/forums/topic/video-guide-for-ps3-wireless-controller-on-retropie-3-final/.
In the last installation RetroPie_OpenELEC_Dual-Boot_v1_SS (Retropie 3.0 RC), everything worked OK. Can you help me? In /opt/retropie/configs/all/retroarch-joypads/ I have PLAYSTATION(R)3Controller.cfg

input_device = "PLAYSTATION(R)3 Controller"
input_driver = "udev"
input_b_btn = "14"
input_y_btn = "15"
input_select_btn = "0"
input_start_btn = "3"
input_up_btn = "4"
input_down_btn = "6"
input_left_btn = "7"
input_right_btn = "5"
input_a_btn = "13"
input_x_btn = "12"
input_l_btn = "10"
input_r_btn = "11"
input_l2_btn = "8"
input_r2_btn = "9"
input_l3_btn = "1"
input_r3_btn = "2"
input_l_x_plus_axis = "+0"
input_l_x_minus_axis = "-0"
input_l_y_plus_axis = "+1"
input_l_y_minus_axis = "-1"
input_r_x_plus_axis = "+2"
input_r_x_minus_axis = "-2"
input_r_y_plus_axis = "+3"
input_r_y_minus_axis = "-3"
input_enable_hotkey_btn = "0"
input_exit_emulator_btn = "3"
input_menu_toggle_btn = "12"
input_load_state_btn = "10"
input_save_state_btn = "11"
input_reset_btn = "14"
input_state_slot_increase_btn = "5"
input_state_slot_decrease_btn = "7"

PLAYSTATION(R)3Controller.cfg

input_device = "PLAYSTATION(R)3 Controller"
input_driver = "udev"
input_b_btn = "14"
input_y_btn = "15"
input_select_btn = "0"
input_start_btn = "3"
input_up_btn = "4"
input_down_btn = "6"
input_left_btn = "7"
input_right_btn = "5"
input_a_btn = "13"
input_x_btn = "12"
input_l_btn = "10"
input_r_btn = "11"
input_l2_btn = "8"
input_r2_btn = "9"
input_l3_btn = "1"
input_r3_btn = "2"
input_l_x_plus_axis = "+0"
input_l_x_minus_axis = "-0"
input_l_y_plus_axis = "+1"
input_l_y_minus_axis = "-1"
input_r_x_plus_axis = "+2"
input_r_x_minus_axis = "-2"
input_r_y_plus_axis = "+3"
input_r_y_minus_axis = "-3"
input_enable_hotkey_btn = "0"
input_exit_emulator_btn = "3"
input_menu_toggle_btn = "12"
input_load_state_btn = "10"
input_save_state_btn = "11"
input_reset_btn = "14"
input_state_slot_increase_btn = "5"
input_state_slot_decrease_btn = "7"

EDIT: Problem solved
https://www.petrockblock.com/forums/topic/retropie-openelec-kodi-dual-boot/page/7/

I have the same problem, I installed the new version RetroPie_OpenELEC_Dual-Boot_v7_SS, I proceeded according to this video https://www.petrockblock.com/forums/topic/video-guide-for-ps3-wireless-controller-on-retropie-3-final/ but my PS3 gamepad works only in the menu, does not in any ROM (Megadrive, PSX, Nintendo) is not working. The previous installation Retropie 3.0 RC everything worked OK.

[quote=102320]+1

I use Plex as my Media Server and would love the ability to run RasPlex from EmulationStation. I too tried berryboot to dual boot my Pi2 but ran into tons of errors. if anyone has made any progress with this I’d love to know.

[/quote]

I’ve got it all working, I’m running latest berryboot with Ubuntu mate, Rasplex, and RetroPie 3.0 on my Pi2…..love it. Bought a small wireless keyboard, and hooked my pi up to my 70″ flat screen. Only one thing though…can’t seem to get any controllers to work in-game..but they work in menu.
Though, from what I can tell my retroarch is out of date even though I updated to 3.0 from retropie_setup.sh.

It might be hard for me to just share the images because I’m running berryboot off of a SD card, the images are on a USB stick (for speed), I’m running wifi with my roms on a windows share. Let’s say this is customized…or geeked out.

[quote=105088]

candyluv wrote:

I seem to have a problem when trying to launch Retropie. I get a black screen from the start and it freezes at that. The only version that works is the vanilla v6. Both version 4 and 7 is giving me the black screen and I really want to use your pre-configured version. Also if I launch retropi from openelec then when I restart it will automatically go to the black screen.
Is there a way to rectify this issue.

Hmmm… sounds like your TV may not support the resolution I have set? In my ‘tweaked’ builds I set the resolution to 720p / 60Hz as below:

hdmi_group=2
hdmi_mode=85

You could try changing the resolution to something different in the ‘config.txt’ file on the partition named ‘BOOT’. Follow the below link to find a list of options you can try:

http://elinux.org/RPiconfig#Video_mode_options

Seems strange though – your TV obviously supports 1080p as thats the resolution I set for OpenELEC, so you would think it would support 720p if it supports 1080p? Well, try amending the options in ‘config.txt’ and see how you go.

[/quote]

Hi again,
Thanks for the reply, much appreciated.I believe you are right about it being a settings issue with my monitor I connected it to. I tried it on another TV and it works. So there is a strange glitch with my monitor.
Is there a way to set it to Auto since I will be moving it about to different TVs/Monitors? For example would you recommend setting it to hdmi_group=0. Don’t want to be playing around to much with changing the settings in fear of braking something.
Thanks

[quote=105085]

mikegold wrote:

I didn’t had the chance to check yet, but is Your build of OpenElec supporting advanced subtitles in the mkv files (on my old basic system I had to do this: sudo apt-get install libass-dev to get subs in mkv) ?

Hmm, I would say probably not, but I have never used .mkv’s in OpenELEC so I can’t say for definite. If its something that is widely used by folk then I have no issue in including it as standard in a future build, as long as it doesn’t come with unpleasant side effects?

mikegold wrote:

The error I mentioned before with missing files is visible on attached photo (the beginning of the message is cut, but it says lvl0: in each line.

As for the missing files – what directory are you using for your roms, is it the ‘mame-mame4all’ folder or the ‘arcade’ folder? I have tried both with no such problems so I’m struggling to replicate your error?
[/quote]

1. mkv files with subtitles are quite popular if it comes to Anime. I know that not everybody is watching Japanese animation, but You can trust me, that there is plenty of us ;]. There shouldn’t be any side effects to it. It’s something I found through Google and it seems to just add the decoding of .ass .ssa subtitle files within mkv container. I know it might sound silly, but I’m clueless if it comes to Linux – Is there any way I can go back to terminal from OpenELEC and install it on my current setup?

2. If it comes to error, I’m not using Arcade folder, but it doesn’t matter, since I don’t have to install any roms to see it. To replicate the issue You have to do this:
a) Install Your current modded build from the most recent mega link
b) delete some preinstalled rom files
c) reset retropie
d) When in EmulationStation after reset click F4
e) see the info about missing roms
Simple as that :)

Are you using the cfg files i uploaded and put them into /opt/retropie/configs/all/retroarch-joypads ?

I am having to start from square one again since i am using smither’s dual boot retropie and kodi build.

I did have them working with a straight retropie install, but i am now getting no response with the buttons with the dual boot image.

Hello Smithers, is there any way to update only sdcard partition with Retropie? I have installed version OpenELEC (KODI) Dual Boot V1 and I tuned OpenELEC and I would not like him set up your again.

I have compiled a binary for ZDoom and it runs well. I include it on my dual boot build, along with Brutal Doom which runs great on there.

If you’d like a copy of the binary then let me know and I will upload it. It is for Pi2 only.

I also have Crispy-Doom (and Crispy Hexen, Heretic and Strife) binaries pre-built, should you want them. All Pi2 only.

you can update individual emulators from the latest source from retropie-setup menu 5.

[quote=104813]@afjara

Install a clean RetroPie 3, then:

update the default snes emulator, “lr-snes9x-next”

Run the setup script
sudo /home/pi/RetroPie-Setup/retropie_setup.sh

Then choose the “Install individual emulators from binary or source” Then (probably 231) “lr-snes9x-next”, choose from binary

Then report the exact rom and error you get.
(Dont do anything except the above steps)

[/quote]

Thanks for your reply ;). I’ll try with a fresh RetroPie 3.0 setup when arriving home.

BTW, in my previous attempts, I didn’t get any errors on screen when launching roms. ROMs start loading and then exit to ES menu. I’ll check runcommand.log if the problem persists.

@afjara

Install a clean RetroPie 3, then:

update the default snes emulator, “lr-snes9x-next”

Run the setup script
sudo /home/pi/RetroPie-Setup/retropie_setup.sh

Then choose the “Install individual emulators from binary or source” Then (probably 231) “lr-snes9x-next”, choose from binary

Then report the exact rom and error you get.
(Dont do anything except the above steps)

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).

doesn’t that conflict with the OP’s situation, though? there’s was set to enable rewind in the psx config (perhaps by accident but even so), and by reverting it they corrected the issue. so the individual core configs override the /all/retroarch.cfg?

if that’s the case I’m not entirely sure of the purpose of the all/ one!

video_threaded is set to false in all/retroarch.cfg (as of 3.0 final), so you could override that if my assumptions about overrides are correct. I’ve got an older version so it’s set to true. all my emulators work fine as far as I can tell.

You need to update the default snes emulator, “lr-snes9x-next”

Run the setup script
sudo /home/pi/RetroPie-Setup/retropie_setup.sh

Then choose the “Install individual emulators from binary or source” Then (probably 231) “lr-snes9x-next”, choose from binary

Smithers, thanks for your reply. The Vanilla version is working like a charm!

May I suggest something?
I was fiddling with the Recalbox, which is also a “dual boot” version of a media center + retropie.
I like how transitions are seamless on that distribution. I mean, linux line codes and texts and command lines do not appear for the user when you boot, start a game, change from media center to game station, etc. It’s more like a “retail version”, if you know that I mean.

Do you plan to do it on your next versions?

Thanks again for your amazing job.

[quote=104160]Ok then, time for a new build – this is “Vanilla” RetroPie v3 and OpenELEC v15.1 (which addresses some of the bugs present in the last build). Please see links below:

MEGA:
https://mega.nz/#!UY5WAAJC!8-SxGSaWobfaUmwgEkXkmGl3vD3oxdAB38osIg5RelQ

Dropbox:
https://www.dropbox.com/s/zso2agu4cnxwdrd/RetroPie_OpenELEC_Dual-Boot_v6-Vanilla_ss.zip?dl=0

They work the same as my previous builds however I have changed the way in which you switch from OpenELEC to RetroPie. I no longer use Advanced Launcher and instead have incorporated a direct link to the launcher script in the ‘Games’ section (click the ‘Launch RetroPie’ button under the ‘Games’ header).

Seems to work fine my end – on first impressions OpenELEC seems more stable and no annoying popups asking to install scripts (so far!). It also has a nice KODI boot video too now which is new and looks great! (I didn’t make the video, it is just something that appeared in this update – just to be clear!).

Anyway – let me know how you get on.

My ‘tweaked’ build will follow in the next few days and I will be including some more ‘non-standard’ ports for your gaming pleasure.

All the best.
Steve

[/quote]

For me it works great, thank you very much for the hard work it’s just what i wanted.

A few questions whilst im here. Can i add a pre made kodi set up (the beast build from the wizzard) on to the kodi software without it messing up the retropie cross over?

Also if i make changes to kodi and then you perhaps bring out another build/fixes can i update without losing all the set up I’ve created?

Hope that makes sense. Sorry if this is common knowledge, I thought I would ask as i was giving feedback. Bit of a newbie.

I’ve finally had some time to test the Xin-mo dual controller with a fresh installation of RetroPie 3.0 and the autofire on the axis issue no longer exists, so applying the previous patch is not needed anymore. Great news!

With regards to it not being recognised as 2 controllers, I’ve tested the addition to /boot/cmdline.txt method that @feederchain describes above and it also works with the Xin-mo dual controller. The code to add to the end of the line (after a white space) is:

usbhid.quirks=0x16c0:0x05e1:0x040

Reboot required after saving the file.

Having reached this solution, I’m not going to bother trying to patch the kernel as this fix is simple enough for those of us with the Xin-mo.

Thanks very much to @feeder for all the help and effort!

Hi everyone! I tried the guide to set up my Dual Shock 4 with my RetroPie and once I get to the step where it asks you to connect your controller via USB, my controller is simply not detected. Now, I realise the guide is for PS3 controllers, but is there anything I can do to make a Dual Shock 4 work wirelessly, or is it simply not supported currently?

To be clear, the controller works great when connected via USB in both EmulationStation and in the emulators I’ve tried (NES, SNES, Genesis), so I’m not sure why the script doesn’t find it, though I guess it’s probably looking specifically for a PS3 controller??

Any help or nudges in the right direction appreciated, as I am a complete newbie at this. :)

Thanks!

Building a repo is tedious and takes time- its unlikely to happen anytime soon. With retropie 3.0 its a lot easier to get up and running from a fresh image- but you can always back up the configs you want and copy them back over after the update. I’m sure updates in the future will improve but the retropie project is always in development- file paths change and settings conflict with changes etc.

And you can update individual binaries without changing your configs. Its a bit of an ask in this day and age to expect something that was given for free to expect it to be perfect. You have to understand that this is free- the developers build it on their free time outside of their day jobs. If you wanted a quick and easy solution then you’re probably best looking somewhere else where you have to pay money for it.

As far as I can tell, this kernel hack doesn’t work with 3.0 for both players.

I ran the upgrade binary script.
Then I ran the new most recent Kernel hack update.
Then I ran JSTest and it sees every button on the Xin-Mo individually, but still registers it all as one big controller (which is what I believe it always did).
Then I ran the input config option within Retropie. It said it detected 3 controllers (I assume Xin-Mo one and two plus the keyboard?), but no matter which button I held down it said I was configuring for player one.
Same happened when I used the old school controller config option within the Retropie settings.
At least for now, my player 2 is dead.

apt-get update and upgrade only apply to the linux repos (like the raspbian repository etc.) these are completely separate from the retropie setup (though some may be needed in order for the retropie build to work- but they are typically already included if you start from a fresh sd image so its not that important)

If you wish to retropie there are a couple ways of doing it:

First and foremost you always want to upgrade the setup script first. That will pull the latest changes from the github repository.

Then you can either update everything with a full binary update (preferred) or full source update (if you really want to wait over 24+ hours for it to compile). Like you said though this will overwrite some configs which is why it is always important to make backups before you update.

Or alternatively you can upgrade emulators individually if you just want a few things updated.

Here’s a quick overview of the setup script that may help clarify things for you.