Saitek X65F & BMS Alternative Launcher
-
If you are familiar with Saitek’s X65F, you know that it has 4 different selectable and independent programmable modes, instantly switchable with a four-way mode switch on the throttle, and each mode has its own functioning <Shift State> as well.
Each mode can be completely and independently programmed for all buttons, hats, etc. on the HOTAS.
Over the years, I’ve developed programming for each mode as follows:
Mode 1 - Normal flight
Mode 2 - Takeoff/Landing
Mode 3 - AAR/Hot refueling
Mode 4 - Emergency situationsThese four independent modes are software programmable using Saitek’s key-binding software, which serves as a driver between my HOTAS and Falcon BMS. So I start the Saiteck HOTAS software with my Falcon BMS profile enabled, and then start Falcon BMS.
I don’t see how the Falcon BMS Alternative Launcher can let me set up a similar arrangement. Am I missing something?
-
@SoBad Sorry, I’ve only used the mode switch as the dogfight switch and been years since I got into heavy shift states. Because of that, I don’t think I’m 100% the best person to answer, but the new Launcher does not give you anymore shift state capabilities that you would have with standard BMS. Advanced shift states like that are device dependent and will always be best done with its programming software, like SST.
There is a simplicity advantage of DX only programming, especially with the DX128 support. Since I have so many devices, I’ve moved away from device software profiles, but that’s because I have enough devices I don’t need the shifts either. I would say I have an issue with X65F with the higher number DX buttons not being recognized by DCS ( any maybe some in BMS but I can’t remember right now) without having the SST profile page open in the background incase you ever decide to go that route.
-
@SoBad sorry I don’t have Saitek, so please clarify … does it work by generating key presses, or by bank-switching the range of dx buttons?
DX limit is 128 buttons per device, so unless it generates several “virtual” devices, one for each of the profiles, I’ll assume you’re programming the buttons to generate keypresses
Obvs you can use AL to craft any missing key bindings … which you then apply in the Saitek profiles. Not sure what else to say or do.
Be advised: for shifted keys, I know BMS is sensitive to the pressA-pressB-releaseB-releaseA event sequence… and I’ve heard the Saitek software is not always perfectly reliable in that way. or maybe that was TM Target? not sure … just be vigilant for the possibility of “stuck” callbacks
-
@Snake122 said in Saitek X65F & BMS Alternative Launcher:
@SoBad Sorry, I’ve only used the mode switch as the dogfight switch and been years since I got into heavy shift states. Because of that, I don’t think I’m 100% the best person to answer, but the new Launcher does not give you anymore shift state capabilities that you would have with standard BMS. Advanced shift states like that are device dependent and will always be best done with its programming software, like SST.
There is a simplicity advantage of DX only programming, especially with the DX128 support. Since I have so many devices, I’ve moved away from device software profiles, but that’s because I have enough devices I don’t need the shifts either. I would say I have an issue with X65F with the higher number DX buttons not being recognized by DCS ( any maybe some in BMS but I can’t remember right now) without having the SST profile page open in the background incase you ever decide to go that route.
Thanks to both of you for your input. This helps a lot settling this question for me. I asked because it’s clear that Falcon BMS users are generally taking advantage of the Alternative Launcher options, and I wanted to explore to what extent I could take advantage of it also. But it seems pretty apparent to me now that the SST software is the preferred method for me. I just wanted to put this question to bed.
Tex, I’m pretty proficient with the SST software, and I can assure you that it handles event sequences without issues. You just have to pay attention when you “manually enter” a sequence of key presses and releases to “step out” in the exact reverse order that you “stepped in”.
-
@SoBad Hi, SoBad. Like Snake, I didn’t use the mode switch as designed back in the 65 days. However, as this was early-AL, I did use a combined approach where I did mostly AL but some SST. I wonder what would happen if you used the new AL to achieve 2 of your desired mode(with shifting) and set the other 2 in another of the 65’s modes?