Error msg at mobiflight start

[abstract tendon]

i getting an error msg while mobiflight start.
Error msg say "Axis cant be mapped: vkbsim gunfighter mcg ultimate aspect: position offset:4 usage : 186 axis: seitenruder label: unknown"

I believe it has something to do how i use/configured my stick. i am using 2 pov switches with 2 axis each+ t rudder + dif brake. So in total 9axis. To make this happend i export the rudder and dif brake function to a virtual controler device within the vkb configuration. So rudder and brakes running on its own vc. So windows can see stick1 (6axis,2pov), stick2 (3axis,4pov ). Mobiflight detect the devices as 2 equal named "VKBsim Gunfighter MCG Ultimate" device. So i believe mobiflight have a problem to handle the both devices properly. I am no expert with this. In a time i used the same stick without a virtual controller, 2 axis less (7 axis,1pov) i didnt got this error msg.

Another explanation could be that pov2 is using both assigned axis as trimmer switch and mobi have problems with this.

For the function i have experience no restriction besides the error log. I dont use the axis at all with mobiflight.

Mobiflight v. 11.0.1
vkbsim GF v.2.18F

[cerulean willow]

Can you show me your axes in vkbdevcfg?

I generally recommend only using the generic axes (x, y, z, rx, ry, rz, slider and dial), rather than specific simulation control axes

[cerulean willow]

That looks okay... try going to the tools tab, make reg file, and open that file in windows explorer. That can clear some cached directinput data in windows

Also, in pic 3/4, the logical axes tab is more interesting than the axes2buttons tab

[abstract tendon]

Yes, true. My mind was off.
I imported the reg file and now make sys restart.

[cerulean willow]

can you set axis 11 HID usage to Rot Z? And maybe 14 to Rot X or something?

and then import the reg file again just to be sure that data is gone

[abstract tendon]

I did. But with no change in mf behavior. As soon as i change the hid name for laxis11, the diff brake axis stoped working (slilder1 pic9)

[cerulean willow]

sorry, I was being stupid there. Axis 11 was fine as Y, Axis 10 should have been Rot Z. My bad.

[abstract tendon]

Bingo. This worked (Axis 10 should have been Rot Z,+reg import+restart). I had to reassigned the controller by hand in mobiflight projects at first start. now mobi is starting without any error. Thank you a lot.

Can you explain me in easy words what problem was with the hid naming?

[cerulean willow]

So basically, that "HID Usage" column has all those different labels you can apply to axes, and each of these labels is assigned a number. Mobiflight uses those numbers to map axes to a certain config.

However, most games only understand a fixed set of axes: X, Y, Z, Rx, Ry, Rz, Slider and Dial. So almost every controller on the market is built from the factory to use axes from the list of those eight.

Depending on how a game interfaces with controllers, Windows might help by mapping some of those other axis labels to one of the standard axes. Like Wheel becomes Z, Rudder becomes Rz, Throttle becomes Slider, stuff like that. Interestingly, Windows performs no such remapping for aileron/elevator axes.

Some software, like X-Plane, can also read directly from those other usages.

Mobiflight, at least in its current state, however, processes the usage IDs directly (that is how axis labeling works consistently across different OS languages on something like a Honeycomb Bravo), but that means it gets confused if a controller is using one of the non-standard ones like Rudder.