Solved Alternative Launcher POV Hat DX Codes on ICP
-
I just bought an ICP and mounted it, but using the Alt Launcher to program the switches and axes etc, it doesn’t recognise the DCS 4-way switch as it sees it as a POV switch, every othe switch and axis works fine. Is there a way to identify what the DX codes are for the DCS switch so I can manually insert them into my keyfile?
-
@fisty was it one from Sebastian Murawicki? I really like mine!
Basically, because the Alternative Launcher currently allows you to tie a POV to a device that has a flight control axis, you can’t as far as I can tell. I tried to override with some .cfg setPOV lines but I couldn’t. Decided to just use Joy2Key, simple solution but did cost $7USD. If it’s Sebastian’s, he has some other file options if you want to try them.
-
Thanks Snake. Just after posting this question I thought of J2K as I use it for OBS (push-to-talk), so I solved it with that. Thanks for posting.
-
-
@fisty I think AL has a long-standing limitation that it doesn’t support multiple devices with POV hats.
https://github.com/chihirobelmo/FalconBMS-Alternative-Launcher/issues/41
https://github.com/chihirobelmo/FalconBMS-Alternative-Launcher/issues/26Sounds like it’s possible to get this working, with some manual tweaks to cfg file and key file… but it’s not clear to me if AL can then continue to be used, to maintain and modify key bindings, or if it overwrites the tweaks.
Search the Technical-Manual for
g_nNumOfPOVs
etc and remember to pay close attn to your DeviceSorting.txt file… the docs are a little unclear on how to number the lines, so you may have to do some trial-and-error.HTH
-
Thanks for the advice @airtex2019. I think I’ll have to try that but I have a Sqn flight tonight so don’t want to mess with it before then. I’ve tried everything to get that DCS switch working. Joy2Key has no problem switching it to the cursor/arrow keys and the same with AntiMicro - the key presses are recognised in other programs such as MS Word, even the desktop recognises them as my highlighted icon moves with every move of the DCS switch! But it still won’t work in BMS. I can’t even find the DX codes for each DCS switch axes to edit the keyfile manually because it’s not recognised by BMS and the manual doesn’t have the part in there any more about how to find device DX codes. I’ll give it some more thought after tonight and re-post if I come up with a solution.
-
@fistyprobably knows this, but just for reference if this thread comes up for a search later, normally if any key commands are not being recognized in BMS but is outside of it, it is due to that utility not being ran as administrator. If it is DX not being programmed, it BMS not detecting over over the first 32 DX buttons.
@airtex2019 I tried multiple setups of the manual .cfg POV commands to override the AL POV issue and I couldn’t find a way to make it happen.
-
@fisty said in Alternative Launcher POV Hat DX Codes on ICP:
I can’t even find the DX codes for each DCS switch axes to edit the keyfile manually
Just to remove doubt … the hat inputs don’t have dx codes the way buttons do.
Well it depends on the stick of course… my VKB Gladiator NXT has several 4-way switches that are just clusters of DX buttons, but one 8-way hat switch that is a true hat (so, no DX button number).
BMS only supports up to 2 eight-way hats (can be on same device or on separate devices)… and you have to use DeviceSorting.txt and g_nPOV1DeviceID,g_nPOV2DeviceID to spell all that out.
[ps: Looks like someone on BMS team recently cleaned up and clarified sec.
10.8.3 How to use POV hats on two devices
so kudos to that fine person!] -
Necroing this a little. Looking to see if the now Launcher has fixed this somehow and I missed this. My new motherboard is reordering my joysticks quite often, resulting in Joy2Key moving mapped keyboard arrow keys to my ICP POV switch (similar to the reason to use the AL in the first place ). I can get the POV codes to work as my second POV if I add the correct .cfg lines, manually code them in a .key and load the associated .key manually so my code work is right. But the launcher of course loads the BMS - Auto.key and overwrites any changes to it. Just checking that the only POV possible still is the one(s) mapped to your flight control axes device.
-
@Snake122
https://github.com/chihirobelmo/FalconBMS-Alternative-Launcher/blob/master/Falcon BMS Alternative Launcher/Override/OverrideSettingFor437.cs#L58Looks somewhat hard-coded (hard-configured?) …
pov1 => first hat on your stick device
pov2 => first hat on your throttle deviceBut there are changes for U1 that we don’t have the source code for, yet so can’t say 100%.
-
@airtex2019 ok thanks! I think I found how to have Joy2Key always have my ICP as the same in the order so I probably don’t need this now, but it was a fun refresher on . key coding