Speed Brake Mapping and WinWing f16ex

[Blackhawk163]

If anyone has a winwing f16ex on an Orion 2 base, can you try mapping the speed brake function onto buttons 8 to extend and 7 or even button 8(off)? I ask because when I do it simply doesn't work. If I try and get creative and have something like 8+7off to extend and 7 on with 8 off as a combo, it will work once and then that's it. So basically, I want to have the paddle pulled in for speed brakes extension and then off to auto-retract. 

The only other module that gives me an issue is the f16, but the combo buttons setup (see above) works with that. All my other modules either work with just two button mappings or actually have an axis assigned to the speed brakes.

[Yurgon]

1 hour ago, Blackhawk163 said:

So basically, I want to have the paddle pulled in for speed brakes extension and then off to auto-retract. 

Sorry, can't help you with the actual button setup problem, I'm flying with a mixed Virpil/TM setup.

Just a word of caution, landing configuration in the A-10 is gear down, flaps full, and 40% speedbrake (give or take, since there's no indicator anywhere ). With the setup you're looking for, it looks like you might not be able to land an A-10 "by the book". 

[Blackhawk163]

4 minutes ago, Yurgon said:

Sorry, can't help you with the actual button setup problem, I'm flying with a mixed Virpil/TM setup.

Just a word of caution, landing configuration in the A-10 is gear down, flaps full, and 40% speedbrake (give or take, since there's no indicator anywhere ). With the setup you're looking for, it looks like you might not be able to land an A-10 "by the book". 

It's all good, I'm definitely not a purist, the book stayed in the aircraft back in the late 90's when I left.  I suppose I can try and use the toe brake buttons on the skywalker pedals to see if that works.

[shagrat]

vor 13 Stunden schrieb Blackhawk163:

If anyone has a winwing f16ex on an Orion 2 base, can you try mapping the speed brake function onto buttons 8 to extend and 7 or even button 8(off)? I ask because when I do it simply doesn't work. If I try and get creative and have something like 8+7off to extend and 7 on with 8 off as a combo, it will work once and then that's it. So basically, I want to have the paddle pulled in for speed brakes extension and then off to auto-retract. 

The only other module that gives me an issue is the f16, but the combo buttons setup (see above) works with that. All my other modules either work with just two button mappings or actually have an axis assigned to the speed brakes.

You may try "pulled paddle"(Button 8?) = "Extend" then select "Retract" and manually select the now available option Button 8 Off. Ensure the Paddle is configured as a constant pressed button in the device software (winwing).

The result should be: Paddle pulled (sends button 8 press and hold) and uf you release, it recognizes button 8 Off and should retract. 

[Blackhawk163]

27 minutes ago, shagrat said:

You may try "pulled paddle"(Button 8?) = "Extend" then select "Retract" and manually select the now available option Button 8 Off. Ensure the Paddle is configured as a constant pressed button in the device software (winwing).

The result should be: Paddle pulled (sends button 8 press and hold) and uf you release, it recognizes button 8 Off and should retract. 

Okay this is promising. I fiddled with simapp pro, but I am lost. I take it that this is in the key binding section? 

 

Setup a new binding (orion+F16ex) hit next and.... 

 

What should I put under condition? Execution should be where I change it (button 8?) to press? Or the paddle axis?

[shagrat]

vor 1 Stunde schrieb Blackhawk163:

Okay this is promising. I fiddled with simapp pro, but I am lost. I take it that this is in the key binding section? 

 

Setup a new binding (orion+F16ex) hit next and.... 

 

What should I put under condition? Execution should be where I change it (button 8?) to press? Or the paddle axis?

No, this is now possible directly in the DCS configuration menu. So you only need to ensure in Simapp pro the paddle button is sending as long as it's pushed, that's usually a default on most software like Simapp.

 

[Blackhawk163]

Oh right, yeah, that's not working for me. It works on other modules, but for some reason it will not work on the A10 (either of them) for me. Which is perplexing.

 

This is why I need someone with an f16EX and orion 2 to test out for me, and if that's you how do I do this

Quote

Ensure the Paddle is configured as a constant pressed button in the device software (winwing).

 

[shagrat]

I downloaded the Manual for the WinWing F-16 Grip. I have a Virpil CM-50.2 on a Rhino base, so very similar, but not the same.

From the button overview it looks like the F-16ex has the same axis and button in parallel setup the CM-50 uses, BUT it has two(!) buttons emulated on the axis (or an additional physical button, at the end of travel ?)

I just checked the paddle lever (button emulation) with that button press and off state for extend/retract and l get the same phenomenon. It works once, then it doesn't react to the pedal button anymore, though the keyboard commands still work.

I tend to suspect a bug here, that's not related to the hardware or configuration. It should work exactly like this.

And this is unrelated to the paddle button, as I get the same behavior with other buttons off-state - works once.

 

[Blackhawk163]

3 hours ago, shagrat said:

I downloaded the Manual for the WinWing F-16 Grip. I have a Virpil CM-50.2 on a Rhino base, so very similar, but not the same.

From the button overview it looks like the F-16ex has the same axis and button in parallel setup the CM-50 uses, BUT it has two(!) buttons emulated on the axis (or an additional physical button, at the end of travel ?)

I just checked the paddle lever (button emulation) with that button press and off state for extend/retract and l get the same phenomenon. It works once, then it doesn't react to the pedal button anymore, though the keyboard commands still work.

I tend to suspect a bug here, that's not related to the hardware or configuration. It should work exactly like this.

And this is unrelated to the paddle button, as I get the same behavior with other buttons off-state - works once.

 

Cheers! I was starting to lose my mind on this. The paddle does have a physical button (8) at the end of travel and one virtual (7) and yes, it works once and that's it. 

So I too believe that this is a bug, as this behavior seems to only be within the A10 module(s).