VKB-SIM

Is it possible to have physical axes 5 & 6 (ministick) control logical axes 5 & 6 by default, but control logical axes 13 & 14 when the button 34 is pressed? (with logical axes 5 & 6 kept at 0 when logical axes 13 & 14 are active and vice versa)
i.e. to have two logical ministicks and switch between which one is enabled & controlled by the physical ministick by pressing button 34, so that I can control two different slew control bindings independently (e.g. targeting pod slew control and radar slew control) using a single ministick.
Thanks!

Do you need axes in both modes in the game, on an airplane? What is wrong with controlling the radar with buttons in the POVs mode, and the aiming mark with the axes of the same microstick?

While controlling radar target designator with digital POV output is doable, I was wondering if it is possible to alternate between two "logical" analog ministicks, (instead of alternating between an analog ministick and digital POV), as analog inputs offer better control precision.
(Perhaps something to put on your software's development TODO list, if it is not possible at present)

Thanks

Show tabs Global-External, Profile-Axes, POVs. Are the pedals connected or not to the BlackBox GF?

Pedals are connected to a separate BlackBox.

There are pedals, but what does the twist do in this case? What do the axes on the top ministick do? I'm trying to figure out where it is possible to free up space for virtual axes so as not to use 10th and 11th on the second virtual controller.
The fact is that switching to virtual axes can only be on the first virtual controller (VC1). But you can move the 3,4 ministick axes to 10th and 11th, thereby freeing up space for virtual ones.
So, let's begin:
in Global we announce 2 Povs and a second VC

move 3rd and 4th to 10th and 11th axes

set them up in the same way, they will be relative

in the buttons we make a switch

making changes to POVs

it remains to configure the LEDs

When calibrating, select all. I would advise replacing the top ministick with a button module, disable the 3rd and 4th axes in External and then VC2 will not be needed. And then there will be no confusion in controllers under the same name, but with a different number of axes, for example, in FS2020.

Thanks!