1. For downloading SimTools plugins you need a Download Package. Get it with virtual coins that you receive for forum activity or Buy Download Package - We have a zero Spam tolerance so read our forum rules first.

    Buy Now a Download Plan!
  2. Do not try to cheat our system and do not post an unnecessary amount of useless posts only to earn credits here. We have a zero spam tolerance policy and this will cause a ban of your user account. Otherwise we wish you a pleasant stay here! Read the forum rules
  3. We have a few rules which you need to read and accept before posting anything here! Following these rules will keep the forum clean and your stay pleasant. Do not follow these rules can lead to permanent exclusion from this website: Read the forum rules.
    Are you a company? Read our company rules

Let's convince Asobo to provide proper motion data

Discussion in 'Flight Simulator 2020 - FS2020' started by Dirty, Oct 14, 2020.

  1. Dirty

    Dirty Well-Known Member Gold Contributor

    Joined:
    Oct 15, 2017
    Messages:
    524
    Occupation:
    All the way up front.
    Location:
    Germany
    Balance:
    5,697Coins
    Ratings:
    +616 / 1 / -0
    Hey there:)

    I'm trying to convince Asobo to provide proper motion data for export through their SimConnect interface and I was hoping to get some of you guys who are intersted in FS2020 to support (aka "upvote") my issue report that I have provided here:
    https://forums.flightsimulator.com/t/simconnect-semibody-loadfactor-x-and-z-not-supported/273198

    In short: Acceleration onset cueing needs the proper accelerations and vehicle referenced angular rates to be exported. The angular rates are all available :thumbs, however the proper accelerations are not. At least not on all axises.

    The proper vertical acceleration is available as "SEMIBODY LOADFACTOR Y", but the X and Z axises are not (yet) supported. Even data that would allow me to derive the necessary data (world positions) is not available.

    Would be great if people supported this :)

    Cheers, Dirty :)
    • Like Like x 5
    • Agree Agree x 2
  2. Ads Master

    Ads Master

    Balance:
    Coins
    Ratings:
    +0 / 0 / -0
  3. MarkusB

    MarkusB Active Member Gold Contributor

    Joined:
    Jun 30, 2015
    Messages:
    495
    Location:
    Germany
    Balance:
    3,698Coins
    Ratings:
    +503 / 1 / -0
    My Motion Simulator:
    2DOF, 3DOF, DC motor, Arduino, Motion platform
    • Like Like x 3
  4. noorbeast

    noorbeast VR Tassie Devil Staff Member Moderator Race Director

    Joined:
    Jul 13, 2014
    Messages:
    16,041
    Occupation:
    Innovative tech specialist for NGOs
    Location:
    St Helens, Tasmania, Australia
    Balance:
    117,037Coins
    Ratings:
    +9,360 / 46 / -2
    My Motion Simulator:
    3DOF, DC motor, JRK
    • Like Like x 2
  5. Dirty

    Dirty Well-Known Member Gold Contributor

    Joined:
    Oct 15, 2017
    Messages:
    524
    Occupation:
    All the way up front.
    Location:
    Germany
    Balance:
    5,697Coins
    Ratings:
    +616 / 1 / -0
    The problem is that Semibody_Acceleration_X and _Z are not available for export. At least they weren't last time I checked, a few weeks ago.
    Yes, you can export some data out of MSFS2020 and get some motion out of it. And if some motion is what you want, then MSFS certainly delivers some. But unless proper acceleration data is available, this motion will not reflect the accelerations a person on the vehicle would experience.

    However, the angular rates are available, so at least rotations should work fine with the data available.

    I have a vague idea how it might be possible to derive the proper accelerations from geographical coordinates, but that is a pretty far shot.
    • Agree Agree x 2