New FFB Elevator Trim is Backwards

[GTFreeFlyer]

I know this was recently mentioned in another thread, but M3 asked for one issue per thread, so here it is:

As mentioned already by another user, I also confirmed in a quick test just now that the new FFB elevator trim, implemented in the latest patch, is backwards on my Moza AB9 as well.  If I pull the hat switch down and towards me, the stick moves forward and my aircraft dives....and vice versa.

I'm glad to see FFB trim implemented, so that's a step in the correct direction before early access ends, it just needs a -1 multiplier at the moment.

I'm still unable to provide a track file, even after updating and running a repair.  I'm not sure what's going on with that.

Thanks!

[Thundersmoke]

Just chiming in to confirm the same on a VPRhino FFB base.  Trimming nose-up will trim the aircraft nose up, but the stick pushes forward/away from the pilot instead of back/towards them.

[MAXsenna]

Just go into the FFB settings and invert the axis. On my trusty old MS SW FFB2 I have to swap axis on all my modules.

Cheers!

Sent from my SM-A536B using Tapatalk

[Hiob]

8 hours ago, GTFreeFlyer said:

I know this was recently mentioned in another thread, but M3 asked for one issue per thread, so here it is:

As mentioned already by another user, I also confirmed in a quick test just now that the new FFB elevator trim, implemented in the latest patch, is backwards on my Moza AB9 as well.  If I pull the hat switch down and towards me, the stick moves forward and my aircraft dives....and vice versa.

I'm glad to see FFB trim implemented, so that's a step in the correct direction before early access ends, it just needs a -1 multiplier at the moment.

I'm still unable to provide a track file, even after updating and running a repair.  I'm not sure what's going on with that.

Thanks!

Make sure, that if you have to invert axis, you do it in the MOza driver, not in the sim. That's important for all FFB-devices.

[MAXsenna]

Make sure, that if you have to invert axis, you do it in the MOza driver, not in the sim. That's important for all FFB-devices.

Not true. We don't have that option on the MS FFB2.

Sent from my SM-A536B using Tapatalk

[GTFreeFlyer]

2 hours ago, Hiob said:

Make sure, that if you have to invert axis, you do it in the MOza driver, not in the sim. That's important for all FFB-devices.

Not sure that will work. My elevator axis is correct. My elevator trim is assigned to key bindings and is on a hat switch.  I think the trim is working correctly if I force the stick to stay in the center position. But if you let go of the stick so that it finds its new position, it moves in the opposite direction intended by the trim.

[MAXsenna]

Not sure that will work. My elevator axis is correct. My elevator trim is assigned to key bindings and is on a hat switch.  I think the trim is working correctly if I force the stick to stay in the center position. But if you let go of the stick so that it finds its new position, it moves in the opposite direction intended by the trim.

When you press the trim button. Does the stick move in the correct direction? If not, you do as Hiob says and fix it in the software. Else you do as I say and invert the FFB axis in DCS. Hiob is probably correct as you probably use telemetry DCS does not know about. I forgot about that.

Cheers!

Sent from my SM-A536B using Tapatalk

[Hiob]

That‘s the problem. Moza (and Rhino, from which Moza copied the basis for their software) use Non-Directx telemetry. When you swap axis‘ around outside the FFB software, the input and effects direction can become misaligned.

[MAXsenna]

1 minute ago, Hiob said:

That‘s the problem. Moza (and Rhino, from which Moza copied the basis for their software) use Non-Directx telemetry. When you swap axis‘ around outside the FFB software, the input and effects direction can become misaligned.

Yeah, I forgot about that in my first post. But then I understood what you meant.

[GTFreeFlyer]

Haven't had a chance to test things since my original post.  Although the behavior is different than the other modules, the solution here is to not only invert the pitch axis in Moza, but also in DCS.  The trim now moves the stick in the correct direction.  Marking as solved.  Thanks all.

[Hiob]

Just as a data point, I tried a instant action mission yesterday (cold start caucasus), and wouldn’t you know it, I almost crashed because the frickin trim was inverted. I didn’t change a thing from earlier. Neither in DCS nor in VP config or TelemFFB.

Tried another mission I made myself and everything went back to normal…… 

Can‘t wrap my head around it so far…..

[Raven (Elysian Angel)]

10 hours ago, GTFreeFlyer said:

the solution here is to not only invert the pitch axis in Moza, but also in DCS

If you invert the inversion, everything is back to normal again... That sounds more like a work-around than a fix. If you invert axes in your FFB software when there is no issue with other modules, it will mess those up as well. This sounds like Magnitude needs to fix that. 

[Hiob]

Whatever else is going on, that I‘m actually sure of.

If you want the proper and consistent recognition of axis across multiple modules (and games for that matter).

You need to properly set up your FFB device on the device level (+the associated config software).

If you have to invert the most basic axis (pitch/roll) in the sim, you‘re already off on the wrong foot.

Since this only happened so far in the corsair (and intermittently), I assume it’s a bug.

[GTFreeFlyer]

6 hours ago, Raven (Elysian Angel) said:

If you invert the inversion, everything is back to normal again... That sounds more like a work-around than a fix. If you invert axes in your FFB software when there is no issue with other modules, it will mess those up as well. This sounds like Magnitude needs to fix that. 

That's what I thought too, but the trim is isolated from the elevator axis.  So, with the trim being backwards, I had to invert the elevator axis in Moza, and that made the trim and elevator work in the same direction.  However, as expected, things were now backwards in DCS, and pulling the elevator sitck back would result in a nose dive, so that's why I had to invert yet again, but this time in the DCS control settings for the F4U. 

 

So yeah, inverting the inversion kept the elevator behavior the same, but it didn't affect the trim, which now follows the same direction as the elevator.  None of this will affect my other modules because I use separate Moza profiles for each aircraft.

 

Cheers,

-GT-