Loss the function of one of the POV hat

[igorry]

Hi

Recently, after getting into setup and clicking the controller tab to test my buttons and pov, I was unable to see my throttle POV when I push the POV hat. My joystick POV can be seen when I push the joystick POV. Both POV used to work fine. I check device and game controller setting in windows and the POV is working fine.

I am using ch throttle and ch flighter stick and also two BU0836A joystick interface for buttons and axis only. Both the BU0836A were renamed and identified separatedly in the Devicesorting.txt

Can someone help on this and also if possible explain the following lines from user config? Could be that I need to set these lines correctly?"

set g_nNumOfPOVs 2 // SETUP OVERRIDE
set g_nPOV1DeviceID 4// SETUP OVERRIDE
set g_nPOV1ID 0 // SETUP OVERRIDE
set g_nPOV2DeviceID 3// SETUP OVERRIDE
set g_nPOV2ID 0 // SETUP OVERRIDE

Igorry

[airtex2019]

@igorry looks like you’re on the right track

The technical-manual.pdf describes those cfg parameters and how they map to lines in Device sorting.txt

[Frederf]

@igorry The 5 values have somewhat non-obvious relations.

NumOfPOVs: Total number of POV, valid values are -1, 0, 1, 2. In this case you want the maximum, 2.

POV1DeviceID: ID number of the controller device which POV1 takes input from, valid values are -1 and then 1 through the maximum ID count for devices. The ID for your device can best be discovered by looking in the SETUP section inside Falcon BMS and opening the drop down menu. The list will be: keyboard, deviceA, deviceB, deviceC, and so on. The ID number is the device’s placement in that list and because the keyboard is #1, the minimum practical value is 2 corresponding to the first device listed immediately below keyboard.

POV1ID: ID number of the POV belonging to the indicated device to assign to POV1. The DirectX API allows for multiple POVs to be defined per controller but in 99% of cases the first POV (POV0) is the only one. Normally use value “0” to choose the one and only POV from that device.

POV2DeviceID: Device ID number that will provide the input for POV2 (see POV1DeviceID)
POV2ID: POV number from the device indicated above that will provide input for POV2 (see POV1ID)

An example set of values:
set g_nNumOfPOVs 2 // Two POVs
set g_nPOV1DeviceID 2 //First joystick
set g_nPOV1ID 0 //0th POV from first joystick
set g_nPOV2DeviceID 5 //Fourth joystick
set g_nPOV2ID 0 //0th POV from fourth joystick

The confusing thing is DeviceID starts counting effectively from 2, 2 being the first ID after “keyboard” and POV_ID begins counting at 0, 0 being the first POV.

[igorry]

Thank you airtex and Frederf.

I managed to solve the problem and recover the lost POV. Indeed reading the technical manual and what Frederf suggested did help. On top of that, lots of trial and error because of my limited understanding!

I have to delve into the DeviceSort.txt file and get this right. At one stage I have to even go into the DeviceDefaults.txt .

At first I have the strange problem of not able to get rid of or change the x and y axis of my ch fighter stick to that of BU0836A x and y axis. It just wouldn’t let me. I have to use the DeviceDefault and physically input the CH FS x and y axis to be blank, that is to keyboard. Can’t do this in BMS controller page. Then I have to ensure my BU0836A is the second device and not the CH fighter stick in the DeviceSort. txt. I think the device that is to be x and y axis need to be the second device after keyboard.

Well I got it sorted in the end and it took quite a number of hours. I have to even remap my hotas but that is more a tedious exercise than a difficult one. Well thanks everyone.

Igorry