Winwing Orion 2 - Cutoff & Idle position detection
-
@Rubberduck85 did you also set the cut off position in BMS set up screen?
Maybe that’s not necessary with Alt Launcher, not sure as I don’t use it. -
@Badger i tried also there but no success.
-
No idea how you do it in Alt Launcher, but what you need to do is assign the buttons the WinWing shows for IDLE and CUTOFF to these commands (it sends a button press for going into and a different one for going out of cutoff):
SimThrottleIdleDetentForward
SimThrottleIdleDetentBackI use the Excel version to do this. Assigning the cuttoff to the axis in BMS won’t work because the WinWing doesn’t show any axis movement once it’s behind the idle detent. Also, make sure you are using the option in SimAppPro to split the throttle up because BMS won’t recognize all the buttons otherwise.
Note: this was for 4.35, I assume callbacks haven’t changed in 4.36 but I don’t know for sure.
-
@Robf4
Stupid question: the throttle is in 4x32 mode? Is the iddle position correctly assigned in the options and controls menu? Within the menu itself, not the launcher. -
Hi,
I had the same problem as well and this is what I had done. BTW since 4.36 you don’t need to have 4x32 mode on. Do you have the F-16 throttle or the Hornet
throttle on installed on the Orion? Either or, I think the issues is that the Orion sees idle detent as a button, not a throttle setting so I had to configure it in
Keymapping.- For idle put the throttle in detent and move to idle
- For cutoff do the opposite.
Hope this helps.
John -
Hi and thank you. So is it necessary to set it as 4x32 in the SimApPro? What does it do?
I understand the i need to map the “buttons” correlated to a specific throttle position but they aren’t read. Is this linked to the 1x128 vs 4x32?Also where can I find the excel version? It would help immensely in quick rebinding if needed.
Regards
Rubberduck85 -
@jfeagin
Thanks,
i have the F-16 grip.Those DX1 and DX31 are read while i move the throttle but they do not stick in the button assignment.
I was reading about an XLS config file. Can i assign them from there?
Regards
Rubberduck85 -
Never tried that with the cfg file but I am sure you probably could. Make sure in keymapping you hit the save dx button.
John
-
I’ve got a Winwing Orion 2 throttle base with the Winwing F-16 throttle grip.
I am using my Winwing in 4x32 mode, and I’m still using v.2.0.0 of the Alternative Launcher, because I couldn’t get my Winwing throttle to work correctly with v.2.1.0 of the AL.
It looks like I don’t have any button assignments for the idle cutoff or the afterburner. (In other words, I don’t have anything assigned to those functions in the Keymapping page of the Alternative Launcher.)
Here’s what I think I did, if I remember right: In the AL “Axis Assign” page, I assigned the Winwing throttle as the aircraft’s throttle. On the little pop-up box where I did this, there are buttons for the AB detent and the idle detent. For each of those detent settings, I think I just put the throttle in a position that seemed good for each setting, and then clicked on the relevant button in the little pop-up window.
I still have the “Idle Cutoff” checkbox checked in my BMS Configuration settings, as I have had for a long time. Back when I had a Cougar throttle, I assigned Idle Cutoff to a button on my mouse, and would click that button whenever I moved my Cougar throttle past the idle cutoff position. But now I don’t have to. I can just move the Winwing throttle forward or backward, past the idle cutoff position, and I get an engine start or an engine shutdown.
Apologies if this wasn’t very helpful, I just thought I’d pass along what seems to work in my case. I hope your idle and AB detents get sorted out soon, so you can enjoy full functionality from your throttle!
-
@jfeagin
that did it! now it works perfectly!thank you and all the users who shared their suggestions!
regards
Rubberduck85 -