Microsoft Flight Simulator 2020 Plugin 1.1.3.0

Hi, I have the issue, that my 3DOF is rapidly changing position, when entering the FS2020 main menu (straight to lean back position). Same when changing from the main menu to the load page (into straight position aagin) and then when pressing the ready to fly button (lead or straight depending on aircraft).

Is there any chance to reduce the position transiting speed?
I already reduce the Startup/resume and Shutdown Speed to 2% in the Simtools tools menu without any changes happening.

Thanks!

For some reason, the game outputs unpredictable motion data when switching between menus. I would recommend using the on/off button in GameManager to disable motion until you are ready to fly.

Mine has never done this.., although I have not been on the sim for a few weeks.

Does anyone have any further information on whether the MSFS outputs are being added to? Specifically, would love to see accelerations that include the g component (or even better, calculated from the pilot's position).
Saw an old post about it on the MSFS forum from September but haven't kept up to date.

@Dirty was kind enough to do some digging and apparently SEMIBODY LOADFACTOR Y would provide correct heave behavior (i.e. +1g at straight and level, -1g inverted straight and level.

@Icy7CE, any chance of a build of the plugin with that change for the heave axis, please?

Hey ,

Yes, "SEMIBODY LOADFACTOR Y" is the FS2020 sim variable for (proper) vertical acceleration and it delivers the correct data. I would love to know who in the world came up with this variable name. Must've been some real pros at work there.

The -X and -Z components are at least listed in the SimConnect interface, however they do not export any data, only zero-values. I hope that at some point Asobo fill them with actual data. I posted this on the FS2020 support forums, but as you can imagine, we (motion sim builders) are a small crowd. If you want to support this with an upvote, here's the link.

As a potential workaround, I think the complete set of proper accelerations can perhaps be derived from geographical coordinates together with barometric data. If they use doubles for those variables, the precision could be sufficient and the data IS available . If there's someone out there willing to put some work and effort into this, I'd be willing to help along with the math. It's not trivial, but certainly feasible.

I haven't had time to take a closer look into this plugin. Would you tell me which values in FS2020 you use?

Cheers,.. Dirty

Right now the plugin uses ACCELERATION BODY Z, ACCELERATION BODY X, and ACCELERATION BODY Y for surge, sway, and heave respectively. According to the documentation that I was looking at, these are the accelerations relative to the aircraft axes. Interestingly, that documentation doesn't even include SEMIBODY LOADFACTOR Y.

I could change the heave axis, but it might not feel right if surge and sway aren't changed. What do you think?

Hey ,

The documentation you are referring to is from P3D . But that makes almost no difference, given that FS2020 and P3D still share a large part of their code.

I have done some searching: It looks like back in the days before FSX they had "SEMIBODY LOADFACTOR X/Y/Z" as a variable but when the code went to Lockheed Martin they eventually removed it from P3D. Here's a statement from a Lockheed Martin employee saying that it is obsolete and should be removed from the P3D SDK.


I have to admit, when I looked into the FS2020 SDK, the description of "ACCELERATION BODY X/Y/Z" virtually screamed at me: "Use me for motion cueing". I mean, in aviation there are certain naming conventions and I would immediately have assumed that those are the proper accelerations in the vehicle reference frame.

But @hexpod told me of some strange behaviours. And indeed, the numbers we saw were not making any sense. I don't know how they calculate the data in those variables, but it's definitely not (virtual) accelerometer data, that's for sure! I checked again just last night and it seems nothing has changed.

BTW, it might still be the case that people have fun driving their rigs with that data. It's just not the data that one would want to use if the correct data were available.

I think I see no reason why it should be a problem. Give it a try.

I can definitely confirm that SEMIBODY LOADFACTOR Y is the vertical acceleration in the vehicle reference frame and it is the data that I would use directly for example for G-seats. If using it for the heave axis I would apply a 1st order HP filter, followed by a 2nd order LP filter.

Instead of SEMIBODY LOADFACTOR Y, you might want to try "SEMIBODY LOADFACTOR Y DOT" (which is "vertical jerk") for heave after applying only a 2nd order LP filter to it (no HP necessary). That should work a lot better for the heave axis. However, problem with this data is that it can only be used for heave and not for a G-seat!

If you have to choose one, then SEMIBODY LOADFACTOR Y would be my choice

Cheers...

https://twitter.com/ignacymieczni/status/1352615023512875010?s=21

You can cite, retweet, like, etc etc. Don’t let it die if you have a hope to get a correct motion in 2020

I don't have much time for testing at the moment, but I've attached a build of SimConnect_UDP.exe that uses SEMIBODY LOADFACTOR Y for the heave axis. You can replace the file in AppData\Local\SimTools\MFS2020 to try it out. If people think it's an improvement, I'll post an update to the actual plugin.

Thanks @Icy7CE

I tested the new Simconnect_UDP.exe yesterday and it works much much better for me. The heave output now does precisely what I'd expect.

Oddly, the output is divided by 10 (e.g. at 1g, the output value is 0.1), but one simply adjusts the min/max range accordingly. Really appreciate you providing this!

Do you mind sharing your profile setting you have..Thanks

Hey @jaynnc ,
Happy to share my settings. Which particular settings were you looking for?

I tested it as well. Thanks for making this, btw.

I also noticed that the values were reduced to roughly 1/10th. I guess you are dividing 9.81. But the value behaved proportional to my expectations So far, so good!

However, here's the bad news:
Back then, I tested this in all parts of the flight envelope. Unfortunately I didn't test it on ground.

Well, now I did and, as crazy as it may sound, on ground it does not behave as expected

Standing still it gives you a zero value, then accelerating during take-off the value gradually increases and after lift-off it actually represents the proper vertical acceleration. It's like it is being calculated by...

Sum of all aerodynamic forces / aircraft gross weight

Also, I suspect it will not give you a "landing bump". @DZSchneider , you may want to test it yourself though. Try to see what it does during take-off and landing.

Sorry, this is not the solution I was hoping it would be.

I have opened two support tickets with MS/Asobo:

1. Bug Report: "ACCELERATION BODY XYZ giving implausible data"
2. Feature request: "Please provide proper accelerations for export through SimConnect"

I do not expect anything to come out of this, because I suspect that they have other stuff on their agenda than providing data for export. :-/

I still think that the correct data can be calculated, and if anyone wants to give it a shot, send me a PM. I'd be happy to help.

Thanks for making that experimental build.

Cheers,.... Dirty

Your profile setting and axis assignments values

That's too bad. At some point I may look into calculating the proper accelerations myself, which I've done for other games. I'm pretty busy at the moment though, so it would be a little while.

Ideally they would provide the correct data through SimConnect, but I agree that it's doubtful they'll get to that any time soon.

@jaynnc

I have a 3-dof motion-integrated g-seat, of Bergison's design.

For the roll axis I mostly use "Extra 1" (roll rate) at with some Sway mixed in
Pitch axis is just Surge
Heave axis is just Heave

For max/min roll rate I use +/-80 degrees/s
Heave +0.3/-0.2
Sway +2/-2
Surge +0.5/-0.4

Still refining these and as better outputs come along with hopefully refine further.

Could someone please be so kind and post an screenshot of his min/max Gamevibe values?
Tried to capture the values with VR, but capturing so how always stops before exiting the game.

Thanks a lot!

Hi all

I’m considering purchasing MSFS2020
Is this profile working ok ??

I’ll not purchase if no option of motion

+is there a shaker/vibration option for buttkickers ?