Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments)
-
From javelin10–—With an x56 you would definitely want to assign the left ministick to Radar Cursor (Cursor X/Cursor Y) and probably use the right ministick as a 4-way hat for CMS up/down/left/right, as in the real HOTAS.
Hello Javelin and all knowledgeable about this: Thanks in advanced.
So, How do users like myself and others that have X52 PRO program the mini - stick that is on the right side of the throttle to control the Radar cursor. (((( ( specifically for for the X52 Pro))) using the Alternative Launcher??? You / javelin have it working on the X56 . We need your insite for the X52 Pro. We need to use the the X52 PRO’s ministick to control the Radar cursor and are thinking that we are missing something in Alternative Launcher to do this. Or do we need to continue to use the Logitech HOTAS software to do this by setting the X and Y bands as in the past.???
Thank goodness Logitech acquired Saitek.
Coincidently I have a X56 but only use it for a space flight simulation and not BMS. I got a replacement X56 after Logitech acquired Saitek. I had issues with the X56 that Saitek manufactured and after Logitech took over , Logitech sent me an replacement made by them. It was better built , especially the throttle. The throttle responded better ( but the throttle is still huge to operate , that’s another story. But no more jitters at least)) The original Saitek produced X56 units had many flaws and jitters. I was the lucky one that had issues with Saitek’s version of the X56. Thank goodness Logitech saved the day. -
This post is deleted! -
According to my experience with Saitek’s x52, the throttle ministick could be set to work as the mouse, or as two separate normal axis. I can’t remember if it works as the mouse by default or not, but you’ll definitely need it to work as two normal axis in order to assign it as the HOTAS cursor.
-
Yep Mar and thanks for the reply.
In the past most x52 and x52 pro end users had to create a profile (((*.pro type file)))) using the X52 Pro HOTAS’ programming software specifically to use the Ministick to control the Radar cursor. Otherwise all the other controls were programmed outside of the Manufacturer"s software by using DX created profiles . We were stuck with this method and unfortunately had to use the HOTAS software only for the mini stick because of the analog inputs the mini sticked used to communicate. Also We needed to load this profile ( *.pro file) prior to opening BMS and to make the mini stick control the Radar cursor and also the DX profile is loaded within BMS for the remaining controls.
SIDE. NOTE:
I have heard of people altering their Windows ’ OS" Registry to overcome this, but that is out of the question and a no no for most END Users .
I’m not certain if the ALTERNATIVE LAUNCHER made thE more cumbersome method mentioned above a little less cumbersome by including a feature that a user can select the mini stick for such controllers like the X52, X52 PRO and more …. as an input to control the Radar cursor.
-
Sorry to ask again but I need to be sure: How exactly do I backup my control configs (including keyboard) so I can load them into the alternative launcher again?
-
restore .xml files in User/Config
-
EDIT: ignore me, me stupid
Sigh
I restored the xml files and my keyboard configuration was not restored in the alternative launcher, only my controllers were restored. Now I’ll have to spend the next few hours redoing the keyboard through the alternative launcher.
Reinstalling BMS didn’t solve the problem I was having either.
-
If you don’t need the twist-rudder (because you have pedals) on the X52 PRO, the reg-edit procedure is not as scary as it seems. There is maximum number of axi (axis? axisses? lol) and buttons for any given DX-device in windows. The X52 HOTAS is a single USB DX device and is standard 1 axis short of this maximum. Ditching the Z-axis on the stick allows you to use 2 axis of the microstick. The other solution is indeed using the stick’s software to set it as bands.
The X56 AFAIK is actually a dual device (2 seperate units with 2 seperate USB connections) meaning it won’t hit this maximum. Probably the reason Javelin can make his microstick work in the Alternative Launcher?
Just a thought… been living under a rock lately ;).
How I wish my X65 had a seperate stick as well….
-
sorry, keyboard setup is saved to BMS - FULL.key
-
My fault. Geeze, I knew that, but last time I looked at it I thought it wasn’t reading BMS - Full.key, only writing to it. Turns out it does read from it and it was my own stupid fault for making a fuss. Sorry about that, and thanks for your help.
-
Why are the “KEYCOMBO/PINKYSHIFT” “RELEASE” and “Invoke Both” buttons on the main page of the KeyMapping UI, as well as when you double-click a specific keystroke to edit?
I want to assign a button on my throttle as a dedicated shift key, so I’m not sure if I’m supposed to assign the shift key universally, or uniquely under each key stroke line item individually.
For example:
DX2 is the key I want as my shift button.
DX6 is assigned to do whatever.
I want to have DX6’s secondary shifted function be, Trim Up - nose down.Thanks, I don’t want to risk messing up as I’m still very new to BMS and this thread is over 30 pages now, so I can’t read every post.
I think I am supposed to:
1. Double click the mapping for TRIM Up - Nose Down
2. Press “KEYCOMBO/PINKYSHIFT”
3. Press DX2
4. Press “KEYCOMBO/PINKYSHIFT”
5. Press DX6
6. Press “Save” -
@Mar:
Have you tested the throttle through windows control panel? Can you assign stuff to the stick hat and to the the throttle through the normal BMS UI?
Do you use voice attack? If so, Does that program recognize the joystick buttons? You can program it that way if it does
Thanks for the advice guys (sry, been busy with work, and I didn’t know you replied).
In the end, I decided to just leave it for now until I get Track IR, when I’ll be reassigning the hat completely. -
What will happen if you press “SET AB” button to set AB threshold?
what DX number is pinky button?
C, sorry it took so long to respond, I just saw this.
At first when I saw the “axis creep” I went into the regular BMS setup, and that seemed to fix it for awhile. But, right before my recent move it started doing it even with that work around, and after the move it didn’t work at all. I now suspect that the “creep” was the first symptom of my x-65 dying. I think that as I now have a Warthog, have assigned all axis’ via AL, and have seen no “creep” at all. -
Hey fellows.
I am having a bit of a problem with my hotas setup while trying to use this alternative launcher.I have the thrustmaster warthog flight stick and the T1.6000M throttle quadrant combined.
On the axis mapping page, the application cannot not detect the throttle to enable me set the throttle axis.
I managed to set Pitch and roll axes on the warthog flightstick correctly but no joy for the throttle.
Am I missing something or I need to tweak things in devicesorting file to get throttle to work.
Thanks in advance
-
Thank you Fluke. I have the x56, only use it for the sim Orbiter. Its bulky to be honest. When I first purchased it, (it was a new release then) it was produced by Saitek. Out of box it had some issues. I contacted Saitek. They were slow on the response. Found out why they were slow and not cooperative (when they did reply) , because Logitech was in process of acquiring them to some extent. Well when Logitech officially acquired Saitek, Logitech honored the warranty and sent me a replacement. I trashed the original one. They had me cut the wires and send pictures of it prior to Logitech shipping their replacement x56 to me. I happily did as they instructed, I had nothing to lose even if they didn’t. Saiteks X56 had some major issues. The new replacement works well, that is , when I use it. Regardless , of being very functional, it feels bulky to me (((bulky meaning, I need quick access to certain controls on the throttle, but the throttle handles are big and controls are far apart –- when simming in BMS, one needs to have quick access and the x56 controls are spaced too far apart )))))))), and I feel I need to have the hands of a 7-6" person that plays basketball to handle the throttles. But anyway, I may give the x56 a try again. I repacked it, since I run with BMS more so than Orbiter. Also, I got a complaint from the wifey, she said that there were, Too, many HOTAS on my 50" desk. Plus, honey you don’t use the other, so why not just pack it up until you have a need for it. So I packed it up and stored it and only reconnect it until the x56 is needed for like Orbiter or FSX (can’t wait for 2020 to come out). I have the x52 pro in use 98 percent of the time for BMS and other stuff. But anyway, thank you Fluke for your response. Appreciated. By the way, I’m using the KeyFile Editor, ((currently experimenting with the Alternative Launcher, has nice features. Thank you to the developer chihirobelmo), for most of the keymapping
and using Logitechs’ programming software to control the mini/micro stick. I just thought there was a tool that had everything built-into it so I didnt have to use multiple tools . Your the best thanks Fluke. -
Will we have to wait for an update to alternate launcher before we can use it with 4.34 U1 Or will alternate launcher work with update one
-
Seems the Alternative Laucher by default inverts the pitch axis for me and some others. I can untick the box in the advanced configuration settings in BMS itself, but the alternative launcher keeps putting it back.
-
I was having the same problem with the pitch axis. I am in the process of reinstalling everything. Will share what happens.
-
Ok did a complete fresh install of 4.34 and U1. Ran it no problem. Install Alt Launcher ran with out doing anything set up of my HOTAS and the pitch axis invert button was ticked. I really like the Alt Launcher hope there is a way to fix it.
using win 10
hotas x56 -
I was wondering if it is possible to change the y axis direction(invert) in the registry as a short term solution. If it is changed in the reg then when alt-launcher changes it again it would be right. I ask this because alt-launcher was the only way I could fix my device sort order problem so kind of need it.