@Flow32:
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
it’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)
@dawgboy:
Howdy, coolts.
What did you put into your key file to get the POV2ID to map?
TIA,
db
for 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 Rudder
my 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 OVERRIDE
note 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