FlyPT Mover 3.7.0.9

Hi Pedro,

Is your software open source now? At least that's what I read on the ark dynamics (aka kinemaniacs) site:

https://ark-dynamics.com/community/

You have had the unit for some time now, can you tell us about how well it works? Noise? Stability? Durability?

Hoping you’ll find some time for an update

Hi all,

More and more impressed by Mover, and exploring functionalities of version 3.7.

As part of this exploration, do you know how I could import - for instance in Excel - the MoverRec files I recorded from a source ? I understand those are binary files but is there a way to decode them so that they can be imported somewhere?

Thanks
Best
Alex

Is there any way to map noise from value in 3.7 like we had in 3.5? @pmvcda you forgot to add this one ?

I would be glad to hear a bit from you. best!

Oh I just realized you moved it to the filters. NICE!

A very useful NOISE filter can compensate for it. Actually, I prefer it because it is possible to apply to each axis

Well done on this awesome software! My rig seems to work a lot better than the 3.5. With that said I have only just finished building my 6dof rig and are new to this I are wondering if someone can help me out with something. I don’t know how to find out what is making my rig make a glitch or little stutter type of movement. I can take a video of it. Is there a way I can see it in the software what’s causing it. It runs really well and then gets a random glitch at anytime? cheers

I had transmissions cuts in sources solved when I started a new config from scratch.
If you imported old 3.5 configs into 3.7 it might come from this.

Thanks for the reply, is there a way I can see if it’s transmission cuts? I didn’t transfer from 3.5 I started from scratch. Cheers

It was noticeable in sources values. Normally the are updated hundreds times per sec. I could see the transmission stops. But if you started from scratch your issue might be related to something else. Good luck

It’s a nice try but I see only one parameter for noise effect. Do you know if we can make this noise slower to use for low RPM or Stall buffet effect ?

Could someone explain why I do have a red color using everything else than = in the if condition ? Bug or Feature ?

Ok, After couple of hours I understood.
It seems that the higher the value, the lower is the period of noise filter.
In order to smooth the response you have to address the EMALP first:


Concerning missing RPM and Stall buffet in DCS you can add following four lignes of code in Lua for Mover.
Quick an dirty for the moment until someone will do it much better:



“+100/-1” is here for the inversion of RPM shakes : Big at idle and decreasing with higher values.

Hoping it will give motivation for eventual further improvements.

Cheers - Hexpod

If you increase the value of the noise function, do you not decrease the frequency of the direction change to lower the shaking? For example, with 250 as a value? Almost like the noise source and the amplitude depend on the simulator telemetry

What’s the difference you’re observing increasing this value ?

Increasing the value slow down the shaking

Would it be possible to expose new variables from MSFS 2024 telemetry?

I bought the A2A Piper Comanche plane, as it's supposed to have the best flight model for most realistic flight experience, but unluckily the developer has messed up the motion telemetry and especially heave is wrong. Maybe surge too.

- instead of fixing the regular vertical acceleration data, they've added some custom variables, please see screenshot; if it were possible to listen to these, the motion might work.

(whole discussion https://a2asimulations.com/forum/viewtopic.php?t=75857)

Hi all

Anyone succeeded to make BeamNG drive work with FlyPT 3.7 ? Thanks!

https://www.xsimulator.net/communit...ce-asobo-to-provide-proper-motion-data.15363/

I mean the A2A Comanche telemetry is off, not Asobo's as a whole: I attached two screenshots comparing the acceleration data on the runway, standing still, and in (almost) level flight (active pause).

While on ground, the values seem to be close (except for roll accel.)

In the air, things get messy.
- Cessna: Vertical acc. w/ gravity ~ 9,81 m/s2 + 0,985 m/s2.
- Comanche: Vertical acc. w/gravity = 0. And vertical acc = -9,732 m/s2

So I was thinking if there's a way to include A2A's own FM variables, they might be correct. Alternatively, maybe I can try to make a custom mover profile for the Comanche and just add a constant 9,81 m/s2 value to the vertical acceleration in all situations, but I don't know if that is the correct thing to do, outside level flight..