Stick Trim hat and throttle POV hat cant be assigned
-
Using “BMS - BasicDX TM Warthog_MFD” which came with the game.
Stick POV shows nothing in controller GUI when pressed and neither does Throttle POV.Is there some odd DX llimit and i have too many buttons?
BMS has a limit of 32 buttons / controller + 2 POV for the main controller only.
So if you combine stick + throttle with TARGET for instance, you have way more than 32 buttons on your controller.
If you don’t, then you don’t have more than 32 buttons / device. You just need to make sure BMS sees them in the right order using the devicesorting.txt file in user/config -
I don’t combine them. Started reading “bms device setup guide.pdf”. Trim may be a shifted function. Will try later. As for throttle POV… no idea. I read somewhere it didn’t work with bms.
-
Make sure your devicesorting.txt is setup correctly. The Joystick should be at the top of the list. If it’s not setup correctly the buttons will not function as described. Also, It’s now possible to use multiple hats but you have edit Falcon Bms.cfg to enable the feature.
POV MAPPING: — Added possibility to override POVs mapping across different devices. (r19837) * New config vars (defaults shown here): set g_nNumOfPOVs -1 // Override number of POV hats. Should be in 0 - 2 range, -1 is override disabled (default) set g_nPOV1DeviceID -1 // Override POV1 hat device ID, -1 is override disabled (default) set g_nPOV1ID 0 // Override POV1 hat ID. Should be in 0 - 1 range set g_nPOV2DeviceID -1 // Override POV2 hat device ID, -1 is override disabled (default) set g_nPOV2ID 0 // Override POV2 hat ID. Should be in 0 - 1 range * Example for a Warthog setup (sets joystick POV as POV1 and throttle POV as POV2): set g_nNumOfPOVs 2 set g_nPOV1DeviceID 2 set g_nPOV1ID 0 set g_nPOV2DeviceID 3 set g_nPOV2ID 0
-
Make sure your devicesorting.txt is setup correctly. The Joystick should be at the top of the list. If it’s not setup correctly the buttons will not function as described. Also, It’s now possible to use multiple hats but you have edit Falcon Bms.cfg to enable the feature.
POV MAPPING: — Added possibility to override POVs mapping across different devices. (r19837) * New config vars (defaults shown here): set g_nNumOfPOVs -1 // Override number of POV hats. Should be in 0 - 2 range, -1 is override disabled (default) set g_nPOV1DeviceID -1 // Override POV1 hat device ID, -1 is override disabled (default) set g_nPOV1ID 0 // Override POV1 hat ID. Should be in 0 - 1 range set g_nPOV2DeviceID -1 // Override POV2 hat device ID, -1 is override disabled (default) set g_nPOV2ID 0 // Override POV2 hat ID. Should be in 0 - 1 range * Example for a Warthog setup (sets joystick POV as POV1 and throttle POV as POV2): set g_nNumOfPOVs 2 set g_nPOV1DeviceID 2 set g_nPOV1ID 0 set g_nPOV2DeviceID 3 set g_nPOV2ID 0
Thanks, yep, all controllers in order and showing correct DX numbers in BMS GUI, except for stick trim hat and throttle hat which don’t respond at all. Very odd. Both work fine in DCS. I need to find what DX number Windows gives them then reference that on the .key file. Might be something odd there. Mind you. 32 buttons per controller sounds a lot but the TM throttle has……a lot of buttons. That might be over the limit.
I did try the “alternative launcher” but as soon as i ran that it wiped all my configs back to the stone age…sigh. Back in the day i used to make my axismappings.dat file read only and keep backups of my .key files before devicesorting.txt was a thing.
ps. i didn’t know about the .cfg update. Where was that documented? I’ll check that out too. Cheers!
-
The warthog throttle has 32 buttons + 1 POV…. as said earlier.
Also, BMS does not look at the controller number given by windows, but looks at the devicesorting.txt file…
Have fun setting everything up, and look at the manual, it contains a lot of good information -
Found the trim issue. I installed ‘alternative launcher’ and it obliterated all my configs. Luckily it creates a backup folder and i restored them all. Won’t touch that again with a 10ft barge pole.
Still no throttle POV, but looks like i need to use Gastones fix to enable that.
[edit]
Adding this to .cfg worked! Cheers Gastone.
set g_nNumOfPOVs 2
set g_nPOV1DeviceID 2
set g_nPOV1ID 0
set g_nPOV2DeviceID 3
set g_nPOV2ID 0 -
This post is deleted! -
Found the trim issue. I installed ‘alternative launcher’ and it obliterated all my configs. Luckily it creates a backup folder and i restored them all. Won’t touch that again with a 10ft barge pole.
Still no throttle POV, but looks like i need to use Gastones fix to enable that.
[edit]
Adding this to .cfg worked! Cheers Gastone.
set g_nNumOfPOVs 2
set g_nPOV1DeviceID 2
set g_nPOV1ID 0
set g_nPOV2DeviceID 3
set g_nPOV2ID 0Howdy, coolts.
What did you put into your key file to get the POV2ID to map?
TIA,
db -
Using “BMS - BasicDX TM Warthog_MFD” which came with the game.
Stick POV shows nothing in controller GUI when pressed and neither does Throttle POV.Is there some odd DX llimit and i have too many buttons?
Hi, Coolts,
You can get the throttle POV functional using Voice Attack -
The warthog throttle has 32 buttons + 1 POV…. as said earlier.
Also, BMS does not look at the controller number given by windows, but looks at the devicesorting.txt file…
Have fun setting everything up, and look at the manual, it contains a lot of good informationit’s worth noting also that in the BMS UI, it sees the keyboard as device#1, Joy as #2 and so on thus the order for most would be:
1.KB
2.Joy
3.TQS
4.& 5 MFD L/R (if applicable)
6. Rudders (if applicable)Howdy, coolts.
What did you put into your key file to get the POV2ID to map?
TIA,
dbfor me I split my programming with the Realsimulator HID Tool software and in the Keyfile editor where if using the editor (found under Falcon BMS 4.34/Docs/01 Input Devices), you’d be programming the WH TQS POV under the “Primary” device (Joystick POV2) , I don’t user the stick POV for TRIM, rather I’ve moved the TRIM to my WH Throttle POV, thus opening up my stick POV (DX buttons 27-30, BMS 28-31) for views etc., ergonomically it works better for me. My mapping was as follows (note set g_nPOV2DeviceID 4) and I should note that I own Realsimulator F16SGRH-CE stick and R3L so my BMS device order is shown below first for device number reference:
1. KB
2. FSSB Stick
3. FSSB R3L
4. TM WH Throttle
5. MFD L
6. MFD R
7. Flight Control Ruddermy falcon bms.cfg entries (bottom):
set g_nNumOfPOVs 2 // SETUP OVERRIDE
set g_nPOV1DeviceID 2 // SETUP OVERRIDE
set g_nPOV1ID 0 // SETUP OVERRIDE
set g_nPOV2DeviceID 4 // SETUP OVERRIDE
set g_nPOV2ID 0 // SETUP OVERRIDEnote the #4 above matching the BMS UI device numbering, most users will have a #3, in my case (RS users) the stick & R3L force sensor count as 2 Joysticks (32 DX buttons each)
Throttle POV mapping (unshifted layer):
AFElevatorTrimUp 1 -1 -3 0 0x0 125
SimDoNothing 1 -1 -3 1 0x0 -1
AFAileronTrimRight 1 -1 -3 2 0x0 125
SimDoNothing 1 -1 -3 3 0x0 -1
AFElevatorTrimDown 1 -1 -3 4 0x0 125
SimDoNothing 1 -1 -3 5 0x0 -1
AFAileronTrimLeft 1 -1 -3 6 0x0 125
SimDoNothing 1 -1 -3 7 0x0 -1(Shifted layer, just insert whatever Callback you’d like):
Your callback here 3 -1 -3 0 0x0 -1
SimDoNothing 3 -1 -3 1 0x0 -1
Your callback here 3 -1 -3 2 0x0 -1
SimDoNothing 3 -1 -3 3 0x0 -1
Your callback here 3 -1 -3 4 0x0 -1
SimDoNothing 3 -1 -3 5 0x0 -1
Your callback here 3 -1 -3 6 0x0 -1
SimDoNothing 3 -1 -3 7 0x0 -1