FlyPT Mover

One could indeed think to add the Perlin when the aircraft enters the clouds.

I’ll prospect if there is a variable to detect such a state in xplane

Hi Flypt ,

I would like to say thank you so much for your last release 2.8.0 (X86 tested) :

1- AC ,thanks for adding yaw roll speed etc ... , love this cause much more realistic

2- adding pose from DOF , just what I need to achieve fine tuning for one axis , roll position + roll speed ... love it (easier as a whole new ID with all DOFs at zero execpt this that I want )

3- the construction of your software , just so easy to setup for all configurations for games ... just simple and with a big efficiency ... i love it

Thank you so much !!!

Go back to my sim rig to live the benefits of your amazing job !

This is what I have been trying to explain all along. THERE IS NO VISUAL CONNECT for turbulence effects. You cannot SEE it, you only feel it. This is why it would be so easy to implement in any flight sim. You just start it by a simple key press.

Hello @pmvcda
Quick question about your Assetto Corsa direct link.
What's the force for the traction loss?
Thanks.
Downloading version 2.8.

Hi ,
Personally I play with yaw speed ( so happy that Flypt adds this parameter to the input effects) with a limited amount on input for yaw axis at 0,3 . And into AC in the steer parameter you can check the feature under steer effects. So in case of traction loss you got the feeling with the driving wheel plus the feeling with yaw speed !
For me it works quiet great !

What do you mean you cannot see it ?

The fuselage is not moving accordingly to the acceleration forces OR the camera (head movements) is fixed and you think it should move ?

Camera shakes are normally developed from third party addons for people without motion systems to make them feel the motion, right ?

In reality AND with motion platforms your head is shaking through the motion of the platform therefore I am not sure if adding the camera (head movements) is a good idea.

I’ll post some graphs of real life turbulences later.

Best

Hey @slipstream

Well, in real life there is a "partial" connection between what you feel and what you see. It is not always in perfect coherency, meaning for every change in motion, there is not always a perfectly matching change in the visual picture. That's one of the reasons why many people feel sick in turbulence.


Let's split the term "turbulence" into rotations and translations:

In flight, there is (virtually) no connection between translatoric motion induced by turbulence and the visual picture. Simply because everything that defines the frame of reference against which you would detect any tanslatoric motion is either too far away or it passes by your window way too fast to be of any use. Even when only 500' above the ground (~50 seconds before touchdown) you probably wouldn't be able to see if the air mass shifted you left/rigth by a few meters. You would certainly be able to feel that! It gets even harder to detect the shift visually if it was longitudinally (fwd/aft).
However, if there are other objects within, say, 50m (150') of you and those object have very little relative motion (formation flight, Helicopter hovering,.. etc), then the translations induced by turbulence would gradually become "visible".

Rotations are a different game! They are independent of distance. A degree is always a degree, regardless of wether you measure it against a point on the wall of your room, or Alpha-Centauri. If turbulence induces rotations, those would very easily be detectable visually. Therefore it would probably feel "wrong" if you felt rotations coming from the rig, but not see any in the visual.

TLDR:

• I would use "synthetically generated turbulence" more for translations and less for rotations.
  
• I would expect small amplitudes and higher frequencies to cause less problems with visual mismatches
  
• If the sim generates turbulence through the physics engine, then I think there is no limit.

...that's my philosophy in a nutshell. I don't have anything better than that.

This is how moderate turbulence can look like. I just recorded it in this beast:

Did you played it in Mover?

My experience contains only accelerometer with g and gyro.

Not sure it will work.

I am away until January, if someone wants to test it ... feel free.

Fired up my 6DoF (Rotational via Bodine 12v) after a long absence from the hobby and installed the latest version. Well done @pmvcda it seems to work great with NoLimits 2. Just had to drop out-gain to .05 - .1 otherwise you get whiplash

This software is fantastic. I will be donating for sure.

I'm having trouble getting the dirt rally 2 source to work. Best I've come across is a quick blip of numbers at the values page then NaN for most values. Reminds me of the issues we saw with dirt rally 2 in simtools 2.

I've changed my hardware_settings_config.xml file to
<motion_platform>
<dbox enabled="false" />
<udp enabled="true" extradata="0" ip="127.0.0.1" port="20777" delay="1" />
<custom_udp enabled="false" filename="SimToolsCustomUDP.xml" ip="127.0.0.1" port="4123" delay="1" />
<fanatec enabled="true" pedalVibrationScale="1.0" wheelVibrationScale="1.0" ledTrueForGearsFalseForSpeed="true" />

..no luck. Any ideas?

Hi,

This is what I'm using:

Code:

    <motion_platform>
        <dbox enabled="true" />
        <udp enabled="true" extradata="3" ip="127.0.0.1" port="20777" delay="1" />
        <custom_udp enabled="false" filename="packet_data.xml" ip="127.0.0.1" port="20777" delay="1" />
        <fanatec enabled="true" pedalVibrationScale="1.0" wheelVibrationScale="1.0" ledTrueForGearsFalseForSpeed="true" />
    </motion_platform>

You need to use extradata = 3
Please try. Any problem just give me some feedback.

And use the last Mover version please.

This fixed it. Thank you very much!

I wonder if the default is extradata=3 or is there an install how to I missed?

I have a suggestion for the suspension pose since it seems you are interested in the feedback of others. I am very much so grateful for this super flexible software. If this never gets added I am still very grateful.

I am going for a specific setup in dirt rally where I want to tune some large filtered swooping motions for heave surge in pitch and sway in roll. Since this will filter all the road texture I also want to mix in some well tuned high freq data from the road. I started with high freq vertical acceleration in heave but quickly found this to still jiggle while I'm flying through the air(why codemasters?). So I turned to suspension poses but I'm having trouble getting things dialed without the input and output gain that is available with the motion poses. I did confirm that they stop jiggling while I'm flying which is great. However I am having to turn the gain down for the whole rig which is not ideal for when I mix in the other data.

Thanks again for everything you've done!

I can add a general gain in suspension.
It makes it easier to tune.
But in the filter you can do it already. Just use this:

GAIN(VALUE;2.0)

To have a gain of 2

To get just the high frequencies, you should use a high pass filter, so use:

GAIN(EMAHP(VALUE;50);2)

It's an example. Just tune the values to your preference.

Oh of course. I see now how to string together multiple filters. Seems pretty obvious now, duh.

THANKS!

btw I just donated 100 bucks for this software. I hope others will see its easily worth that much.
I am often amazed how cheap people will be when it comes to the software on their expensive rigs. I hope this changes so we can support more development in this hobby!

Thank's!

Hello @pmvcda

I now have my 6 actuators running with your Mover interface. So time to thank you for your effort and your tireless support We appreciate this very much!!!!

I still have the problem that my actuators are completely retracted after calibration and start by the Odrive motor control and have their zero point here.
After switching on the mover-interface the actuators want to retract even further - of course this is not possible.
I have now helped myself so that I pull out the actuators by hand on approx. 2/3 of the way and only then switch on the Odrive motor control. After the calibration the zero position is now at 2/3 of the stroke.
If I now switch on the mover interface, the actuator retracts a bit and everything works.
Now my question: Can I enter an offset value in the mover interface so that the motor control has the zero point at the lower stop, but the mover interface has its zero point at approx. 50% of the total stroke?
And even better, that the actuators drive automatically (and slow) into this middle position?

Wickie