Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments)
-
Mouse whell works with acceleration so simply scroll your mouse slow and you get +1 scroll fast and you get +5 default timing is 60 ms between 2 scroll clicks, if you want to apply that to DX or keyboard inputs as well you could add the g_nKnobAccelerationDelta to your falcon bms.cfg file. setting this to a value will change the timing for the mouse wheel as well so setting it to 100 change the default 60 ms to 100 ms
g_nKnobAccelerationDelta When set to 0 it will make the “By1” and default “By5” callbacks
work without acceleration, i.e. By1 =1 and By5=5. Default = 60
milliseconds in which the next input has to occur.If g_nKnobAccelerationDelta is not 0 it will not change the
“By1” callbacks at all. Instead the “Normal” callbacks will
behave as “By1” if used once and accelerated to “By5” if used in
rapid succession. Basically if you move the controls slowly you
get By1 increment, if you move them faster you get By5
increments. Use SimHsiCourseInc, SimHsiCourseDec,
SimHsiHeadingInc, SimHsiHeadingDec, SimAltPressInc,
SimAltPressDec “normal’ callbacks for acceleration to work, not
the By1 callbacks. -
Yes. I am running 4.35 and 1.60. I tried your method and no joy. I guess I am too thick to get this to work. Will keep trying though. When I click on the shortcut, nothing happens.
Ok, how about if you go to the folder that contains AL 1.60 and dble-clik the “Hub.exe” file in there, what happens?
I’ve attached pics of my AL folder structure and also the contents of the beginning of “Setup.ini” in the AL folder for comparison. -
Icer: I get the hour glass for 2 seconds and then nothing. There does not appear that any of the little Microsoft program are needed for AL so I have no idea what I am doing wrong.
-
Icer: I get the hour glass for 2 seconds and then nothing. There does not appear that any of the little Microsoft program are needed for AL so I have no idea what I am doing wrong.
I’m at a loss, you have run BMS 4.35 without it at least once, yes (using “Launcher.exe” in the x:/BMS 4.35 folder)? Did you already follow the “normal” install instructions replacing “Hub.exe” before trying my method?
-
Thank you for putting this app together - as a new user I really appreciate it.
My apologies as the instructions for install are very clear - it is just as I have no experience of backing up registry files - is there a post that runs through this step by step? Wanted to avoid going through google / microsoft forums to work it out if it has been covered.
Also wanted to check that the app would help resolve an issue I have with my T.Flight Hotas One (appreciate this is not an ideal joystick choice) - the standard launcher is not recognising my throttle axis - and instead is forcing me to use the finger rocker on the front on the joystick. It has latest drivers and firmware and works OK on other sims (IL2 e.t.c.) - will your app enable me to force BMS to let me use the throttle.Thanks
-
Thank you for putting this app together - as a new user I really appreciate it.
My apologies as the instructions for install are very clear - it is just as I have no experience of backing up registry files - is there a post that runs through this step by step? Wanted to avoid going through google / microsoft forums to work it out if it has been covered.
Also wanted to check that the app would help resolve an issue I have with my T.Flight Hotas One (appreciate this is not an ideal joystick choice) - the standard launcher is not recognising my throttle axis - and instead is forcing me to use the finger rocker on the front on the joystick. It has latest drivers and firmware and works OK on other sims (IL2 e.t.c.) - will your app enable me to force BMS to let me use the throttle.Thanks
Took Icer’s advice in an earlier post on this thread and just unzipped inside BMS 4.35 - haven’t backed up any registery but it all works fine. And I have been able to set up the throttle on the T.Flight Hotas One OK and it is now working properly. Great app - can’t thank you enough, and thanks to Icer for the post.
-
Took Icer’s advice in an earlier post on this thread and just unzipped inside BMS 4.35 - haven’t backed up any registery but it all works fine. And I have been able to set up the throttle on the T.Flight Hotas One OK and it is now working properly. Great app - can’t thank you enough, and thanks to Icer for the post.
Glad it works for you now but I do not touch the 4.35 (or 4.34) installations. It is run from a folder completely separate from my BMS installation(s), as are WDP and MC so a uninstall/reinstall of BMS has no effect on these apps… I outlined it again earlier today in your other posting. Pic of both running away at same time blissfully…
-
From post #632:
1.60 Released, Now Supports BMS 4.35.
To Transfer setup files to 4.35, copy all XML files in User/Config from 4.34 folder to 4.35.
https://github.com/chihirobelmo/Falc…ases/tag/v1.60
All I had to do was transfer those files and all my mapping worked as it did with old version.
I did just this and no joy. AL fires up 4.35 but the keyboard commands didn’t transfer.
-
My new Warthog Throttle has many toggles but only creates a DX press/hold in the forward (ON) position. It seems that I can set a “Release” state for the OFF position but BMS does not see it. Am I doing it incorrectly or is this not possible? Here is a pic, using the RDR ALTM switch on the throttle to send a DX25 press for “NRM” (ON) and a DX25 release for “DIS” (OFF)… Please advise…
Edit: No idea what I did but it works perfectly now as I have it set up… In the interim I found an older AL ReadMe with the P/R instructions but don’t think it works that way anymore…
-
Does the current version work on U1?
-
-
I did just this and no joy. AL fires up 4.35 but the keyboard commands didn’t transfer.
From memory this was my experience as well. The xml files have some sort of id in the filename (inside curly brackets) which is probably significant in a way I don’t understand.
-
I have been advised to add the “-mono” option to the launcher in order to try and get crash reports for 435.
I am wondering if this is what the “Debug” button in Alt Launcher does, or if a separate button could be added for “-mono”
EDIT: Just done my own testing and “Debug” does seem to be equivalent to “-mono”
-
Hi all,
Thanks for this great toolI have a little problem with the x52 pro joystick.
I wanted to use the mouse stick as I did before, like a 4axis hat, but when I make the change in the logitech program and go back to the alternate launcher, the pinky is no longer recognized.An idea ? someone who had the same problem?
Thank you in advance for your assistance -
So I have a franken-stick where I have a t16000m base using a CH fighterstick grip. Each device uses its own USB plug so when I open Alternative Launcher, I see both the T16000m and the Fighterstick as mappable devices. The pitch and roll axes are controlled by the T16000m, but I want to use the hat switch on the grip to control my trim. However, Alt. Launcher will only recognize the hat switch on the device that controls the roll/pitch axes (t16000m).
Is there any way around this?
-
@abfagin:
So I have a franken-stick where I have a t16000m base using a CH fighterstick grip.
That sounds awesome. I don’t know about Alt Launcher but if you point me to any photos/videos or guides to do that… I will try to help guide you through hand-editing the .cfg and .key files…
\Falcon BMS 4.35\Docs\BMS-Technical-Manual.pdf
sec 10.8.3\Falcon BMS 4.35\User\Config\falcon bms.cfg
set g_nNumOfPOVs 1 set g_nPOV1DeviceID 3 // this will depend on order of rows in your DeviceSorting.txt file, see sec 10.8.3
There is some inconsistency in the docs about whether you count the rows in DeviceSorting.txt, starting at “1” or “2”. You may have to try it both ways…
There is also some ambiguity, for your case, of only having 1 hat but on a secondary device, whether that becomes dx-hat #0 & #2(shifted) or #1 & #3(shifted).
You can probably just hedge that, by just assigning the same set of callbacks to both 0/2 and 1/3.
Here’s what my key file section for dx hat bindings would look like… you can probably copy/paste and modify as you like…
[Edit: if your key file is not super well organized … I think the signature thing to search for (eg. use [ctrl+F] in notepad) to locate all the hat-bindings is the " -1 -3 " sequence… as far as I can see that doesn’t occur anywhere else in the stock key files.]
##---------------------------------------- ## Primary POV Hat => slew cursor + elev/range SimCursorUp 0 -1 -3 0 0x0 -1 SimRangeKnobUp 0 -1 -3 1 0x0 -1 ## NE => man-rng knob, zoom in SimCursorRight 0 -1 -3 2 0x0 -1 SimRangeKnobDown 0 -1 -3 3 0x0 -1 ## SE => man-rng knob, zoom out SimCursorDown 0 -1 -3 4 0x0 -1 SimRadarElevationDown 0 -1 -3 5 0x0 -1 ## SW => ant elev, down SimCursorLeft 0 -1 -3 6 0x0 -1 SimRadarElevationUp 0 -1 -3 7 0x0 -1 ## NW => ant elev, up ##---------------------------------------- ## Primary POV Hat (shifted) => TMS switch SimTMSUp 2 -1 -3 0 0x0 -1 SimDoNothing 2 -1 -3 1 0x0 -1 SimTMSRight 2 -1 -3 2 0x0 -1 SimDoNothing 2 -1 -3 3 0x0 -1 SimTMSDown 2 -1 -3 4 0x0 -1 SimDoNothing 2 -1 -3 5 0x0 -1 SimTMSLeft 2 -1 -3 6 0x0 -1 SimDoNothing 2 -1 -3 7 0x0 -1 ##---------------------------------------- ## Secondary POV Hat => same bindings as above SimCursorUp 1 -1 -3 0 0x0 -1 SimRangeKnobUp 1 -1 -3 1 0x0 -1 ## NE => man-rng knob, zoom in SimCursorRight 1 -1 -3 2 0x0 -1 SimRangeKnobDown 1 -1 -3 3 0x0 -1 ## SE => man-rng knob, zoom out SimCursorDown 1 -1 -3 4 0x0 -1 SimRadarElevationDown 1 -1 -3 5 0x0 -1 ## SW => ant elev, down SimCursorLeft 1 -1 -3 6 0x0 -1 SimRadarElevationUp 1 -1 -3 7 0x0 -1 ## NW => ant elev, up ##---------------------------------------- ## Secondary POV Hat (shifted) => same as above SimTMSUp 3 -1 -3 0 0x0 -1 SimDoNothing 3 -1 -3 1 0x0 -1 SimTMSRight 3 -1 -3 2 0x0 -1 SimDoNothing 3 -1 -3 3 0x0 -1 SimTMSDown 3 -1 -3 4 0x0 -1 SimDoNothing 3 -1 -3 5 0x0 -1 SimTMSLeft 3 -1 -3 6 0x0 -1 SimDoNothing 3 -1 -3 7 0x0 -1
-
Thanks Airtex,
I read through the Technical Manual and found what you’re referring to with regards to editing the config file and assigning the correct device ID. Unfortunately, it seems that alt. launcher overwrites my changes so unless there’s a way to prevent that overwrite from occurring, I’ll have to stop using alt. launcher or deal with not being able to use the POV hat on the CH stick?
-
Darn. Might have to open an issue at https://github.com/chihirobelmo/FalconBMS-Alternative-Launcher/issues
Maybe 3 or 4 issues… definitely it should
(a) throw a warning at startup if it encounters something in the keyfile (eg. multiple hat devices) which it can’t roundtrip serialize, and
(b) not overwrite your key file if you didn’t make any changes, and
definitely not overwrite it if you set the file to readonly -
Darn. Might have to open an issue at https://github.com/chihirobelmo/FalconBMS-Alternative-Launcher/issues
Maybe 3 or 4 issues… definitely it should
(a) throw a warning at startup if it encounters something in the keyfile (eg. multiple hat devices) which it can’t roundtrip serialize, and
(b) not overwrite your key file if you didn’t make any changes, and
definitely not overwrite it if you set the file to readonlyFWIW I was able to resolve this by doing the following:
1. Turning off setup override in AL. Upon launch, AL was over-writing the device ID I wanted the POV hat to be associated with.
2. After turning off setup override, setting the device ID’s accordingly in the “falcon bms.cfg” file, as you suggested
3. Opening up the Full key file and manually adding the code from the first two bullet points of section 10.9.2 from the Technical Manual under the CH Fighterstick section of the keyfile.I suppose if I ever want/need to use AL again to make the keybinds easier, I can just disable the setup override, make the changes I want to make, and redo the 3 steps above.
Also, regarding the Frankenstick, I just followed
video. I didn’t use putty to affix the CH stick onto the T16000m base, but rather mocked up an adapter piece and had it 3D printed out of steel. I also didn’t snip the connectors off the wires of the CH Fighterstick as the video creator did, since crimping new connectors on would have been a huge pain, so I just had to feed the wires through the holes in the T16000m gimbal. Feeding the wires through the holes wasn’t terribly difficult, but it does require a lot of patience and some finesse (a set of small picks and small needle nose pliers is also vital). Taking pictures of how the gimbal is assembled and installed was crucial in making sure I was assembling the gimbal and feeding the CH Fighterstick wires through at the correct time to keep anything from getting pinched. I must have gone through this step 3 or 4 times and was a huge PITA. Lastly, this sounds dumb, but taking pictures of which end of the male connector (of the Fighterstick wires) is “up” when inserting into the female portion is crucial. Also it’s important to note that the male connectors have a little barb that needs to be pryed upwards to prevent faulty connections when reconnecting to the main PCB.Space Reserved for Cartoon Sketch
Threw some Nyogel on the gimbal pivot surfaces and I’ve been extraordinarily happy with it thus far. Resolution and accuracy is leaps and bounds better than the stock Fighterstick and I don’t have any stiction around center which I’ve heard some Warthog owners don’t like.
If it ever need to go through the process again due to parts breaking or intermittent connections, maybe I’ll take some pictures for posterity, since there was very little information out there on performing this mod.
-
Cool glad you got it working … what g_nPOV1DeviceID value did you end up using (relative to what row # is your CH stick in DeviceSorting.txt)?
Thanks for the video link … too deep for me … but yeah I agree I’d want some sort of rigid coupling.