Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments)
-
Hey will there be any plans in the future to allow for more modifiers and if possible a more customizable axis settings?
p.s ur awesome!
-
Is there a way to do the “on else off” thing outside of this launcher ? I’d like to bind my speedbrakes as on when my X56 SLD button is pressed and off when it’s not
-
I would like to suggest adding a shortcut for OpenTrack/Free-Track ETC… I always forget to open it,
It would help me a lot! -
Make autostart opentrack if launch falcon. in opentrack.
-
Would be nice add-on if you add an option to read the already made key maps. If already has be done and i dont see it im sorry please guide me!
-
@AsafBoy:
I would like to suggest adding a shortcut for OpenTrack/Free-Track ETC… I always forget to open it,
It would help me a lot!Or all the current shortcut spaces, customisable - i.e. you can add your own shortcuts, for instance I would add, voiceattack, joy2key and opentrack
-
Or all the current shortcut spaces, customisable - i.e. you can add your own shortcuts, for instance I would add, voiceattack, joy2key and opentrack
yep that will be good also.
I have a strange situation though… It seems that your program completely overide all the axis setup. Even if i load my keyfiles in game they dont work… maybe im doing something wrong…
-
I’m still new to the SIM and had a question regarding the KeyMapping in the AL. Right now I’m using a profile by Cashman which I downloaded into the config file. I’m using a X56 Rhino. It works ok (have problems with pinky shift/DX) but I would like to create my own mapping. Can I just do this in the AL? If I use the AL mapping section will it become the default map? What do I load into the UI. Do I just leave the Cashman profile in and have no changes made to it or do I have to load another profile in its place to match my AL map.
Thanks for any help.
CAFB
-
I’m not an expert but I’ll give it a try here. Someone will correct me if I am wrong hopefully.
I would like to create my own mapping. Can I just do this in the AL?
Yes.
If I use the AL mapping section will it become the default map?
Yes. The default map is “BMS - Full.key”.
What do I load into the UI. Do I just leave the Cashman profile in and have no changes made to it or do I have to load another profile in its place to match my AL map.
I don’t know what you mean by “the UI”. If you want to start with the Cashman keymap, then what I would do is rename “BMS - Full.key” to “BMS - Full.key.original” (even though I think AL already creates a backup in a subfolder for you) then rename Cashman’s profile to “BMS - Full.key”. Then I would do any adjustments I wanted to Cashman’s keymap (after renamed to BMS - Full.key) in the AL. You do not have to do anything in Falcon Setup as to keybinding and axismapping thereafter IIRC.
-
I’ll look into it tonight. Thanks for your response!
I was thinking I had to change the BMS KEY FILE based on my AL mapping since I was using Cashman’s key file for X56. But after I set my own mapping in the AL I just need to load BMS FULL correct?
CAFB
-
I’ll look into it tonight. Thanks for your response!
I was thinking I had to change the BMS KEY FILE based on my AL mapping since I was using Cashman’s key file for X56. But after I set my own mapping in the AL I just need to load BMS FULL correct?
CAFB
No I don’t think that’s correct. AL doesn’t load different keyfiles. It only loads BMS - Full and it only saves to BMS - Full. So you have to rename Cashman’s file as I stated above using Windows explorer or the command prompt or some other file utility program.
-
Hi,
I tried making my own profile with the alt launcher but found I couldn’t bind as much as I would like to attempted to revert to the default X52 Pro profile that comes with the BMS docs. My problem is that even though I’m launching with ‘Without any setup override’ - the default profile won’t work in the sim.
I have the Logitech profiles selected correctly and the correct keyfile loaded. tested the buttons in 2D and they work correctly but nothing happens when i enter 3D. No buttons on the HOTAS work at all.
-
@DUSTOFF17:
Hi,
I tried making my own profile with the alt launcher but found I couldn’t bind as much as I would like to attempted to revert to the default X52 Pro profile that comes with the BMS docs. My problem is that even though I’m launching with ‘Without any setup override’ - the default profile won’t work in the sim.
I have the Logitech profiles selected correctly and the correct keyfile loaded. tested the buttons in 2D and they work correctly but nothing happens when i enter 3D. No buttons on the HOTAS work at all.
Just to confirm:
1. As to the Alternative Launcher, there is no loading different profiles. It uses BMS - Full.key and I’m not sure how it manages axismapping.dat and any other files. But the long and short of it is that if you have your button/keybinds in a profile other than BMS - Full.key I think you will fail. That’s why you rename the BMS - Full.key to something else and rename your X52 profile to BMS - Full.key to take it’s place as I described a couple of posts back.
2. I’m not sure what the “without setup override” function’s purpose is. So you may be using it for its intended purpose I don’t know. But if you aren’t using the alternative launcher for it’s stability in keeping the HOTAS mapped correctly between sessions, then I’d consider going back to the stock launcher, at least until you get some better support than I can provide.
-
Thanks for the reply Vandal! That makes sense, I’ll give it a try!
One other oddity that I’ve noticed since using the alternate launcher is that I’ve lost the ability to use the mouse scroll wheel on cockpit wheels like the QNH knob and the UFC brightness wheels. I have my view FOV axis set to the mouse scroll but I always have and it hasn’t conflicted with those in the past. Any ideas?
-
Huh, so strange. Renaming the .key file from the default “BMS - BasicDX X-52pro.key” to “BMS - Full.key” worked for one instance, but the radar slew is doing that runaway thing where you move it in one direction and then centre the stick but the slew keeps moving indefinitely. Then exited 3D, checked the setting and loaded back into 3D and now none of the keypresses on the HOTAS do anything again. Shows they are working in the 2D screen but nothing in 3D.
About to give up on this.
-
@DUSTOFF17:
Thanks for the reply Vandal! That makes sense, I’ll give it a try!
One other oddity that I’ve noticed since using the alternate launcher is that I’ve lost the ability to use the mouse scroll wheel on cockpit wheels like the QNH knob and the UFC brightness wheels. I have my view FOV axis set to the mouse scroll but I always have and it hasn’t conflicted with those in the past. Any ideas?
I use AL and my mouse wheel works both FOV and QNH knob etc. So my guess is that somehow you got a setting changed somewhere. I’m not at my gaming PC today and probably not much this weekend otherwise I’d look for you. If you don’t get an answer from someone else send me a DM on Monday and I’ll see if I can figure out what might cause that.
-
Thanks Vandal, really appreciate your swift help!
I’ve head a breakthrough though!So i cut away trying to use the default X52 Profile that comes from the docs folder. For whatever reason, it and the alt launcher just don’t get along. even when i rename it to the BMS - Full.key. In the 3D world it just stops registering keypresses after approx 15 seconds!
Anyway. The issue with the scoll wheel not working on dials in the cockpit was fixed by deselecting the mouse wheel as the FOV axis in the alt launcher and leaving that field blank! It still works as a FOV axis by default which I didn’t realise.
My other little victory is that I’ve figured out how to use the best elements of the default profile that I like whilst just using the alt launcher to set all axis and key mappings and the logitech profiles for the bare nuts and bolts. Using the default “BMS X-52pro_DX.pr0” that comes in the docs folder works to use the mode switch for MRM/DF/CANCEL like a charm.
The only remaining problem I have is that the RDR cursor slew is still runaway. I’ve read online many posts and even in the “BMS Device Setup Guide.pdf” where it talks specifically about the press and release of the ‘shift key’ modifier before and after the ‘DX’ but what is frustrating me is that I’m using the default Saitek/Logitech .pro file supplied by BMS. So surely they wouldn’t have buggered that up in their file, right?
-
Do you have the cursor slew bound to th ministick or one of the 4 way switches?
Gesendet von meinem SM-G930F mit Tapatalk
-
Do you have the cursor slew bound to th ministick or one of the 4 way switches?
Gesendet von meinem SM-G930F mit Tapatalk
Using the default .pr0 provided by BMS, It’s bound to the mini-stick using the logitech profiler. I can always revert it to using a 4-way hat but I was really hoping to get the ministick working to free up the throttle hat for COMMS switch and another function.
-
You can just overwrite Hub.exe and other stuffs from v1.51 for update.
v1.40 had issues with overwrite check option, it is solved now.
….Sorry If only now I replay, but last question on the update from 1.4 to 1.51: does this update overwrite all settings I have done with the old key mapping for which I must to reset what I had set?
I don’t suppose because every change should be save into a key file, don’t you?