FlyPT Mover

@deadlymanager ,

Do you have some edit in the Lua file to use other programs, like simtools?
Could it be that the default UDP port is already in use?
Is it connecting and then disconnecting, or you can't even connect?
Did you follow the instructions here: https://www.flyptmover.com/sources/games#h.dfx7v0f1f1y7

You can try another UDP port. Change it on the Lua script and in the source window. They have to match.
Also try to use the latest version of Mover.
The Lua was changed in the last version to include the angle of attack.

I will make some tests.
Have a new version I hope to release in some hours. If I find something I will post.

@J-1775 ,

Ignore the AWAY filter.I'm removing it.
I was just testing some washout alternatives. It doesn't work.

For IL-2, the problem is that I verify ground contact with the suspension.
So if we have travel in the suspension, we are touching ground.
The problem is that some wheels have travel after we leave ground.
And it's not something repeatable. Same plane, same track, same conditions, it can have travel or not...
Need an idea to overcome the problem.

Wrt AWAY filter. However the idea of some washout alternative without the use of Highpass sounds teasing! A filter that always pulls towards zero, with a definable strength/speed. Like gravity...

Wrt transitions in IL-2: It's a pity IL-2 does not return something like DCS' AltitudeAboveGroundLevel, so you probably need a combination of indicators. I will think about it, too.

I encounter the same problems as deadlymanager. However, 3.4.2 still works, with its original AND latest LUA of 3.5.1.
Have tried about all you suggest. Deleted all SimTools and Simshaker files in Script and Hook, run a repair and check of DCS installation, changed port #...
What happens is this: Source starts like this:

on connect click only the balance of 'amount of air/ground' changes, 20% in every click, so first click looks like

and fourth click like

Hope this helps!

How big are the suspension values once in the air ? Are they present on all 3 wheels ? If it’s just a tiny number, maybe we can just ignore them and trigger air/ground from something slightly above the 0 ?

No idea if there could be a better solution...

@pmvcda : WRT ground/air transition in IL-2. I noticed something peculiar. No matter what airfield you take off, in a fighter 'World vertical Z position' starts always at around 1.5m (in larger aircraft like the A-20 or the Ju-52 it's somewhat higher like 2.2/2.3). But with a value of > 2.7m you'd be on the safe side.
Even better would be if you take the difference between the initial 'World vertical Z position' value and current value. It fluctuates a bit on the runway with bumbs and aircraft attitude, but a difference of > 0.5m should be good for all situations and aircraft.
How good that works for air-to-ground transition is difficult to say. Trying will tell!

EDIT: On second thought: calculating a difference might not be so easy. When do you fix the base value, especially in a long Mover session when you maybe close and restart IL-2?

Maybe give an input field like those for CoG displacement? Default value is 1.5m to which you add another 0.5m. That'll should cover nicely 90+%. The other 10% (like huge bombers) can be adjusted individually and easily.

Also noticed it, but not 100% sure it's always the height to ground. But it seems to be.
So I'm using 3m for now, in combination with suspension data.
If we are above 2.5 m, then we go to air, even if suspension is not zero.
We go to ground if suspension as a value and we are under 2.5 m.

Seems to be a bug of IL2. Not important on the game, but for us it has side effects.

... Let's add the option to choose the altitude with a default to 2.5.

The values are high, like 0.176 for a rear wheel, when we have the front wheels at 0.01.

Still on the track (lifted rear wheel):


In the air with landing gear:


In the air with retracted landing gear:



Same mission restarted, now with value zero... :

Done:



Now we can force air above a specific altitude above ground.
Could it be they have more data available beside this?
We are still missing so much info.

The combination of suspension with an adjustable height value looks like the most perfect solution we can get out of current data. Can't wait to try it! Thanks!
IL-2 was reluctant and late with offering telemetry data. We probably must be happy with what we currently have...

Mover 3.5.2

Downloatd at: https://www.flyptmover.com/downloads

- Removed message showing when sharing setup (was for debug).
- Replaced the DCS Lua. Please update the file. There was an error in the file and a bug in Mover, now solved. DCS must connect now.
- Setups now save the data used for sharing (not the password), so when opened the info is there.
- Solved problem caused by some chars when sharing setups.
- Updated links in Thanos output.
- CSPLINE and LSPLINE with 3 decimal places in the fields.
- Review of IL2 air/ground. It's now working correctlly on my tests.
Added a force air altitude. You can specify that above a specific altitude, ground to air is forced (default is 2.5m).
This avoids a problem in the suspension data of IL2 forcing ground sometimes.
- Replaced AWAY filter by the WASH filter.
It's a wheighted washout with 3 parameters: The value to filter, the multiplier used to go back to zero and the amount of the new value we want to use.

Can confirm that DCS connects again. New IL-2 ground/air/ground transitions also seem to work nicely according to settings. Haven't tried yet the WASH filter, but I'm sure I'll have good use for it.
THANKS alot for all the improvements!

Maybe it’s worth the hassle to report this “weight on wheels” bug to the il2 dev team ?

I don’t know which forum would be the most suitable to communicate about it. Any idea?

I can post something, but they are going to ignore it.
Worth trying

Actually Jason is aware of problems with telemetry, but it's not the problem we talk about here. On 20 August he opened a thread:

Guys,
Im getting reports of motion not working with 4.603b update. True? I can’t test my unit any time soon unfortunately. Jason

EDIT: The good news however is that Jason obviously has some kind of rig himself. Or access to one.
Could be a GForceFactory Edge6D ─ the one I have...

Oh that’s good news

@hexpod and @J-1775,

I posted at the il2 forums, maybe say something also to get attention.

Look here: https://forum.il2sturmovik.com/topic/73847-behaviour-of-landing-gear-data-in-telemetry/

Excellent

Great updates thank you

However its been a bug for a while (cant remember exactly) now that if you change a check box in loop pose the whole rig will jolt but it does not show on the rigs output. The same happens if you change default home value in directs while its on. There may be other places too. This used to be fine. So the result is that i now have to turn it off, change a setting and turn it back on just in case something has an issue. Changing numbers for most things seems to be just fine.

One minor addition that would be great for merging profiles. Checkbox to clear all so you can select one or two instead of clicking everything off. Bit tedious with 20+ modules