It's still a step in the right direction. I think once I get my controller problems all sorted out, everything will be fine. What I'll probably just do is use your Joystick Selection tool and map everything out to just use the Xbox controller, and then the NES pads just for NES. I can still go back in and change that to the Xbox controller in the future easily enough, so I don't have to worry too much about using that "on-the-fly" method.

Hi, I'ven been playing around with connecting a ps4 to retropie. The wike from FreakyBigFoot was a very big help. Like it sad, i borrowed 2 controllers from my friend, one newer , so i needed to use the ds4drv.
Today i bought my own new controllers, wich turned out to be the new version 2 (light bar on top of the touchpad and grey buttons).
I disabled ds4drv on startup in rc.local, connected both in the bluetooth menu, and they worked fine! buttons get registered.
(with the ds4drv i couldn't connect the second one)
Maybe someone else can confirm this. I just tought to share this so someone could put it in the wikki to help other people.

Thx for all the help, especially FreakyBigFoot

ps i also did the firmware upgrade discribed on the wikki of FreakyBigFoot , maybe it matters

@XD3l I don't know if there stuff is also in the US but some electronic warehouses sell Xmas calendars for electronics.
There are 24 doors to open and behind every door there is a new (very small) project to build. Here is a list with experiments :) and I think there also is a kit for the Raspberry Pi online :)

Edit:
The kit with RPi experiments

Answering my own question. I will start a new thread with full usage

#!/bin/bash # Script use $ sudo ./makexml.sh [RomDirectoryName] [-n optional] # -n does not right name to <name> tag useful for MAME roms as ES will autofill correct name # Store arguments arg1=$1 arg2=$2 output="gamelist.xml" # Change deliminator for $IFS # Allows script to work with names with white space SAVEIFS=$IFS IFS=$(echo -en "\n\b") # print scripts current status printf "Scanning dir: "$arg1"...\n" # Creates output XML file (gamelist.xml) printf "<?xml version=\"1.0\"?>\n\n" > ./$arg1/$output printf "<gameList>\n" >> ./$arg1/$output # Scans directory given by first argument for file in ./$arg1/* do # Just some manipulatiuon of data returned by $file filename=$(echo $file | cut -f 3 -d '/') name=$(echo $filename | cut -f 1 -d '.') # Checking for existance of correctly named image in ./images dir. [[ -f ./$arg1/images/$name.png ]] && theImage=./images/$name.png || theImage="" # Start writing to gamelist.xml printf "\n" >> ./$arg1/$output printf "\t<game>\n" >> ./$arg1/$output printf "\t\t<path>./"$filename"</path>\n" >> ./$arg1/$output # Checking whether the -n argument was used if [ $arg2 = "-n" ]; then name="" fi # Continuing writing to gamelist.xml printf "\t\t<name>"$name"</name>\n" >> ./$arg1/$output printf "\t\t<desc></desc>\n" >> ./$arg1/$output printf "\t\t<image>"$theImage"</image>\n" >> ./$arg1/$output printf "\t\t<rating></rating>\n" >> ./$arg1/$output printf "\t\t<releasedate></releasedate>\n" >> ./$arg1/$output printf "\t\t<developer></developer>\n" >> ./$arg1/$output printf "\t\t<publisher></publisher>\n" >> ./$arg1/$output printf "\t\t<genre></genre>\n" >> ./$arg1/$output printf "\t\t<players></players>\n" >> ./$arg1/$output printf "\t</game>\n" >> ./$arg1/$output # Print scripts current status printf $filename clear printf "Scanning dir: "$arg1"...\n" done # Closing gamelist.xml file printf "</gameList>" >> ./$arg1/$output # print scripts current status clear printf "Finished\n"

@BuZz

Ah, that's too bad.

I updated installed packages / kernel in hopes of fixing the issue. No devices were detected even with a cold 4.1 install.

The more i play with my Ubuntu up board the more I really like my pi3 to be honest it's cheaper and better less bugs and just all around runs better

You can get better performance if you do like Windows based emulators and turn up the detail but you are then limited on space. Sick with a pi 3 it's the best platform for retropie right now.

Thanks. I googled how to do that and it worked :).

I have this resolved after a bit of tinkering.
I had a old controller config in the mupen64 cfg file, I told it plugged=false.
Then I manually edited the config to match the buttons, using the same config you just linked to above.

this old post on the old forum helped too.
http://blog.petrockblock.com/forums/topic/8bitdo-nes30-pro-hotkey-problems-in-mupen64plus/

Thanks everyone.

@edmaul69 at the top right of the box where you edit posts it has a link compose? which opens a popup which links to http://commonmark.org/help/ which has all the info :)

@dankcushions , I will look into this. The thread may be misleading because it may not be a refresh rate issue, only what I suspected to be.

Problem solved. Turtorial is great.

@jrhessey I updated the wiki :)

Any luck with this? I would really love to use my iPhone as a wireless keyboard/mouse.

How do I install it on top of retropi?

Thanks

I have ran into so many issues with these rom set. It's really the fault of all these rom sites not listing the games or sets correctly or having different bios versions that work with different games and sets. It is very confusing.

I did it the sucker way by changing out roms and bios till I got most working.

Thanks all for the clarification. I had a feeling it was similar to Sega Genesis border colors and artifacts in areas not generally seen on older displays.

I was too verbose in the previous post. Let me summarize:

The all_users_control_menu doesn't make all plugged controllers control the menu. Actually it just makes all controllers bound to a player control the menu.

If I have a plugged controller not bound to any player, this controller can not control the menu.

Changing Device Index on-the-fly still can bring some unpleasant situations, like I detailed here (the all_users_control_menu decreases the chance to make it happen, though).