FlyPT Mover

@pmvcda I discovered with horror that the planes in „flying circus“ (1stWW) in the il2 series are incompatible with those from previous series. I am trying to figure out the accel directions which seems different to those from previous releases. Those with gravity you set up back that unfortunately doesn’t work with the WW1 planes.

Coming from them, it's possible.
Give me some feedback if you can please

Ok, after a quick analysis (I always can be wrong) I think the sway (lateral accel.) is inverted once we choose WW1 birds. You can see the overcome in the screenshot (minus sign in “sway” and “mix sway in roll) which shows how great and flexible mover is. You should guess why the accels with gravity are getting stuck. I it’s possible to fix directions in flying circus without breaking them in other series you can go for it.
Cheers

Hi

can't wait the beta thanks for the work

Is it possible to communicate via bluetooth in actual version ? and in the next one ? for wind or led for example.

THanks !

The way I read the docs, when loading a plane there should be a FOCUS event over UDP with the name of the plane in it. That could theoretically be used to set a custom gain. But it would have to be coded in the source code, no way to do this as a generic UDP input.

That is done for the new release, the problem is that events are events, it's not info received with a good frequency to imediatelly update the setup...

No, but I'm looking at it for the new release. Not for day 20...

True, the best fix for this would be in the source code of IL2, not yours.

Good news, I could get the hands on the OXRMC local frame of reference fix which improves greatly the experience. Supposed to come in the future release in the near future.

Interesting - what's that supposed to do? I'm assuming it is intended for using Mover as virtual tracker?

The fix will correct a mismatch in translations according to rotations. The tracker will subtract correctly according to the local frame of reference the linear motion - also when the platform is tilted - which was not the case obviously until now.

So flyPT Move does rotation first then translation while OXRMC did translation first then rotation. This caused some discrepancy between what the rig did and what the compensation did at combined lateral and rotational movements. The new fix does the order of operation the same way Mover does it.

Reason for first rotation, next translation:

You rotate for constant acceleration
You sway/surge/heave for acceleration "noise"
So translation should be done relative to the direction of your body

Absolutely! I agree 100%. It's just OXRMC did it the other way but now fixed so should be good.

Day 20 here starts in 15 min, so I still have 24 hours...

Don't expect much, I'm cutting/hidding to many parts due to bugs.... It will have many updates to do in the next days


Major problem making it one executable right now.... but will do it

So the new release is almost here (BETA!)
We are going to move the dicussion of that to a new thread:
https://www.xsimulator.net/community/threads/flypt-mover-3-7.19016/

For now it's lacking info. Sorry.

Can it be that now Pitch speed and roll speed are inverted in „flying circus” ?

Just a quick note that it seems like the remote server for flyPT is down and because of that it's getting a segfault "unable to connect to remote server". This should probably be handled a bit more gracefully. Ver 3.5.3 here.

Mover 3.7.0.4


Download: https://www.xsimulator.net/community/threads/flypt-mover-3-7.19016/
Info: https://www.xsimulator.net/community/threads/flypt-mover-3-7.19016/page-18#post-251308