Hello! are you in 4x32 mode?

my config ORION and F16EX GRIP : stick 56ce018f-f13a-41d3-95dd-c6d72b9f55bd-image.png

And trottle: a1ea1caa-d656-4ac2-938e-95c7259e2a27-image.png

That fixed it! Setting it to an Axis did the job and the rate of rotation in the sim is perfect at the default.

@Kumquat it is true the latest Alt Launcher sets it to 128 now … I think you’re seeing the result of that

I don’t know, if Alt Launcher has any special ability to track which button-assignments map to which device, and adjust accordingly (incl. pinky-shift magnitude) if/when you plug in new devices.

What I did in my Mac setup with FAF was to use a shift key to toggle the Trim hat between Trim and POV - works really well…I haven’t run that setup for a bit, but I think what I did was to set up the toggle by using a double tap of the NWS/MSL Step switch on the side of the stick.

I am at loss to understand what is going on. In set-up, I select throttle as the controller. Then in “Advanced” I map throttle axis (to winwing throttle x-axis) but I can’t select stick axes in that menu, so I select OK, then select the winwing stick on set-up, go Advanced again, and map the pitch and roll axis, but then it automatically resets the throttle axis to something else! So in the Advanced screens for mapping axes, I can either map the throttle ok, but then stick doesn’t work, or map the stick, then the throttle doesn’t work.

I have uninstalled and re-installed 4.36, and it still has this behaviour. Is there something I am doing wrong, or is there a way to fix this please?

LATEST - I ‘might’ have fixed it. Edited the DeviceDefaults.txt to put the axes in manually. It seems to like that better. I still needed to assign throttle axis in the set-up screen but it appears happier now. There is still some strange behaviour in the .key file, in that DX buttons have been assigned but the relevant .key file doesn’t show them (at all), even though they seem to work when tested in set up.

@kouzi You are the BOSS! Works like charm! Exactly like it was supposed to do! Thank you my friend!!!

@jfeagin
that did it! now it works perfectly!

thank you and all the users who shared their suggestions!

regards
Rubberduck85

Thanks for the suggestion! What I ended up doing is using vJoy and JG to create the virtual controller for the >32 buttons. Then I went to the Setup menu in game and assign the buttons the old way. The game didn’t have any problems recognizing 2-way/3-way toggles and mutli-selectors. I just have to save after assigning and load BMS Full before I fly. It worked out great!

Happy Holidays!

Kerfuffle,
There are no instructions per se!

This was an email from Winwing:
The BMS is too old and can not support 128 key hardware, please go simapp>test page of orion base, there is a selection to 4x32key device ,change to that model, you will have 4 device in BMS. Follow this instruction/advice…this is the only thing you will do in the simapp pro is select 4x32key device!

Then open Falcon_BMS_Alternative_Launcher_v1.60 set-up your axis assign and key mapping(you will see 4 winwing throttle base2+ F18 handle columns and one Winwing Joystick base2 + F18 Grip column) this is where the fun begins! Always launch the game from Falcon_BMS_Alternative_Launcher_v1.60! I tried to embed a screenshot but it didn’t work.

Everything works with my orion in BMS…pretty freaking sweet! Launching off a carrier in f18 I flip the launch bar switch on the throttle base panel and then rotate the wing fold knob to spread and watch the wings unfold and lock.

I am here to help because I understand the frustration…let me know we can get you up and running!!