Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments)
-
Do you have FBMSALTERROR.txt in C:\Falcon BMS 4.34\ ?
-
Do you have FBMSALTERROR.txt in C:\Falcon BMS 4.34\ ?
No!
But in your installation, under the directory of C:\Falcon BMS 4.34\Bin\x86\ , I read that you have another file Falcon BMS.exe that I have not in that position. Did you copy it from the original position.
PS
ehy guys, please wait! I have seen that there anotherf file to download “Dlls.zip” that I haven’t doawnloaded. Have I to extract it in the same position as I have done with “Falcon_BMS_Alternative_Launcher”??Hope this can solve the issue…
-
Well, after many attempts appear that program has been installed: it was necessary to extract and install in “_C:\Falcon BMS 4.34\Bin\x86_” the missing file “dlls.zip”….All’s well that ends well
-
I have a question about the default FOV when using the Alternative Launcher. I searched in this thread, and in the forum in general; apologies if this has been answered elsewhere and I didn’t find it.
I’ve installed the Alternative Launcher and it seems to work very well with 4.34. Many thanks for such a great tool! I finally have the ability to use “shifted” HOTAS buttons, and it’s great. I can use the pinky shift to do all sorts of things now, like using my left MFD brightness rocker switch as my Master Arm switch. Very helpful! (My MFD is on an iPad-holder stand just behind and above my TQS, so it’s very easy to reach this rocker switch with the fingers of my left hand, even while my left hand is still resting on the TQS. So nice!)
There’s one thing that works differently than it did before I installed the A.L., and I can’t figure out why. Whenever I start a mission, I spawn into the cockpit with my FOV really extremely zoomed-in. In other words, a really small FOV, even though my default FOV is set to 75 degrees in the BMS Configuration. Sometimes it’s like I’m looking at the ICP with a magnifying glass. Or like I’m looking at a screw head near the HUD projector lens with a magnifying glass.
I’ve assigned my mousewheel as my FOV control. That’s the same thing I was using for FOV control back when I was using the “stock” BMS launcher UI. I had my default FOV set to 75 degrees before I was using the alternative launcher. Once I started using the alternative launcher, I clicked on the Configuration button and made sure the default FOV was still set to 75 degrees. I’m using a Logitech G502 mouse with a free-spinning mousewheel.
A quick rearward spin of the mousewheel gets me out to a nice wide FOV, but I don’t understand why this behavior has changed. Is there another setting I should be checking?
Sorry to complain, it’s not a huge point. More of a minor inconvenience. Overall, though, the Alternative Launcher seems to be a very nice utility, and it has finally given me the ability to use shifted HOTAS controls, which is something I’ve been dreaming of for a long time! Thanks very much for this utility!
-
Unassign mouse wheel from FOV. Wheel should still work as FOV without assigning it to FOV axis and default FOV should be applied then.
-
That worked! Thank you very much! :mrgreen:
-
Apologies if this has already been answered (I can’t seem to find anything), but could you tell me where the alternative launcher keeps its configs?
To clarify: I back up my keyfile regularly, but I can’t load that backup into the alternative launcher. So in the case of a reinstall, I have to redo my controls from scratch in the alternative launcher if I want to use the alternative launcher to change something.
-
@Mar:
Apologies if this has already been answered (I can’t seem to find anything), but could you tell me where the alternative launcher keeps its configs?
To clarify: I back up my keyfile regularly, but I can’t load that backup into the alternative launcher. So in the case of a reinstall, I have to redo my controls from scratch in the alternative launcher if I want to use the alternative launcher to change something.
Alternative Launcher Configs are saved in User/Config directory as setup.v100.<devicename>.xml</devicename>
-
Thanks, would that include the Setup.ver file I see there too?
-
Setup.ver is not an alternative launcher related file. You don’t need to back up that.
-
Got it, thank you!
-
Thanks
-
Good Day, All, I’m loving the AL, but do have a question. Since I have started launching BMS via AL, I’ve seen frequent “axis creep”, for lack of a better term. Particularly in the throttles on the Super Hornet. The rpm values can vary from engine to by 10, or in one memorable instance, 50 %. In other words, one or the other goes into 'burner at half throttle. On deck one rpm is at idle and the other is 80% or more.
Another thing I have seen is when flying on autopilot. If I use the paddle switch to disengage the autopilot,I see the throttle move by itself and hear the 'burner sound. It’s like the Hornet’s autothrottle is engaging without me engaging it.
This has all started since I started using AL. When I enter BMS with the standard launcher it seems better. If I go in via AL but check the “no override” box, it also seems better. It may(still testing) also be better in the Hornet the the Rhino-F. -
Hi all. I have not been able to figure out how to set up pinky switch for dx shift. Im sure it is something simple I’m missing but dont see it. When I double click on the pinky switch (dx Shift) then press the pinky switch nothing happens. It just keeps saying awaiting input when I press the pinky key. To be honest I have never had to program my hotas, but since the upgrade to 4.34 I now need to make my own. Cant use the keyfile editor excel sheet because win 10 wont run the macros for reasons I cant figure out either. I have searched and read manuals to no avail. I know the button physically works. All other setup methods see it depressed and released. Inlcuding the mfd on the throttle. I have a saitek x52 non pro on win 10. I am not using any sst programs and hit clear on the tray icon and MFD on throttle confirms no program installed.
-
-
Hi all. I have not been able to figure out how to set up pinky switch for dx shift. Im sure it is something simple I’m missing but dont see it. When I double click on the pinky switch (dx Shift) then press the pinky switch nothing happens. It just keeps saying awaiting input when I press the pinky key. To be honest I have never had to program my hotas, but since the upgrade to 4.34 I now need to make my own. Cant use the keyfile editor excel sheet because win 10 wont run the macros for reasons I cant figure out either. I have searched and read manuals to no avail. I know the button physically works. All other setup methods see it depressed and released. Inlcuding the mfd on the throttle. I have a saitek x52 non pro on win 10. I am not using any sst programs and hit clear on the tray icon and MFD on throttle confirms no program installed.
Just had the same issue.
see post #16 here:https://www.benchmarksims.org/forum/showthread.php?37486-TARGET-Software-issues/page2
-
So I’m having an issue I drop the hub and hub.exe.config into the x86 folder yet the alternate launcher won’t launch I click on it and nothing happens and I’m not sure why it’s not working.
-
Did you try this from the download page?
“If the Hub.exe does not launch, put DLLs to /bin/x86/”
-
thank you that was it
-
Pardon my ignorance, as I’m new to BMS and AL.
On my T.16000m Flightpack setup I wanted to setup my twist stick to look left and right and my throttle paddle’s for up/down, but I suspect this won’t be possible.
Barring that, is there an editable file in AL that would allow me to at least invert the up/down axis on my POV hat?