vJoy mapping issue

Villajota

Hi, just made my first (very short) flight, really impressive. Thanks for this bird.

I've got the elevator trim of my Bravo mapped to a vJoy driver through Authentikit to improve sensivity and response. It seems that in this plane it works the other way round: moving the wheel towards me makes the trim go nose down and vice versa. In Bravo terms, button 23 to + and button 22 for -.

I've solved this creating another Authentikit profile for the Starship with the Bravo buttons mapped the other way: 22 for + and 23 for -

That's no big issue for me, I just wanted to share just in case someone else finds the issue.

Great aircraft, @Black-Square, as always. I'll spend hours inside it.

mysticfm

I have a Bravo too, but I use FSUIPC, not Authentikit. I wonder if I would have to expect the same problem? (I can’t check, because I’ve elected to hold off on a purchase until this kind of thing gets fully sorted out.)

Black Square

There should be absolutely no difference between binding the flight controls of Starship versus any other MSFS aircraft. Can you explain how this binding works for you? Are you setting the trim through its variable directly, using the native events, or something else?

Villajota

I found the instructions in this video: https://www.youtube.com/watch?v=Sx6KJ0dEtus

First I installed the vJoy driver. vJoy appears in MSFS like another piece of hardware.

Then I installed Authentikit and configured it like this:
Mapping Type: Remap Button to Virtual Axis
Input Button +: Bravo Throttle Quadrant Button 23
Input Button -: Bravo Throttle Quadrant Button 22
Virtual Output Axis: vJoy1: X Axis (L-Axis X in MSFS)
Sensivity:360

Then I mapped the elevator trim in vJoy to that L-Axis X in MSFS. It works exactly in the same way in all aircrafts but I was a bit surprised when I found that in the Starship it was moving the other way.

Authentikit lets you save and load different profiles so I copied this one and created another with controls inverted. This new profile is linked to vJoy2: Y Axis (L-Axis Y in MSFS). Then I create a configuration for vJoy /Starship in MSFS 2024 using that axis. That works for me.

By the way, binding directly the Bravo wheel to the elevator trim works fine, but we usually don't do this because a lack of sensivity and responsiveness - nothing to do with the Starship. That's why because we use something to improve it.

Black Square

Very interesting. Thanks for sharing. I can only assume this is because someone at Asobo forgot to invert that input based on a flag I had to set in the aircraft configuration to get the correct virtual elevator deflection for a canard aircraft.

If you wanted to test whether this is correct, you could try setting pitch_moment_delta_elevator in flight_model.cfg to a positive number. I suspect this will make your elevator trim run in the correct direction, but don't attempt to fly the aircraft like that. If I'm correct, we can submit a bug report with Asobo for you.

Villajota

You are right. Changing that value to 4.5 instead of -4.5 makes the normal Authentikit profile work as in the rest of the aircrafts. For the moment I'll keep both profiles, I can change it when I fly the Starship. Eventually Asobo will solve the problem once you notify it...

Thanks for your fast response!

Best regards

Black Square

Wonderful! Thank you so much for confirming that! It's always good to be able to speak definitively about bugs, rather than going off hunches. Sorry this one affects you. I never ever heard about this with my Velocity XL. Hopefully we can get it fixed for you soon.

Black Square

I have told Just Flight's lead developer, and hopefully he will make the bug report with Asobo soon. Thanks again!