Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments)
-
Yeah. So far, I have been trying numerous fixes to make target work again with 1706, but to no avail.
This is the reason why I switched to the Alternate launcher.
So far, everything is bound correctly, I am just somewhat struggling with all the invoke commands.
-
Then again, I uninstalled the old key-file for target as well as the .tmc file.
Still, the launcher keeps “unbinding” my controls in mid-flight, which just annoys me.
-
Unbind while flying?
Perhaps, do that occur when you use pinky shift?
Or if you are using TARGET, isn’t it disconnecting “Thrustmaster Combined”? -
I don’t know if it only occurs when I use the DX shift.
Currently, I am NOT using target. I uninstalled the key-file and the tmc-file, as I would like to only work with the alternate launcher.
It seems like the program is terminated while I am in-flight, for whatever reason.
Could it be possible that the current version of the launcher is somewhat bugged?
IIRC, I read something like that on page 8 and 9 of this thread.
Greetings
Chris -
Alternative Launcher will be minimized and could not open until you close BMS. That’s OK.
The Launcher will overwrite config files when launching BMS, and BMS loads config files before flying.
After that, there is nothing the launcher can do, like unbind keys while you are flying.If you lost your key bind while flying and somehow any joystick button becomes unassigned to any callback, that might be BMS’s pinky shift glitch. If you press DX button where you assigned “STICK: Pinky Button (DX Shift)” longer than a second, without pushing any other DX buttons, BMS will keep DX layer shifted.
-
Thank you for your effort my friend. Everything is working fine except AxisAssign on my PC. It cant recognize my saitek x56. When starting hub, it says ‘awaiting inputs’. However, when I open the BMS setup section, BMS can recognize my stick and thrtolle. What should I do? Thank you.
-
Mhh, ok.
So you think that unbinding the DX-shift should resolve the problem?
What, if it still persists?
I wonder if the backup of the key-file screwed things up.
I always made a backup after any changes that I have done, but despite keeping it in the same folder, I always renamed it.
I also noticed that the launcher sometimes keeps crashing on me when I exit BMS, for whatever reason.
-
Mhh, ok.
So you think that unbinding the DX-shift should resolve the problem?
Don’t release pinky if you hold it but still not commanding any other shifted DX bind.
For instance, If you assign…
STICK: Pinky Button (DX Shift) | DX3 STICK: TMS UP | SHIFT DX7
If you short press DX3 for Pinky, it’s OK. This is “DX3” command. Pinky will be called.
If you hold press DX3 and press DX7, it’s OK. this is “SHIFT DX7” command. and TMS UP will be called.
If you hold press DX3 but release it without pressing any other button you have assigned “SHIFT DX n”, this will stuck your DX assignment to shifted layer. So even after releasing DX3, any “DX n” button you press will be “SHIFT DX n”.In this case, assigning following will fix the problem.
STICK: Pinky Button (DX Shift) | DX3, SHIFT DX3
Try assigning like above, And if you accidentally hold but released DX3, simply do the same thing again. DX layer will be back to unshifted.
What, if it still persists?
We have to look for another reason causing a problem.
I also noticed that the launcher sometimes keeps crashing on me when I exit BMS, for whatever reason.
I will terminate the launcher after launching BMS in next update.
-
Thank you for your effort my friend. Everything is working fine except AxisAssign on my PC. It cant recognize my saitek x56. When starting hub, it says ‘awaiting inputs’. However, when I open the BMS setup section, BMS can recognize my stick and thrtolle. What should I do? Thank you.
Do you mean you can’t assign any axis even you move the stick or dials at ‘awaiting inputs’ window?
-
Do you mean you can’t assign any axis even you move the stick or dials at ‘awaiting inputs’ window?
OK. I solved the problem by re-installing the x56 driver.
How can I use 4.32 KEYSTROKES instead of 4.33 BMS keystrokes on this launcher? Is that possible?
-
How can I use 4.32 KEYSTROKES instead of 4.33 BMS keystrokes on this launcher? Is that possible?
Are you going to use 4.32 key file for BMS 4.33?
or are you asking me if you can use the launcher for 4.32? -
Are you going to use 4.32 key file for BMS 4.33?
or are you asking me if you can use the launcher for 4.32?I want to use 4.32 key file named ‘‘keystrokes’’
-
Copy the key file you want to use from 4.32 folder to 4.33 User/Config and rename it as “BMS - FULL.key” might work, but I don’t recommend it. I can’t promise the launcher or BMS to work properly.
-
Some of 4.32 callbacks do not work any more on 4.33 … so using 4.32.key is more that “not recommanded”. So now, do what you want despite all the dev recommendations … but please do make us loosing our time and don’t post anything into the Support room and do not report for bug please.
-
This post is deleted! -
Well, so far I managed to sort out my bug. Guess, it was the DX shift problem.
Now, I am somewhat having trouble setting my Idle Detent correctly.
When I was using target, I could actually lift my WH throttle over the mechanical detent and BMS registered a movement there, so at that point I could set my Idle/Cutoff detent.
With the launcher, it does only recognize the movement once I lifted the throttle past the mechanical detent.
Is there any way to make it work like with target? Otherwise, I am sadly not able to use my mechanical Idle detent.
Thank you very much in advance.
-
Well, so far I managed to sort out my bug. Guess, it was the DX shift problem.
Now, I am somewhat having trouble setting my Idle Detent correctly.
When I was using target, I could actually lift my WH throttle over the mechanical detent and BMS registered a movement there, so at that point I could set my Idle/Cutoff detent.
With the launcher, it does only recognize the movement once I lifted the throttle past the mechanical detent.
Is there any way to make it work like with target? Otherwise, I am sadly not able to use my mechanical Idle detent.
Thank you very much in advance.
Thrustmaster Warthog Throttle has an axis transition only between IDLE to MAX AB.
It also has DX switches for its CUTOFF position, but there is no axis transition between CUTOFF to IDLE.
Warthog Throttle has 0 axes output at IDLE and 65535 at MAX AB.
TARGET is the only software that can program CUTOFF to IDLE axis transition.
The TARGET Script you were using, was scripted to consider that axis output 0 for Warthog Throttle set to an IDLE position to be an axis output 1 for Warthog Combined.
Then programmed that when the CUTOFF DX switch has been pushed, set Warthog Combined axis to 0 output. If released, set it to 1.So, It is not because “With the launcher” but because “Without the TARGET” you don’t have the axis transition.
In theory, TARGET and the launcher can work together.
You can program TARGET SCRIPT like this.
https://www.benchmarksims.org/forum/showthread.php?21919-having-trouble-with-shutting-engines-off-with-the-Warthog-throttle-shut-off-detents&p=428675&viewfull=1#post428675 -
I wonder if I could just use the Target Key-File together with the launcher by just renaming it?
I would love to go back to the Target Script, but since the 1709 update, it is constantly making trouble due to not loading correctly even after several tries.
I tried all the bugfixes on the forum that I could find, but without luck.
Maybe I should try using the most recent Morphine or Mud script, what do you think?
-
I wonder if I could just use the Target Key-File together with the launcher by just renaming it?
I would love to go back to the Target Script, but since the 1709 update, it is constantly making trouble due to not loading correctly even after several tries.
I tried all the bugfixes on the forum that I could find, but without luck.
Maybe I should try using the most recent Morphine or Mud script, what do you think?
Try anything you came up with…I am unable to know what would be best for you.
-
Hi chihirobelmo, thanks for your work. Your program crash after closing BMS, I am using 1.04 with BMS 4.33.u3. Thanks.