Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments)
-
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.
-
Thanks to you I finally got rid of foxy and cougar cp! I was to lazy to read on how to use normal key file editing.
-
chihirobelmo do you have any plans to release this as open source?
It still crashes here nearly on every BMS exit and I would like to debug and fix it. -
App crash is caused here.
“Win32Exception: Not enough quota is available to process this command” happens at Line 400 when closing BMS.
Any idea?If you would like to read whole code, I can give you via PM.
I’m ashamed to say I could not understand Git well so I may public the code as a zip file to somewhere later…is there any good place to do so? -
I am unable to shift my POV hat on my X-52. I am trying to set it where the normal presses are DMS and shifted is CMS, but when I assign one, the other clears. I am clicking ‘KEYCOMBO/PINKYSHIFT’ and pressing the directions on the hat, but each time I do that for CMS it clears the regular assignments for DMS. Am I doing something wrong? Thanks for looking!
-
Thanks to erpe’s help CTD issue when exiting BMS has been fixed.
I also added theater own settings launcher and fixed some layouts, made/added several changes.Theater own setting launcher
When you select a theater that has its own settings executable, clicking a wrench icon that appears next to the theater combo box will launch those executable.
Currently, the app supports this for Israel and Ikaros theater.
If you have any other theater that has its own settings, please tell me the executable name, its path and theater name on the combo box.Code:
- Fixed CTD while exiting BMS. - Reduced file size. - Added theater own settings launcher. - Fixed "AxisAssign" page not showing whole device name. - Added MONO command line option for BMS. - Added shortcuts for TrackIR 5 and VoiceAttack.
-
I am unable to shift my POV hat on my X-52. I am trying to set it where the normal presses are DMS and shifted is CMS, but when I assign one, the other clears. I am clicking ‘KEYCOMBO/PINKYSHIFT’ and pressing the directions on the hat, but each time I do that for CMS it clears the regular assignments for DMS. Am I doing something wrong? Thanks for looking!
Thanks for your report. I confirmed a same behaviour on my setup too. I will look for codes.
EDIT:
Oops! What a fool code I was writing. Okay I release v1.06 here.
Code:
- Fixed unable to assign both shift and unshift layer for POV
ANOTHER EDIT:
wow it’s still v1.05 at the bottom right corner of the app but don’t wolly its v1.06 -
Oh, and as you guys might notice when clicking on the download link, the Alternative launcher is now open source.
I also would like to know exact instance name of each following device: ie. “Joystick - HOTAS Warthog” for Hotas Warthog Joystick.
The instance name is what you will find in this window.- Thrustmaster HOTAS X/T16000M/T16000M FCS/TWCS/TFRP
- CH Products Fighter Stick/Combat Stick/Pro Throttle/Pro Pedals
- Saitek X52/X52 Pro/X55/X56/X65F (Do they still has the same instance name after they went to Logitech?)
- Logitech G940
- FSSB R1/R2/R3
- FCC3 for Warthog
- MFG CROSSWIND (other than V2)
- SLAW DEVICE RUDDER
- BAUR PEDAL
- VKB MCG/KG12
- VPC T-50/Constellation
-
Thanks for your report. I confirmed a same behaviour on my setup too. I will look for codes.
EDIT:
Oops! What a fool code I was writing. Okay I release v1.06 here.
Code:
- Fixed unable to assign both shift and unshift layer for POV
ANOTHER EDIT:
wow it’s still v1.05 at the bottom right corner of the app but don’t wolly its v1.06Thank you so much for the quick fix!
I have a Logitech X-52, and I show ‘X52 H.O.T.A.S.’ in the game controllers window. I hope that helps, thanks again!
-
with version v1.06, a debug console windows is opened when a launch the game
-
with version v1.06, a debug console windows is opened when a launch the game
That should happen on purpose when you enabling “MONO” command line.
Clicking the button to grey out it, and debug console will be disabled. -
Sorry! I just find v1.06 can’t assign keyboard! I will fix and release v1.07 ASAP.
-
Oh, I’m really stacking here. Running app from Visual Studio and building solution then put it into BMS works completely different way. Is there anyone good at compiling problem?
EDIT: Okay, things are becoming tricky and weird.
Right window has a release built with debug code which will popup both debug message window before launching BMS. Running release built from right window, those will be successfully popup. Now then I will select whole files in the right window. Ctrl+C, I select the left window which shows /bin/x86/ of BMS directory. Ctrl+V, explorer asks if I want to overwrite them, I say yes. new release built were overwritten to bin/x86/, I run Hub.exe from Bin/X86/, launch BMS, debug window does not comes up.
FINAL EDIT (I HOPE):
OKay, I was thinking the source of the problem waaaay exaggerated.
There was a so simple mistake I was making when checking the app at /Bin/x86
Yeah, There is a “Launch without any setup override” option checked when I starting BMS.
This launcher remembers each checkbox settings you set last time.
When I move the app executable to a different directory, It starts to save and load such settings as an another preset.
So, while “Override off” unchecked at release built file, it is checked when it moved to /Bin/x86 of BMS.I will add “You are checking override offsetting, are you sure?” message box when the option is enabled.
I will release v1.08 with keyboard bindings fix but before that, I will test the app again. Sorry troubled you guys.