![]() If there is a problem with the Emulationstation, you can edit the es_input. ![]() If you want to test harder, you can test it with the sdl2-jstest command: If you want to take a look at other threads with a similar problem, see these for example: I can't give a solution to this one time, maybe waiting for the next version will be easier. Is there any information or log I could provide to help diagnose the Sorry, I'm not sure what it could be and I can't test it because I don't have this joystick, there are other reports on the forum, users saying they can't connect, users saying they can do it without problems. Then I configured the controller and tried again, no change.Īlso, when I turn the controller off and on during the game and it starts working inside RetroArch, I see the popup device disconnected from PORT #1 but I don't see anything on the log about it. I started with a clean system (no controllers connected/configured), I used the VirtualKeyboard to connect the 8bitdo controller via BT and tried a game before configuring the controller. Its not an emulation, its more a simulation, which is why you get near. Just in case here is the rest of the relevant part of the log This is the controller I'm using 8bitdo NES30 PRO (currently working with version 6.1.1) with last available firmware (v Thanks for your quick answer, I just had time to check this today, looking at the es_log I don't think it is the same error, that's assuming I'm reading the log correctly, the -p1devicepath has a value (INFO ) : Command: python /usr/lib/python2.7/site-packages/configgen/emulatorlauncher.pyc -p1index 0 -p1guid 05000000c82d00002038000000010000 -p1name "8Bitdo NES30 Pro" -p1nbaxes 6 -p1nbhats 1 -p1nbbuttons 16 -p1devicepath /dev/input/event1 -system nes -rom /recalbox/share_init/roms/nes/2048\ \(tsone\).nes -emulator libretro -core nestopia -ratio auto This emulation has a 96.2 accuracy according to TASVideos testing. But for anyone looking for better emulation I would like to recommend the emulator PuNES. Downgrading the firmware, factory resetting the Recalbox install and doing the pairing/configuring again didn't make any difference in the controller behavior.Īny ideas? I would really like to move to version 7 but these are the only controllers I have and using them via USB is not practical. For most people emulating the NES through Retroarch using either the Nestopia or FCEUX cores is plenty good and is by no means a terrible way to emulate the NES. ![]() I also tried downgrading the firmware to v4.00 since I saw other post talking about that as a workaround (could not find a download link to v4.01 on 8bitdo website). I can see the popup telling me the controller has been disconnected/connected. If I DO configure the controller, then it doesn't work in the emulator unless I turn the controller OFF and ON again.If I don't configure the controller before launching a game I can play (tried NES and SNES) but none of the HOTKEY combos work so I can't exit the game.I flashed a fresh image of 7.2.2, I was able to pair the controller by connecting a USB keyboard first. Hello all! I decided to try my luck again today with version 7.2.2 but I'm still experiencing the issues described in my previous post when I tried version 7.0.1Ĭontroller works in EmulationStation but not in RetroArch
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |