Jump to content

Recommended Posts

Posted

I have a Logitech x-56 HOTAS and would like to use its "(SLD) Thumb" "button" (JOY_BTN33) on its throttle console as a speed brake, to have it similar to where it would be and would be used in the real F-16C or F/A-18C. However with the following configuration I can extend it but then it stays stuck in the extended position:

F-16C, not working:
* SPD BRK Switch - Aft/EXTEND (Momentarily) -> JOY_BTN33_OFF
* SPD BRK Switch - Fwd/RETRACT -> JOY_BTN33
Or:
* SPD BRK Switch - Aft/EXTEND (Momentarily) -> JOY_BTN33_OFF
* SPD BRK Switch - Fwd/RETRACT <> OFF -> JOY_BTN33

speed-brake-issue-f-16c.png

F/A-18, not working:
* Speed Brake Switch - EXTEND -> JOY_BTN33_OFF
* Speed Brake Switch - RETRACT -> JOY_BTN33
Or:
* Speed Brake Switch - EXTEND -> JOY_BTN33_OFF
* Speed Brake Switch: RETRACT<>OFF -> JOY_BTN33

speed-brake-issue-fa-18c.png

In the "Adjust Controls" menu the two slider positions, JOY_BTN33 at Fwd position and JOY_BTN33_OFF at Aft position, are detected correctly though and selected/highlighted fine in there.

If I assign only one of the two functions at a time, so only retracting or only extending then each function works fine individually. If I use a toggle switch on the x-56 throttle console instead, which uses distinct button inputs, for instance the top one has JOY_BTN_18 for up and JOY_BTN_19 for down, then everything works as expected. Also if I invert the assignment, so JOY_BTN33 (fwd) for extending and JOY_BTN33_OFF (aft) for retracting then it works as expected, too (but that would be inverted to the real thing, so I would like to avoid that workaround).

Also interestingly, with the F-14 I do *not* have this issue - I can use the "(SLD) Thumb" "button" just fine for the speed brake there:

speed-brake-issue-f-14.png

(Disclaimer: I'm also on Linux. And I'm aware that I can't expect fixes/support for that there. But then I'd be curious to hear if this works fine for Windows users with an x-56 HOTAS and this "(SLD) Thumb" "button". That information would already help me a lot.)

SW, OS: Linux / Debian Sid -- VR: Monado (OpenXR) -- Launcher: Lutris -- Runner: Wine lutris-GE-Proton7-39-x86_64

HW, base/laptop: Lenovo Thinkpad T14s AMD Gen3 (AMD Ryzen 7 PRO 6850U, AMD/ATI Radeon 680M iGPU (for DCS usually unused), 32GB RAM, Samsung SSD 980 PRO 2TB) + eGPU: Razer Core X Chroma (Thunderbolt 3) + AMD/ATI Radeon RX 6650 XT 8GB; HOTAS: Logitech x-56, VR: HP Reverb G2

DCS Modules, Planes+Helicopters: F-14, F-16C, F/A-18C, AV-8B, AJS-37, UH-1H -- Maps: Nevada, Syria, Persian Gulf, Normandy 1944, The Channel -- Other Modules: FC3, Combined Arms, Supercarrier, WWII Assets Pack

1st "DCS" experience: Lock-On, later +FC1

Posted

You need to add an "On-Else-Off" binding to the aircraft's joystick default.lua.  

There are probably more than a few ways to do this.

You can check out this Mod in the user files for the files with changes in them. 

X55/56 Speed Brake Slider by Shiroka -

After using the above mod for a year I ended up migrating to DCS-Input-Command-Injector by Quaggles because it is a more elegant solution to the problem.

Happy hunting. 

  • Do not own:  | F-15E | JF-17 | Fw 190 A-8 | Bf 109 |
  • Hardware:  [ - Ryzen7-5800X - 32GB - RX 6800 - X56 HOTAS Throttle -  WINWING Orion 2 F16EX Grip - TrackIR 5 - Tobii 5C - JetPad FSE - ]
  • 3 weeks later...
Posted

Before I forget again: Many thanks @YSIAD_RIP, that workaround works like a charm! Diff'd those files and could figure out the one line I had to add to create this custom button that works with the x-56.

Still I guess it could be nice to fix this upstream, looks like several people stumbled over this and had to spend some time to figure out what's going on and how to work around it.

  • Like 1

SW, OS: Linux / Debian Sid -- VR: Monado (OpenXR) -- Launcher: Lutris -- Runner: Wine lutris-GE-Proton7-39-x86_64

HW, base/laptop: Lenovo Thinkpad T14s AMD Gen3 (AMD Ryzen 7 PRO 6850U, AMD/ATI Radeon 680M iGPU (for DCS usually unused), 32GB RAM, Samsung SSD 980 PRO 2TB) + eGPU: Razer Core X Chroma (Thunderbolt 3) + AMD/ATI Radeon RX 6650 XT 8GB; HOTAS: Logitech x-56, VR: HP Reverb G2

DCS Modules, Planes+Helicopters: F-14, F-16C, F/A-18C, AV-8B, AJS-37, UH-1H -- Maps: Nevada, Syria, Persian Gulf, Normandy 1944, The Channel -- Other Modules: FC3, Combined Arms, Supercarrier, WWII Assets Pack

1st "DCS" experience: Lock-On, later +FC1

  • 3 months later...
Posted

Hi,

Just wanted to ask politely, with no pressure, but to avoid that it is forgotten: What is typically the procedure here, is this issue on some internal bug tracker now, so that it might get a proper fix at some point?

Would be great if those of us owning an x56 wouldn't have to fumble in changes to Lua files for the workaround after every update anymore, that would be very appreciated :-). And I'm hoping that a proper fix wouldn't be too complicated?

Cheers

SW, OS: Linux / Debian Sid -- VR: Monado (OpenXR) -- Launcher: Lutris -- Runner: Wine lutris-GE-Proton7-39-x86_64

HW, base/laptop: Lenovo Thinkpad T14s AMD Gen3 (AMD Ryzen 7 PRO 6850U, AMD/ATI Radeon 680M iGPU (for DCS usually unused), 32GB RAM, Samsung SSD 980 PRO 2TB) + eGPU: Razer Core X Chroma (Thunderbolt 3) + AMD/ATI Radeon RX 6650 XT 8GB; HOTAS: Logitech x-56, VR: HP Reverb G2

DCS Modules, Planes+Helicopters: F-14, F-16C, F/A-18C, AV-8B, AJS-37, UH-1H -- Maps: Nevada, Syria, Persian Gulf, Normandy 1944, The Channel -- Other Modules: FC3, Combined Arms, Supercarrier, WWII Assets Pack

1st "DCS" experience: Lock-On, later +FC1

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...