-
I’m trying to get the POV2 to work. I have two joysticks each with one POV hat.
So far I’ve set falcon bms cfg lines to:
set g_nNumOfPOVs 2
set g_nPOV1DeviceID 0
set g_nPOV1ID 0
set g_nPOV2DeviceID 1
set g_nPOV2ID 0Desired number of POVs 2 should be obvious. My joystick is the 0th controller, 0th hat so I think those values should be 0, 0 respectively. The 1th controller is the Thrustmaster Combined, 0th hat so I assume those are 1, 0 respectively as shown.
Does the GUI setup>controllers>key-mapping area show when POV2 input is received? Currently only “POV 1 : _____” is shown below the table. Hmm I changed the POV1 device ID to 3 just to try to break it and GUI and in-game it still does trim.
What am I missing?
-
I’m trying to get the POV2 to work. I have two joysticks each with one POV hat.
So far I’ve set falcon bms cfg lines to:
set g_nNumOfPOVs 2
set g_nPOV1DeviceID 0
set g_nPOV1ID 0
set g_nPOV2DeviceID 1
set g_nPOV2ID 0Desired number of POVs 2 should be obvious. My joystick is the 0th controller, 0th hat so I think those values should be 0, 0 respectively. The 1th controller is the Thrustmaster Combined, 0th hat so I assume those are 1, 0 respectively as shown.
Does the GUI setup>controllers>key-mapping area show when POV2 input is received? Currently only “POV 1 : _____” is shown below the table. Hmm I changed the POV1 device ID to 3 just to try to break it and GUI and in-game it still does trim.
What am I missing?
I set up the warthog just like the change notes show and both now work and register in the gui setup.
set g_nNumOfPOVs 2
set g_nPOV1DeviceID 2
set g_nPOV1ID 0
set g_nPOV2DeviceID 3
set g_nPOV2ID 0 -
I tried that before and it didn’t work but now it does. Why 2 and 3? Is it keyboard = 1, joystick = 2, TARGET = 3? What if my devices are in a different order?
And I’m looking how things change on the key file:
AFElevatorTrimUp 0 -1 -3 0 0x0 -1
AFAileronTrimRight 0 -1 -3 2 0x0 -1
AFElevatorTrimDown 0 -1 -3 4 0x0 -1
AFAileronTrimLeft 0 -1 -3 6 0x0 -1SimTransmitCom1 1 -1 -3 0 0x0 -1
SimCommsSwitchRight 1 -1 -3 2 0x0 -1
SimTransmitCom2 1 -1 -3 4 0x0 -1
SimCommsSwitchLeft 1 -1 -3 6 0x0 -1OK, first digit after the callback is the ID of the POV1/POV2 so 0 to 1. OK that should work fine then thanks. Are POVs 3 4 5 6, etc. possible?
-
I tried that before and it didn’t work but now it does. Why 2 and 3? Is it keyboard = 1, joystick = 2, TARGET = 3? What if my devices are in a different order?
I wonder too. What I know is that it doesn’t exactly follow the device order set in the DeviceSorting.txt file : I have one POV on my joystick and one POV on my throttle, respectively 1st and 2nd line of the file, (and I don’t use TARGET or any other similar software) but I had to write
set g_nNumOfPOVs 2
set g_nPOV1DeviceID 2
set g_nPOV1ID 0
set g_nPOV2DeviceID 3
set g_nPOV2ID 0
as you did in the falcon bms.cfg file to make it work, even though logic seemed to lean towards the first solution you tried. -
This is just a wild guess as I haven’t tested the config stuff prior U1 release (will do before 4.35 though):
I think it is the Windows device order, not the one applied in the devicesorting.txt.
However, if this is true we might change that to match the order defined in devicesorting.txt.As of now the limit is 4 POV hats or 4 layers (2 unshifted, 2 shifted).
-
So I setup my second POV hat as POV2 successfully but then was doing some testing and I added another controller to BMS and then the POVDeviceID changed. Before adding a third device my POV1DeviceID was 2 and POV2DeviceID was 3. Once I added the third controller the POV2DeviceID changed to 4 and no longer worked as POV2DeviceID 3.
These additions of POV functionality is wonderful but … it would be nice to have some info on how these new POVDeviceIDs are determined. I see several posts here with people trying to figure out how its implemented so they can understand the configuration rather than guess and do trial and error.
I’m not a hater so please no roasting is required. Just pointing out a few things.
-
Frederf, I’ve sucessfully got the Warthog POV2 to work via Voice Attack.