Search found 4 matches
- Thu Feb 25, 2021 18:05
- Forum: Technical Support
- Topic: Possibility of toggling BrakeV function?
- Replies: 2
- Views: 1396
Re: Possibility of toggling BrakeV function?
In my case I need to be able to have analog control over the braking axes, from what I can tell, this method only offers a digital input via the button, correct? Something similar was described in the NJoy32 manual and when I tested it, pressing the button just increased the brakes. My current setup...
- Thu Feb 25, 2021 1:04
- Forum: Technical Support
- Topic: Possibility of toggling BrakeV function?
- Replies: 2
- Views: 1396
Possibility of toggling BrakeV function?
Pretty much as the title says. It would be really useful if it was possible to toggle the BrakeV function for axes using a button, I have tried a bunch of stuff: AUX axes in order to override the input from BrakeV doesn't seem to work, I even tried to create a sacrificial axis that mirrors the rudde...
- Thu Feb 18, 2021 10:11
- Forum: Technical Support
- Topic: (Update 2) Firmware releases after v.1.99.6 have incorrect defaults for throttle axis on Gladiator MK.II
- Replies: 1
- Views: 1139
Re: Problem with Switch 0 and Fix Axis in Firmware 2.03.6/7 (Gladiator MK.II)
Update!: To fix issues with Switch 0 on newer firmware, you have to go into the axis settings (Profile -> Axes) and uncheck/disable "Cn" on throttle axes (Logical Axes panel) and then make sure to check/enable "ACn" (in the Physical Axes panel) on the throttle axes. (Throttle axe...
- Wed Feb 17, 2021 18:54
- Forum: Technical Support
- Topic: (Update 2) Firmware releases after v.1.99.6 have incorrect defaults for throttle axis on Gladiator MK.II
- Replies: 1
- Views: 1139
(Update 2) Firmware releases after v.1.99.6 have incorrect defaults for throttle axis on Gladiator MK.II
Edit: I found the issue and changed the title to match it, please see my updated findings and workaround in my reply below. Update!: It seems that the axis behavior was changed and the defaults not updated accordingly. I have once again updated my reply with the information for the workaround. ---Or...