2015-12-09, 02:48
Profucious, I need to understand what's going on better. I tried to PM you, but you have that turned off.
I appreciate your solution, but I've got further issues and want to better understand what's going on.
- In an emulator program I discovered that I could not map the controller at all. It would instantaneously return a -z axis input for all button mappings. This looks a lot like what was going on with the left trigger in Kodi before I tried your XML file.
- In another controller mapping program (PadStarr, which is a cousin of Pinnacle Game Profiler) I'm getting similar bizarre behavior on an old profile for Google Chrome. The trigger appears to be controlling the mouse when I intended it to control scrolling up and down and the mouse ought to be mapped to the left joystick. As it is, it just causes the mouse to run up and left.
- The controller continues to work fine in Steam both in Steam's browser and in games.
- I had bought the wireless adapter that was released in late October. I thought there might be a driver issue (since the adapter shows up in Device Manager as a "network adapter" with the actual controller as an HID device). Hooking it up via USB shows the same weird behavior.
What gives? I'd like to help the designers of these programs, but I need to understand what's going on. I'm seeing conflicting information about combined and separate axes that Microsoft changed. Also something about XInput vs DirectInput, but nothing clearly explained.
Thanks in advance for your help.
I appreciate your solution, but I've got further issues and want to better understand what's going on.
- In an emulator program I discovered that I could not map the controller at all. It would instantaneously return a -z axis input for all button mappings. This looks a lot like what was going on with the left trigger in Kodi before I tried your XML file.
- In another controller mapping program (PadStarr, which is a cousin of Pinnacle Game Profiler) I'm getting similar bizarre behavior on an old profile for Google Chrome. The trigger appears to be controlling the mouse when I intended it to control scrolling up and down and the mouse ought to be mapped to the left joystick. As it is, it just causes the mouse to run up and left.
- The controller continues to work fine in Steam both in Steam's browser and in games.
- I had bought the wireless adapter that was released in late October. I thought there might be a driver issue (since the adapter shows up in Device Manager as a "network adapter" with the actual controller as an HID device). Hooking it up via USB shows the same weird behavior.
What gives? I'd like to help the designers of these programs, but I need to understand what's going on. I'm seeing conflicting information about combined and separate axes that Microsoft changed. Also something about XInput vs DirectInput, but nothing clearly explained.
Thanks in advance for your help.