![]() When I do this, I'll also note that the TTL adapters TXD LED stays lit while the RXD one stays dark.įrom the above I can only guess its an issue with the firmware not finishing the handshake properly. That said, the console never receives the input. By that I mean, when I press the different buttons / sticks, the console window shows the buttons/etc im pressing properly. When I do this, I can see the debug inputs from the controller. It doesn't work more than maybe 10% of the time. To do this I spam click on the console window while pressing enter etc. When I set the GIMX Messages mode to "curses" sometimes i can get the command prompt to stay and not immediately show the error message. my TTL adapter has TXD and RXD led indicators as well as a USB led indicator, when I plug it in, the usb lights up, its recognized in the device manager as a TTL adapter, the TXD and RXD leds flash for a moment when I click "Start" indicating data is indeed sent across them. I don't think its the Teensy because I can load firmware fine including the blink program etc and everything seems to work properly. I don't think its the controller as it works perfectly fine with the console or on computer. The only part of the loop I couldn't change are the controller/cable and the Teensy itself. I swapped out the cable between the Teensy and console(mini usb) same problem. ![]() So I swapped out the TTL adapter and cables between it and the Teensy, same problem. I notice near the bottom of the log it says "Press the guide button to activate the controller.", I'm not sure how I'm supposed to do that in the fraction of a second the command prompt displays for(or if doing that would even do anything).Īnyway, any help would be greatly appreciated. Libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x00) No haptic sink found for joystick 0 (XInput Controller) Haptic core has source haptic_source_rumble for device 045e:028e Joystick 0 has name 'XInput Controller' and virtual id 0ĭump of C:\Users\Hex\AppData\Roaming/gimx/config/X360Pad.xml: Keyboard 0 has name 'PC/AT Enhanced PS/2 Keyboard (101/102-Key)' and virtual id 0 Mouse 0 has name 'ASUS Touchpad' and virtual id 0 Registered joystick 0 with name "XInput Controller" GIMX adapter detected, controller type is: 360pad. Global option -c with value `X360Pad.xml'Ĭontroller #1: option -p with value `COM3' For instance: I configure mine with ToolsUS, as well I run the US version of the game.Code: Select all global option -l with value `log.txt' ![]() However I reemphasize that if it's working in tools then it should be working in game. That being said: by default the PS4 controller is a directinput controller, not a x-input device, unless the driver you are using for it is redirecting it, so the above may be moot depending on what exactly it is you're doing. ![]() The simplest thing would be to configure all 3.Īs for that article: it doesn't appear to be related as you aren't experiencing those symptoms, however worse case scenario you could manually uninstall your driver and manually install the 360 controller for windows driver. There's a US config and EU, and I think still a generic one (checks, yup). It has to be something with windows 11.POL and XI have different configurations/settings, if it is working in XI config and not in game then 99% chance you are using the wrong config file for the version that is being launched. It works in POL and every other game but once FFXI loads up only can get the Dpad and sticks to work. Yea I give up and just going to go get a Xbox controller.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |