Re: Cannot Bind VKB T-Rudder Pedals to Yaw Axis. Game does not detect device.

My VKB rudder pedals have been working since day one.

However after today's 1.3 patch, not only did it obliterate all my previous bindings, but I can now only bind the left pedal; it doesn't detect the axis increasing. 

The key to getting the VKB recognised is ONLY HAVE 3 USB HID DEVICES CONNECTED i.e. Stick, throttle, rudder. Anything else will break squadrons. 

crappy coding, non-existent testing and abysmal support. 

My VKB T-Rudders were working perfectly until todays patch, then it wouldn't recognise the right pedal going down. 

I stupidly patched my 1.9.4 vkb rudders to 2.0 and now frakking squadrons can't see them at all, but windows and every other sim can!!!!

So unless someone knows how to downgrade the firmware, we frakked. 

Okay, found an online repository of old VKB firmwares and successfully downgraded to 1.99.4... still not seen in the game.

The culprit seems to be the firmware has changed something in the Orange 'BlackBox' as it's now appearing in windows 'Game Controllers' as a device by another name. 

I believe this is the problem; mine worked because I had an old 2017 T-Rudder BlackBox firmware and never bothered to update it. You guys probably have newer boxes or even the Black 'BlackBox' and as such it's completely invisible to SW:S.

Really EA, such a lack of response, even from the community manager is really disgusting here. 

As mentioned in post 4 of this thread, there is a workaround: Read this -> https://answers.ea.com/t5/Technical-Issues/Workaround-for-VKB-T-Rudders-not-being-detected/m-p/9656120#M3843

Several huge issues with this 'workaround': 

- I doubt most of us have thousands of dollars in flight peripherals to play Star Wars Squadrons, and messing with VJoy will totally screw up DCS, IL2, FS2020, and any other decently coded flight sim.  

- If your HOTAS and pedals (or VJoy virtual controller) aren't in the first three enumerated devices, it doesn't matter what you do, and most of us have way more than 3.

They need to simply implement the same DirectInput options every other flight game on the market has.  Even FtP games like War Thunder get this right.

Perhaps they've improved it then, as the last time I used VJoy (admittedly over 10 years ago on Windows 7) it screwed up your device enumeration order, which invalidated your bindings.  It was treated just like plugging in and unplugging a peripheral, and it could bump other peripherals down a number.  Or maybe Win 10 handles it better.  After having to reconfigure DCS and 1946 bindings at the time (a job of hours) I never messed with it again.  

There's still the device enumeration limit hard coded into the game right now.  Squadrons doesn't see my Slaw pedals or Warthog throttle at all - it sees the Gunfighter III, the CH Quadrant, and the Accuforce Pro wheel.  

Edit:  Apologies, I didn't realize there was already a huge thread on the device limit.  

I'm not saying the vjoy+gremlin is ideal; it's far from it, but to date, it's the ONLY solution to get my rudders recognised and working. 

I am growing increasingly frustrated at the utter lack of engagement from the Community Manager / Developers. This is really bad form.