Daphne and 8bitdo
-
@BuZz
I know that daphne has nothing to do with retroarch. But i discovered that by chance when I accidentally deleted the controller.cfg. Suddenly daphne worked correctly. Since then I tested it 5 times. always the same result. Every button of the 8 bitdo stops the "laserdisc", when the controller.cfg is activated in retroarch. as soon it is deleted, daphne works fine.@theroamer
Maybe you can test it too?@Finhead
It's very much a controller issue. Since when i use a dualshock 3 I can use retroarch and daphne at the same time (and kodi). ONLY 8bitdo has these problems! The easiest way would be to just use a ds3, but where is the fun in that :)@mediamogul
jstest works fine. But I indeed see sometimes "INFO: The key you just pressed is not recognized by SDL" when retropie switches between games. But all the buttons work correctly in retropie menu, retroarch games, dreamcast, mupen64 so I ignored it. What does it mean & how do I stop it :)Thanks for your help everybody
-
@Keoky said in Daphne and 8bitdo:
What does it mean & how do I stop it :)
I believe it's symptomatic of the same issue you're seeing in Daphne and that you can at least trace the problem to the 8bitdo's interaction with SDL. Have you made any udev rules regarding the 8bitdo. If not, you may have to. I've got to run out the door right now, but I'll continue to give it some thought.
-
@mediamogul
I made one following the wiki
https://github.com/RetroPie/RetroPie-Setup/wiki/Setting-up-a-Bluetooth-controller
sudo nano /etc/udev/rules.d/10-local.rules
SUBSYSTEM=="input", ATTRS{name}=="8Bitdo FC30 Pro", MODE="0666", ENV{ID_INPUT_JOYSTICK}="1"I once again checked jstest. All axes and button work fine as I said before. But there are more axes and buttons shown then there are on the controller. Like there is a third axes shown that doesn't exist or buttons 13 to 21. Since I don't map these I thought this is not a problem :/
-
I've tested a lot of controllers and controller adapters out with Daphne and noticed that it tends to behave strangely every time it uses SDL to auto map the joystick and finds unused axis input. However, it usually only affects directional input, leaving the manual jsX input mappings alone.
For the sake of troubleshooting, can you confirm that a more conventional controller is working so as to eliminate other outside factors being a problem here? Do you have a standard pc USB controller you can try?
-
Actually, I have to recant what I was saying about my experience with Daphne and SDL. I had forgotten that my particular issues were due to a udev rule I had entered incorrectly.
-
@mediamogul
I only have two dualshock3 connected over usb for the kids. They work fine without any problems. I don't have any other input devices. Sorry -
This is obviously hard to troubleshoot without testing first hand, but I keep running into threads mentioning the udev rule solution not working perfectly outside of RetroArch due to a firmware issue with the 8bitdo. Is it possible there is a firmware upgrade available for the device from the manufacturer?
-
@mediamogul
I tried the last 3 released firmwares up to 1.69. Every firmware gives the same "INFO: The key you just pressed is not recognized by SDL". :( -
Did you ever attempt to operate Daphne before the 1.69 firmware update? There are reports that it breaks compatibility.
[NOTE] Verison 1.69 of the NES30 Pro/FC30 Pro software currently breaks the controllers in the emulators. If you accidently updated to version 1.69 you can easily downgrade following the same steps but downloading the 1.68 version.
Taken from:
https://www.reddit.com/r/RetroPie/comments/49amv4/8bitdo_controllers_guide/ -
@mediamogul
I used 1.68 most of the time because i had issues with retroarch and 1.69 at the beginning and also read about problems with that version. But funny thing happened yesterday, when I finally tested again 1.69. daphne worked fine and I dont get the "INFO: The key you just pressed is not recognized by SDL"! But retroarch didn't work at all. So I checked the controller.cfg of retroarch. Looks like emulationstation writes the wrong numbers in the cfg. (This works fine with firmwares <1.69) Like start =22 when it should be 11 and so on. I changed the numbers according to jstest, and it looks like everything works fine now. It was late at night, so I couldnt test everything. Will look more into it later today. -
@mediamogul
I finally had time to test the firmware – driver situation with the 8bitdo NES30 Pro.
Firmware 1.68 is very stable. Emulationstation and Retroarch games work fine “out of the box”. But there is this "INFO: The key you just pressed is not recognized by SDL" prompt. You can completely ignore this prompt, if you are not planning to use Daphne. Daphne has problems with these “not recognized buttons” and will pause every time you press a button. It doesn’t matter how you configure your daphne.ini.Firmware 1.69 has some problems. The controller sometimes doesn’t wake up. (When this happens, you have to charge the controller for a sec with the usb cable and it will wake up again). The larger problem is that Emulationstation is automatically writing the wrong button numbers in the retroarch controller cfg. It adds the value plus 10. Button 1 becomes 11, 9 becomes 19 and so on. That’s why there are a lot of users in this forum or reddit that complain that firmware 1.69 screws up their emulators. But this is actually very easy to fix. You just have to sudo nano your controller.cfg in /opt/retropie/configs/all/retroarch-joypads. Replace the wrong automatic generated numbers, with the right ones (that can be obtained by using jstest) save the cfg and reboot. Now all Retroarch games work fine again, you don’t get this “Info:…” prompt and Daphne does exactly what you defined in daphne.ini. I guess that’s PROBLEM SOLVED.
Of course it would be great if there is a tweak that Emulationstation is writing the correct numbers with the new firmware again. But the workaround takes like 5 minutes and you have to do it once.
Thanks for all your help and input @mediamogul
-
@Keoky I'll test this later today / tonight. With 1.69, which mode are you using? Power + R1?
-
@Keoky said in Daphne and 8bitdo:
Thanks for all your help and input mediamogul
Not a problem. I'm glad you've found some steady ground with this.
-
@theroamer
Just regular start (only power button). Dont forget that Retroarch uses the button numbers as shown in jstest (like A=0), while daphne.ini uses values +1 (A=1). You only have to map the buttons for daphne. the cross & left stick will be automaticly maped (keep the left,up,right,down button values at 0 in daphne.ini). Hope it works :) -
Verified that Daphne / Dragons Lair works with this fix! Also great that the 1.69 bug is fixable.
@Keoky would you mind posting your 8BitdoNES30Pro.cfg ? Retroarch seems to be working but I'm having some issues like exiting retroarch with start + select doesn't work.
-
Actually nevermind, everything's working great now with firmware 1.69.
Below is my /opt/retropie/configs/all/retroarch-joypads8BitdoNES30Pro.cfg
Daphne config are these numbers +1
input_device = "8Bitdo NES30 Pro"
input_driver = "udev"
input_up_btn = "h0up"
input_down_btn = "h0down"
input_left_btn = "h0left"
input_right_btn = "h0right"
input_a_btn = "0"
input_b_btn = "1"
input_x_btn = "3"
input_y_btn = "4"
input_l_btn = "6"
input_r_btn = "7"
input_l2_btn = "8"
input_r2_btn = "9"
input_l3_btn = "13"
input_r3_btn = "14"
input_select_btn = "10"
input_start_btn = "11"
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 = "10"
input_state_slot_increase_btn = "h0right"
input_exit_emulator_btn = "11"
input_state_slot_decrease_btn = "h0left"
input_save_state_btn = "9"
input_load_state_btn = "8"
input_reset_btn = "14"
input_menu_toggle_btn = "13" -
@theroamer
Sorry was on holiday the last days without internet. Happy that everything works for you too. Any progress with kodi controls?
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.