Saitek X52 HOTAS issues with button 6 and button remapping

[Shimaaji]

Hi

I just got the game and ran into the following issues with my X52 HOTAS:

While playing the tutorial, when it gets to expecting me to target a subtarget on the barge it tells me to use Joystick button 6.

I can confirm in my control panel, that button 6 on my X52 actually works, but in game it does not register. Neither can I select subtargets nor does the control setup register button 6 at all.

(EDIT: Note that "conceptually" button 6 on this HOTAS is primarily intended as a shift-button to assign additional functions to all other buttons ... but I don't have it set up that way and it "should" work as a normal button. Apart from that the problem I'll describe in the following paragraph exists, preventing me from circumventing the usage of this specific button altogether:)

Remapping buttons in general also doesn't work all that well: When I select a function and then press one of the buttons to remap it the item in the control setup changes to the new button (for instance button 13) and for a fraction of a second flashes white and then returns to red and the "Press any button to continue" prompt reappears. It doesn't actually lock in my choice. alt+tabbing out of the game helps to get the menu "un-stuck", but actually changes the mapping to the alt key.

I do have an old 3rd party x-box controller that I can technically use to play the game, but after trying both devices in the first few moments of the tutorial as stick just feels SOOOO much better with flying the bird and felt really fun even in those few moments ... I'd like to get this to work if possible. :D

(Maybe it's just me, who actually grew up with sticks on Amiga and PC and never owned a gaming console until much, much later in my life ... and even then didn't really use that for action games ... so I wouldn't want say that gamepad input is inferior in this game ... just not what I'm used to for flying anything. So don't take this post as criticism for that, please! ;) )

[Muppetpuppet]

it does sound if some kind of bug is happening that is preventing rebinding.

Can you try the following for diagnostics
-disconnect all other input devices (controllers) except the stick
-disconnect the throttle component of your hotas
-turn of or turn on steam input (try it with enabled or disabled)

feels like a conflict of some sort, and the error is preventing the rebinding from working properly

[Shimaaji]

Forcing Steam Input to on or off doesn't change the result and apparently the HOTAS also isn't managed via Steam Input. (It doesn't appear as a controller in it's settings menu.)

I also hadn't connected any other controller or other gaming-input device the entire time. (The gamepad that I confirmed to be working I had only plugged in for that one test run.)

Unfortunately I cannot disconnect the throttle unit since the stick doesn't have it's own USB connector, but is instead hooked up to the throttle via a cable with proprietary connectors. (look somewhat similar to s-video connectors, but not identical)

I've recorded a super-short clip to visualize how it looks on screen and uploaded it as an unlisted YouTube video: https://youtu.be/8oOUr8-FyVw
The buttons 13 and 14 that light up during the "failed" mapping process are indeed the ones I was pushing at that time, since they don't conflict with other mappings in the game.
At the end I wasn't touching the HOTAS anymore and just repeatedly pressing ESC, which also did not lock in properly for a few tries until I eventually got out of the menu. (Alt+tab is more reliable in interrupting the "stuck" mapping process, but I didn't want to do that with the recording.)

[Muppetpuppet]

I fear it is an error that is interfering with the remapping and just breaking it outright.
Could be that button has some different functions behind the scenes of the saitek driver or something. or a double binding which I hadn't considered.

That said there should be a log at user/appdata/locallow/wiredproductions/thefalconeer/player.log

If you could paste just the bits that say "error" that could show if there is an actual error being thrown.

I do know other saitek users that played it, and cannot recall another report. so that suggest it can fixed somehow just by fiddling with drivers/settings

[Shimaaji]

There are indeed no error entries in the log. The very same process shown in the video looks like this in the log: (At least as far as I can tell that should be the lines referring to my attempt at binding keys. But the term "error" appears nowhere in that log at all.)

switched resolution to : (1920.0, 1080.0) 
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 39)

skipped cutscene 
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 39)

Input detected 
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 39)

[Inputs] Change input 
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 39)

total health value5 
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 39)

[ControllerBindings] OnRebindApply Applying path <HID::Saitek Saitek X52 Flight Control System>/button13 
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 39)

[ControllerBindings] OnRebindApply Applying path <HID::Saitek Saitek X52 Flight Control System>/button14 
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 39)

[ControllerBindings] OnRebindApply Applying path <HID::Saitek Saitek X52 Flight Control System>/button13 
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 39)

[ControllerBindings] OnRebindApply Applying path <Keyboard>/escape 
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 39)

[ControllerBindings] OnRebindApply Applying path <Keyboard>/escape 
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 39)

[ControllerBindings] OnRebindApply Applying path <Keyboard>/escape 
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 39)

[ControllerBindings] OnRebindApply Applying path <Keyboard>/escape 
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 39)

[ControllerBindings] OnRebindApply Applying path <Keyboard>/escape 
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 39)

prepping saving controls 
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 39)

total health value5 
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 39)

Considering this is apparently a very isolated issue ... if there's no idea that pops up instantly I really don't expect you to devote time to this issue. I'll later try playing around with settings in X52 config and see if that changes anything.
If all else fails I might eventually try un-mothballing my other HOTAS or just make do with a gamepad. ;)

[Muppetpuppet]

Hmmm that is dissapointing. I got sponsored by thrustmaster so I do admit having tested on a lot of thrustmaster hotas sets back in the day. Could be some new issue or a saitek issue.

sorry

[Muppetpuppet]

@shimaaj,, I've tracked down a massive rebinding issue on linux. Was one hell of a nasty mother.

But I might have fixed your issue,, if you contact me I can get you on the beta test version of the patch
Cheerio
sorry it took so long
tomas

[Shimaaji]

I can confirm that your patch today fixed the issue! (I guess no more need for a beta.) Thank you so much! :)

[Muppetpuppet]

aaah excellent , and there you've just beta tested my patch ;) QA 4life ..
thanks