FlyPT Mover 3.7.0.9

I will test tomorrow. Sorry

Oh my god, don’t be sorry!!! your work is remarkable, we are just here to help you refine, so many variables, so many possibilities!!!!

Thank you. Finally, something got off the ground. But unfortunately motion still doesn’t work. But during the test some movements began. but absolutely unrelated to the road. I can’t figure out how to configure everything correctly so that everything works. Can you help me? From start to finish, you can tell me what needs to be written and where. at least one example with a slope. I'll figure it out further by analogy. Possibly communication via discord or anydesk

I will help with the setup. But I'm travelling until Monday.
I will try to post a visual guide. I'm also trying to release a new version on that day that solves some of the current bugs and might help with some default setups for rigs and actuators.

Hi Pedro. I still get no connection between the 'Just Pose 6 DoF' rig and UDP or VR Comp OUT modules. However, 3D Viewer works well.

Yes, this is just a vidual bug.

Thanks Pedro. I had forgotten to ask you to switch into «dummy asks» mode. But the «tiny little bit less dummy» has now found out, that he needs to replace the <sway> etc. inserts with <R0.SWAY.B> etc. and everything is fine now and working as expected! Thanks again!

It would be nice to have a similar generic guide for aircraft. I had my 2DOF dialled in but once I get my new 6DOF working I will need to configure it from scratch. What I used for 2DOF was mixing a little bit of pitch/roll position into pitch/roll accelerations that wash out to 0. So I had a little roll remaining during the turn for example, in addition to feeling the start and end of the turn with roll accelerations. I'd like to keep that approach for pitch/roll (yaw?), but there are now more axes to think about. Also feeling the lift-off and the touchdown with heave is extremely important.

I wonder if there is something like a 'Best Practise' guide how to migrate from 3.5/6 to 3.7? Or is there no need for it?
I migrated my FS2024 profile by creating all 10+ Poses and porting/copying over the filter lines. On a few occasions the line was rejected. I don't remember when and which slight correction I had to make to get it accepted.
However I feel (didn't yet check the numbers) like one or two poses have a somewhat different effect. E.g. this: EMALP(LOGISTIC(ADD(CROP(VALUE;-30;-8);CROP(VALUE;8;30));30;0.5);50.000)
On a second look, I see that you added 5(!) new CROP filters to the already existing 3, so the above 3-year-old filter thread may be obsolete anyway?

I'm working in a file import from 3.5.3.
It's not done yet, but will come later.
The main difference in the setups is the outputs and that is because of the variables. If you keep the values everything is the same. The outputs should work better now. Calculation is way faster than it was and should give you a better result, specially for larger setups and output strings.

New filters will be added to the manual next month. Some need small corrections, others will be removed

In any case, the work done is already enormous, happy holidays to everyone here !!!

I really like the concept of using a weighted Sum of Highpass (for Turn Entry/Exit) and Lowpass Filtered Bank Angle as roll in a flight simulator.
(Maybe in the anounced „Black Box Module“ we will get a simple slider to chose a mix that feels natural…?)
In the meantime one could use a formula like:
PlatformRoll = A x Emahp(bankangle) + (1-A) x Emalp(bankangle)
Where A is constant between zero and one ( i.E 0.75)
(Simplified formula to show the principle).

Same concept applies to other axis (i.e. pitch)…