Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments)
-
@Lavender looking at your config file there are two XML files with different instance GUID. But for BMS they will look for the same productID like you can check with DeviceSorting.txt
-
@chihirobelmo So I should change it to match? does it matter that it’s purposely split into two devices in the VKB software to avoid the 32 button limit in some games?
-
does it matter that it’s purposely split into two devices in the VKB software to avoid the 32 button limit in some games?
I don’t own VKB but possibly… can you try connecting only X-56 and if the problem still happens or not? only for testing.
-
Ahh, what am I doing wrongly?
I installed F4 and 436 to a Hdd. Turns out, I already had F4 and 434 installed on the ssd. No matter, I didn’t uninstall the programms on the ssd.I didn’t run F4/BMS.
I then downloaded AL210 and started to set it up. It already had buttons mapped to the Warthog throttle, including Throttle POV. Nothing mapped to the stick. (This was the point where I realised I had BMS on the ssd).I tried to assign buttons to the Warthog stick (Warbrd base imitating a Warthog base) and couldn’t assign functions to the Stick POV. Query: is this a bug with AL210?
I thought it may be a bug, so I uninstalled AL210 and installed AL200. This time, I could assign functions to both Throttle POV and Stick POV.
I went to launch BMS through the AL, got a pop up about pilot names, so closed AL, started BMS, changed my pilot name, closed BMS, started AL200 and launched BMS.
Launched TE3/Takeoff and Landing. In game, some of my key binds are working (landing gear, I think!), most are not. Axes are working, including cursor.Should I do a full reinstall of F4, BMS and AL?
I’m running a Warthog HOTAS (Virpil gimbal) without TARGET and vkb Trudder, with TIR.
-
Nevermind, a pc restart and third start of AL/BMS and all seems to work (perhaps the first load of BMS without AL didn’t count).
The question above about AL2.1.0 and Stick POV remains.
Also, afterburner kicks in about 2/3rds of the way up the throttle. Is that realistic? How do I set the afterburner to start later on AL2.0.0? I couldn’t seem to find a function to do that in AL2.0.0.
Edit: Probably yes:
-
@mypc said in Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments):
Nevermind, a pc restart and third start of AL/BMS and all seems to work (perhaps the first load of BMS without AL didn’t count).
The question above about AL2.1.0 and Stick POV remains.
Also, afterburner kicks in about 2/3rds of the way up the throttle. Is that realistic? How do I set the afterburner to start later on AL2.0.0? I couldn’t seem to find a function to do that in AL2.0.0.
Edit: Probably yes:
IIRC all you do is go to Axisassign>Throttle: >ASSIGN>Clear> then move the throttle and the name should appear>move it to where you want the AB to kick in>clik AB DETENT>Save…
-
@chihirobelmo - I have an odd occurrence in 2.1. The columns listed are:
Thrustmaster Combined DX128 (my TARGET modified TM Warthog Throttle)
ICP
F16 MFD1
F16 MFD2
JOYSTICK - HOTAS WARTHOG
MFG CROSSWIND V2
VIRTUAL JOYSTICK (No idea what this is)When I assign the “Throttle:” Axis it shows my MFG Crosswinds RZ axis (MFGCW:RZ) as my throttle? It works, just strange. For my rudder “Yaw:” it’s JOY 5:RZ and not the MFG pedals, but again the function is perfect?
-
@chihirobelmo Without the VKB stick connected it just crashes on start up for some reason.
Edit: After reconnecting it now it crashes either way, I didn’t change anything else.
-
@Icer hmm I had similar issue maybe joy resorting is causing problems… will be fixed in 2.1.0
-
@Lavender said in Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments):
@chihirobelmo Without the VKB stick connected it just crashes on start up for some reason.
Edit: After reconnecting it now it crashes either way, I didn’t change anything else.
Does BMS crash or AL crash?
-
@chihirobelmo said in Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments):
@Icer hmm I had similar issue maybe joy resorting is causing problems… will be fixed in 2.1.0
This IS 2.10, maybe you mean 2.2? Again, function is 100% but it is reading something incorrectly… it can wait!
-
@chihirobelmo The launcher does when I go to start the game.
-
Hi, thx for the update. I’m still getting the F4patch lines as selectable theatres in the launcher. I tried manually removing the lines but no joy. Any fixes?
-
@DennisGRC @chihirobelmo same here I delete the lines and when I start AL they get back in there. Love AL by the way!
-
@danaos75 said in Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments):
@DennisGRC @chihirobelmo same here I delete the lines and when I start AL they get back in there. Love AL by the way!
This is a known and raised issue with @chihirobelmo .
I believe he had a major PC malfunction, so be patient.
https://github.com/chihirobelmo/FalconBMS-Alternative-Launcher/issues/58
-
@chihirobelmo Not sure if it was alternate launcher or something I messed up on my own, probably the ladder due to other changes I have been making in parallel with 4.36, but somehow in my Falcon BMS config file the set g_nPOV2DeviceID got set to a DeviceID of 2. It appears this was then in conflict with set g_nPOV1DeviceID which was also set to 2. This resulted in no button presses working when in 3D. AL was detecting the button presses and the button presses were detected and showing correct in the BSM controller settings in the UI. To correct it I changed g_nPOV2DeviceID to 3 and button presses were again working in 3D. Does AL do anything to set the g_nPOV2DeviceID?
-
-
So I was able to just reinstall and bind everything manually but the second I try to install and use the alt launcher it messes everything up, and uninstalling it after removes my ability to manually bind axes (buttons are still fine but it won’t remember any axis I bind). If I just don’t use it and play on a fresh install everything is fine but I would really love to be able to use the alternative launcher for changing theaters and stuff! I’m sure these XML files are the problem but I have no idea how to actually fix it.
@chihirobelmo said in Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments):
@Lavender looking at your config file there are two XML files with different instance GUID. But for BMS they will look for the same productID like you can check with DeviceSorting.txt
-
@Lavender Do you have 2 same joysticks in DeviceSorting.txt when you assign joysticks from the default UI?
-
@zeek AL considers a joystick that has roll axis as g_nPOV1DeviceID and who has throttle as g_nPOV2DeviceID. It should not set both g_nPOV1DeviceID and g_nPOV2DeviceID to duplicate IDs even if one device has both roll and throttle axis as the source divide the cases but I’ll recheck it. At least one of my friends with X52 setup working with AL though. What are your devices?
-
@chihirobelmo
My new SimGears ICP arrived recently.
The 3-position switch for GAIN/LVL/AUTO utilizes a virtual POV for the LVL (center) position.
AL shows this as „POV1.UP: Sim Gears IT“ but I‘m unable to assign anything to this.
In the falcon bms.cfg the parameter g_nNumOfPOVs is 2 (stick + WH throttle).
Could you have a look into this?