Forum Discussion

SethMarion's avatar
SethMarion
5 years ago
Solved

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

Product: Star Wars: Squadrons Platform:Steam-PC Please specify your platform model. PC What is your gamertag/PSN ID/EA Account name? SethMarion Are you playing in VR? Yes Which VR Platform are y...
  • Scar_Wardjinn's avatar
    Scar_Wardjinn
    5 years ago

    If anyone is interested, i've fixed it using Vjoy and and Joystick Gremlin.

    The game detected the Vjoy input so i could assign an axis to it. In this case my rudder pedals.

    First install Vjoy: i didn't do anything here particular.

    Then installed Joystick Gremlin(JG): it detected all my peripherals, didn't do anything special here.

    Hit the activate button(the controller pad icon in JG, booted up the game and the Vjoy got detected. Now i could assign my yaw to that axis and it worked.

    Now fix that bloody deadzone issue!

    Hope this helps for everybody who's having the same issues i had.

    Cheers!

     
Nervous1's avatar
Nervous1
5 years ago

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.

  • Elphaba's avatar
    Elphaba
    5 years ago
    @Nervous1 If you don’t have gremlin running then the vjoy binding doesn’t do anything, and as the other games take bindings directly from said hardware, then this workaround doesn’t cause ANY issues whatsoever. At least not with Elite, DCS, Star Citizen and X-Plane.
    • Nervous1's avatar
      Nervous1
      5 years ago

      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.  

      • Elphaba's avatar
        Elphaba
        5 years ago

        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. 

  • Elphaba's avatar
    Elphaba
    5 years ago
    @Nervous1 And I know about the 3 device limit and they have to be first. I figured that out on release day. But the latest patch broke the vkb t-rudders (running on 2018 firmware) and in patching them to 2020 firmware they wouldn’t be recognised even if they were the ONLY device plugged in.

    So this workaround is just that, something that solves the problem until a perfect fix comes along; not that that is likely.

About Star Wars Games Discussion

Talk with the community about EA's STAR WARS™ games.14,755 PostsLatest Activity: 9 hours ago