I just fired up Xpadder for the first time since updating to Windows 10. My wireless 360 controllers work fine, but the Xbox One controller has problems with the trigger axis. It reads as +100% (i.e. as if the right trigger was fully depressed) while at rest when it should read 0%. The entirety of the trigger axis is mapped to the left trigger, so that as I push it down, the right trigger gradually drops from 100% down to 0%, then once past the half way mark of the left trigger's range, it begins to read towards 100% in the opposite direction. Pressing the right trigger at the same time as the left trigger is in any position at all has absolutely no effect.
Please note, this is not a game specific issue, and thus not a problem with my mappings. It is a problem visible in the Xpadder interface itself. It is however Xpadder specific, as I have been using the same controller in various games for some time without problems on my new OS setup without any difficulty whatsoever.
1 post • Page 1 of 1