Joystick Pitch Control Axis

Blue Robotics Software Cockpit
1

I have seen similar themed posts, however they do not completely fit the bill.

I use Mode2 layout on the Xbox controller, and would like to modify the controls slightly.

I wish to:

Change Ascend/descend from left stick, to LT/RT axis

Change left stick forward/back (currently ascend/descend) to pitch up/down.

The above will allow me to have pitch and yaw on left stick, and ascend/descend not have the potential of accidental yaw.

This is with Cockpit, so the LT/RT will work (unlike QGC).

I am aware of the Trim Pitch control parameter, is there a different control parameter that could be used on the stick axis?

2

Hi @3dMB,

There’s actually a small factor that’s blocking this from working at the moment - I recently implemented a fix for it, but it needs to be reviewed before it can be included in a release. I’ve just marked that for fast-tracking, since there have been multiple requests for this kind of thing lately.

You’re welcome to test the pull request by downloading a relevant artifact (requires being logged in to GitHub), but otherwise I’m hopeful it will be available in a beta release some time this week or next :slight_smile:

Axis T controls pitch. I’m also working on making that clearer, but it requires some infrastructure improvements that need to be well considered so we can maintain them effectively - apologies for the ambiguity/confusion in the meantime.

3

Thanks @EliotBR

4

Was there any progress on this in a beta release, please @EliotBR ?

5

Per the pull request thread:

It will be one of the first changes included in a 1.19 beta, which should be released just after the 1.18.0 stable (expected in the coming weeks). Sorry for the delay on my initial expectation!

If you’d like to test it sooner you’re welcome to do so via the Artifacts :slight_smile:

6

Hi @EliotBR - now 1.18.x is released, is the beta for this still on the cards?

7

Still on the cards, but I’m on break at the moment.

IIRC the feature is partially held up from a desire to avoid requiring a migration later for some more advanced functionality that I was hoping to roll in with it (frontend all-vehicle gain and reversing), but if those seem low priority to you we can potentially merge and release just the base axis transfer and then do the extra migration work after I get back. Do you have a preference?

8

Enjoy your holiday @EliotBR - lets pick this up when you are back :+1: