No need to tap dpad and action, and all shaders work. I just bought the $20 Walmart onn 4k stick.I'm impressed. Those PS2 knockoffs work as wired gamepads, a way better option just need to purchase the USB connector. You have to pair that knockoff PS3 to a single use csr USB Bluetooth dongle and that is the only controller that will work (Bluetooth) with the motionjoy app. FYI the knockoff PS3 controllers only work with the paid motionjoy app, it's not practical. I've had great success with the knockoff PS2 wireless controllers- I have a USB to PS2 connector, it's near perfect. I don't use PS4 controllers I didn't see that. I've seen lots of complains of people using 8BitDo controllers, but I really think this is a RetroArch issue, since I could manage to make everything work well using standalone emulators.ĭoes anyone have any ideas on how to handle those issues? I believe this is the similar issue as but any of the solutions worked, since i couldn't make it fully work, since there is always something not working well on these controller configurations. On the Xiaomi Mi stick both controller worked very well out of the box. If you still manage to go to configurations and configure it again, you'll be able to use the D-pad but not the A/B/X/Y buttons. But if you touch the remote controller, RA will assign it to #1 controller and you will mess all the controller configurations and nothing works correctly anymore. If you start retroarch with gamepad, configure the controller before entering a rom. And if you go to settings and try to configure it correctly, now you screwed the gamepad and nothing works again. Mostly the default controller configuration will work, but the start/select buttons. If you start retroarch from the gamepad: It will assign the gamepad as #1 controller. Like not even remote-controller nor gamepad will navigate correctly on menus. If you manage to go to the settings then, and add the gamepad as #1. If you start retroarch using remote-controller: it will assign the remote-controller as #1 controller, so when loading a rom, the gamepad controller will be assigned to #2 - and it's not going to work. Retroarch for some reason understands that the fire stick's remote controller is a gamepad controller, and always adds it as controller #1. Problem - explanantion and how to reproduce: I couldn't reproduce this issue, seems to me that this is a fire tv stick issue Tested on Xiaomi mi stick, everything works very well with zero configuration. tested with several versions of retroarch, 1.9.x, 1.10.x, nightly, stable, google play vesion, aptoide version, even downloading apk from official website. Tested with some standalone emulators, and I don't have those issues on them. On fire tv menus both controllers are working perfectly well. Tested with PS4 and Gamesir G3s controllers, same issue for both. Using most updated available version of FireOS I believe the same issue also happens on the regular FHD Fire TV stick. I am facing some weird controller issues on the Amazon Fire TV Stick 4k max. This problem affects millions of amazon devices.I am an old-ish Retroarch User, I've been using it on linux, windwos, raspberry pi, batocera, lakka among others. Blacklist devices with the keyword "remote" this really can't hurt.įix regular controller system and fallback system to support more than one controllerĪllow for both systems to work side by side, so as to allow at least two game controllers to work with Fire OS 6 and above.Īs there are probably significant devices between Android and FireOS, you may want to include these changes under input drivers "FireOS", where users are currently stuck with one option "Android".Also for wired devices RetroArch has a fallback system, but the fallback system cannot work in tandem with the regular system and the fallback system is also limited to one controller. This is insulting and proof of broken API. The Controller API literally spits in the users face, by claiming to detect controllers under some circumstances and yet when you map one controller to one profile and another to another profile only one controller works. Therein is the bug because outside the app, bluetooth controllers no manner how you add can all control the FireOS interface. This is evidenced by being unable to operate two controllers within RetroArch except for FireStick remote + any 1 controller. Controller API is fundamentally almost entirely broken on FireOS 6 and FireOS 7.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |