Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments)
-
I just downloaded the BMS launch v1.08 and it looks very good - and I know exactly the problem with the switching USB / DX devices as I often unplug/replug my Cougar and Logitech DFGT and Logitech RumblePad and it really messes up BMS.
However, how do I get the launcher to read in my BMS - Full.Key file? I’ve edited the default BMS - Full.Key file to add my DX-bindings.
But when I start the launcher and go into key bindings, I see nothing being mapped to any of the Cougar? I rather not want to re-do all my mappings in the launcher tool again if I can help it.
I read something about the launcher reading in the default key file when it cannot find the joystick XML file(s)? I’ve tried removing the XML files in the x86 directory where the replacement HUB.EXE is located but I still cannot see any of my DirectX bindings in the launcher? -
OK so no import function then. So I made a coffee and decided to redo my Cougar setup in the launcher then.
However, I now run into the issue that I cannot replicate my DX Keyfile Setup?
For instance, in my key file setup I’m using S3 as both the Pinky Switch AND as the Shift button to activate other functions.
If I press the S3 by itself, it acts as the Pinky switch, if I combine it with any other key, it activates the shifted layer in my DX setup.How do I replicate this here? I cannot seem to get it to accept this “double function” - and as such I cannot get my trim functions to be the Shifted HAT1 functions?
I’m sure I’m missing something here? Any help would be much appreciated.
-
Sorry I haven’t checked BMS forum for weeks.
You have to confirm no .xml files in /User/Config but in /x86. Usually this launcher saves .xml files after its first launch and close. So if it was the first launch, it should have tried to import axis setup and BMS - FULL.key from stock setup. If any error occurs it gives up importing stock setup and starts from blank setup. If there were any .xml files the launcer saved in /User/Config it loads setup from them instead of importing from the stock.
Could you upload your BMS - FULL.key and DeviceSorting.txt ?
-
A few days ago, I did a complete clean reinstall of my system and obviously (:drink:) BMS was one of the first things to be put back into place. Just as obviously, I went with the latest version of the launcher and put in the time to also clean up my binds so “get it right, this time”…
…at which point I noticed that it doesn’t seem to want to play well with my Warthog as far as button-release events go. I vaguely remember getting this to work on my old system, but since the binds were a mess (hence why I wanted to redo them from scratch anyway) I can’t quite be sure that they did indeed work.
At any rate, it doesn’t seem like I can actually use the many hold- and three-way switches the way I’d like in-game. I can easily use the key mapper’s “release” functionality to bind the switches to the proper on/off or forward/middle/back positions, but the ones that correspond to a button release refuse to trigger. The only one I’ve gotten to work is the MSL/DGFT override switch by binding each override position and then using the “3-way On-off-on override switch” checkbox – trying to do it manually with release triggers or through the config utility doesn’t work at all.
So I’m wondering if I’m misremembering or if this is something that is not working at the moment for whatever reason? The fact that it only works with a specialty option checked suggests the former and that this is more of a systematic problem that I just didn’t notice before.
-
Could you confirm you are enabling Invoke Key Down?
3-Way On Else Off assigning is working fine for my Warthog as follows:oh, by the way, this screenshot is also sneak peek for next version.
-
Nope! That was it.
I knew I had it working before and I’ve simply forgotten that part of the binding process.Also, nice visual update!
-
Hello, gentlemen, and very nice job to the author of the Alternative Launcher program! However it doesn’t seem to remember the key mappings I have set previously through it, i.e. when I assign keys to a particular function, close the launcher and then open it again, the key mappings are as they were before the change. Do you have a solution for this problem?
-
Thanks.
You have to launch BMS to save keyboard mapping.
In next version, it will be saved without launching BMS. -
You have to launch BMS to save keyboard mapping.
I don’t quote understand. You mean I have to launch BMS before or after I change the mappings in Alt Launcher?
-
OK, I think I get it now, I had to startup BMS after I was done editing the key mappings. Thanks, @chihirobelmo.
-
Hello, I installed as you have stated but when I click on the launcher of BMS it says App found BMS- FULL.key broken (/n) would you like to restore it to the default. If I press ok the same pop up message appears and I can’t launch the game. Any solutions?
-
Can you confirm BMS - FULL.key in C:\Falcon BMS 4.33 U1\Docs\Key Files & Input is the original one?
If it isn’t, try overwrite them with this one.
https://drive.google.com/file/d/1XRdb4ELN10ivEgF_HTM8NkCuvpvA2xBi/view?usp=sharing
-
Cheers mate, fixed it thank you so much!!
-
Can I actually import an old keyfile into a fresh install?
Or do I have to rebind all the buttons and axis again?
-
If you mean an old key file that of 4.32, No.
If from 4.33, as long as every line is in the correct format. You can. -
Jup, it is a recent keyfile.
So far, I tried just to copy and paste the file, but the bindings were not showing up in the launcher itself.
Maybe I have to use the “launch without any setup override” function for this?
-
That might be a glitch. Can you upload xml’s in your User/Config?
-
What do you mean by uploading xml’s in my config folder?
-
There is the setting files for your joystick.
ex: Setup.v100.Joystick - HOTAS Warthog {1ACA3150-718F-11E7-8001-444553540000}.xml or somethings like that
also don’t forget DeviceSorting.txt
-
Quick question, maybe with a quick answer. Can I bypass with that launcher the 32 button limitation? I have an x65f stick and the buttons higher than number 32 are not recognized.