Using button to Fix Axis when the axis is logical
Posted: Thu Feb 27, 2020 1:00
I have an MCGO Pro with twist and a GF III base. I have T-Rudder Mk. IV pedals attached to the same BlackBox. Everything is on firmware 1.986 and I am using VKB Device Config v0.91.10.
I am trying to modify the behavior of a logical axis based on a button press. I have figured out how to do it for a physical axis (set the button to a "Fix Axis" function), but I can't figure out how to do it for a logical axis. I will attach some screenshots below, but first some context. I am trying to use the rudder pedals as virtual toe brakes in DCS. I tried setting up the pedals on a separate BlackBox and joining the MCG and the pedals with T-Link. I wasn't happy (and maybe it's just me), but I couldn't get the hang of how the rudder and brake axis worked together with a button press, and despite many many tries, I could never maneuver smoothly down the runway.
So, I ended up plugging the rudder pedals into the same BlackBox as the MCG so that I wouldn't need to use T-Link any more and so that I could get creative in the way the toe brake axes work. I came up with a configuration that makes sense and has allowed me to maneuver much more smoothly down the runway, but I am trying to tweak it further.
Under the current configuration, pressing the brake handle engages both brake axes equally as well as the brake handle axis. When I press the rudder pedals either to the left or to the right, the corresponding virtual axis (defined as axis 5 & 6 in my Logical axes setup) engages and ramps up on its own depending on how much I press the rudder pedal. This is what I wanted instead of the binary on/off activation of the T-Link software. Also, when I have the brake handle partly pressed, I can still press one of the rudder pedals to add additional brake pressure to that wheel, while still maintaining pressure on the other wheel based on the amount of pressure that I am applying to the brake handle. This was a way to set up the axes more like true toe brakes rather than differential brakes (as I understand the difference).
So far, so god in terms of functioning for the brakes. However, the problem is that any time I engage the rudder pedals to engage the brakes, I am also engaging the rudder itself on the plane. So, what I wanted to try to do was to set a button to disable to rudder axis when I only want to use the toe brakes. The solution that I tried out (using a Fix Axis button, setting it to FA1 on the rudder axis (axis 7)) did work because it disables the physical input on the axis rather than the logical output of the axis.
Can the above be accomplished? Assuming that it cannot be made to work in a different manner, is there a way to affect the output of a logical axis, such that I can press a button to modify whether the rudder axis or the brake axes drop to center/zero when the button is pressed?
Here is my current configuration. As an aside, I also set the microstick on the MCG to be on VC #2 because I didn't want to lose the use of those physical axes.
I do not have the twist adapter axis enabled, since I have rudders connected and they seem to be working even though I am not sure where on the physical axes where they show up. Is someone able to explain to me how to read the GF Base tab below to determine where that physical axis of the rudder appears (I have seen other threads that explain what the axes on the MCG correlate to)?
I am trying to modify the behavior of a logical axis based on a button press. I have figured out how to do it for a physical axis (set the button to a "Fix Axis" function), but I can't figure out how to do it for a logical axis. I will attach some screenshots below, but first some context. I am trying to use the rudder pedals as virtual toe brakes in DCS. I tried setting up the pedals on a separate BlackBox and joining the MCG and the pedals with T-Link. I wasn't happy (and maybe it's just me), but I couldn't get the hang of how the rudder and brake axis worked together with a button press, and despite many many tries, I could never maneuver smoothly down the runway.
So, I ended up plugging the rudder pedals into the same BlackBox as the MCG so that I wouldn't need to use T-Link any more and so that I could get creative in the way the toe brake axes work. I came up with a configuration that makes sense and has allowed me to maneuver much more smoothly down the runway, but I am trying to tweak it further.
Under the current configuration, pressing the brake handle engages both brake axes equally as well as the brake handle axis. When I press the rudder pedals either to the left or to the right, the corresponding virtual axis (defined as axis 5 & 6 in my Logical axes setup) engages and ramps up on its own depending on how much I press the rudder pedal. This is what I wanted instead of the binary on/off activation of the T-Link software. Also, when I have the brake handle partly pressed, I can still press one of the rudder pedals to add additional brake pressure to that wheel, while still maintaining pressure on the other wheel based on the amount of pressure that I am applying to the brake handle. This was a way to set up the axes more like true toe brakes rather than differential brakes (as I understand the difference).
So far, so god in terms of functioning for the brakes. However, the problem is that any time I engage the rudder pedals to engage the brakes, I am also engaging the rudder itself on the plane. So, what I wanted to try to do was to set a button to disable to rudder axis when I only want to use the toe brakes. The solution that I tried out (using a Fix Axis button, setting it to FA1 on the rudder axis (axis 7)) did work because it disables the physical input on the axis rather than the logical output of the axis.
Can the above be accomplished? Assuming that it cannot be made to work in a different manner, is there a way to affect the output of a logical axis, such that I can press a button to modify whether the rudder axis or the brake axes drop to center/zero when the button is pressed?
Here is my current configuration. As an aside, I also set the microstick on the MCG to be on VC #2 because I didn't want to lose the use of those physical axes.
I do not have the twist adapter axis enabled, since I have rudders connected and they seem to be working even though I am not sure where on the physical axes where they show up. Is someone able to explain to me how to read the GF Base tab below to determine where that physical axis of the rudder appears (I have seen other threads that explain what the axes on the MCG correlate to)?