FlyPT Mover

I will try to create something.
Have some ideas.

You're terrific - as always! THANKS!

its great idea.. just wish i had time to do something like that!
at the moment im trying to build a 3d printed make of an apache helicopter collective.
appreciating your replies and shares!

thank you for share. trying to find some time to check out your profile.
whats your steamname?

The crazy but altogether fascinating thing about our 'science' here is: it's full of surprises. Like this afternoon when I reversed the roll motion and found that it tricked me even better than the 'correct' way around. Is it 'muscle memory' or are the G forces better replicated this way? Or maybe both? I also added an additional Sway input. In a sequence of small left and right stick movements and with some rudder I feel now like 'swimming' thru the air... I attach the new P-51 profile.
I try to keep Steam alerts and overlays as low as possible, but on Discord (e.g. the OVR Motion Compensation thread) I go by «DeHavilland».

EDIT: Noticed that SimConnect and DCS provide reverse roll data. That's why this afternoon I involuntarily 'tested' inverse roll application. I tried my DCS P-51 profile with the ICON A5 (the only aircraft I fly in FS2020 until we have a VR Prop fix). It worked astonishingly well. I left 'ground rumble' unticked ─ it feels overdone. You may try Roll (in AIR!) with or without the negative multiplier. However, if you ─ like me ─ run FS2020 on the WMR OXR runtime and without motion compensation, it's better WITH the negative sign.

EDIT2: Found why my ROLLOVER didn't work as expected and corrected it: the profile is now 'approved for aerobatics'. However on my system it feels better on roll than in a looping. And don't try it on the Extra, it's obviously too sensitive for such a nimble aircraft. But Carenado's WYMF5 is fine. All things said apply to my 6 DoF system (GForceFactory EDGE). Attached latest versions (Beta3).

Depending on the version of mover you use you can have directions and swapping bugs if the build is made before 18 June. In the profile I sent above it got corrected in the test version.

Thanks very much for the tipp noorbeast, I will give it a shot when I come back to more FS2020 flying.
BTW, I noticed something quite intruiging. I couldn't believe how any VR aviator can live with such a nauseating issue. So I swapped OXR runtime from WMR to Steam. And what did I notice (ZLIN Shock Ultra)? The effect is far less disturbing on Steam! Though I need the same amount of reprojection (every other frame) like I do on WMR runtime. And frame smoothing is on, I double-checked. Such a shame for MS & Asobo!

@pmvcda : Do we have a 'gate' filter (apart from its CROP subset)? Why do I ask? I currently use ROLLOVER which works as intended. The problem is: My profile is focused on +/- 30° bank angle. That's where 97% of my flying happens. Fast but smooth responses in level flight. Now I don't want my level flight profile reflected 1:1 when in a roll crossing the median upside down. It would kick in relatively late, move fast to the other side, and then rest for a while before 'washing out' to zero/level flight.
Of course, I could somehow adapt my profile, but my idea was to limit (crop) the current profile to -90/+90 and setup a separate profile for the remaining half of the circle (the 'gate' between 90° to 270°) with a long smooth transition from end to end. I had the idea it might work by switching (in the CROP filter) the -90 and +90 values. But, of course, it did not.
Hence the idea of a freely customizable 'gate filter'. Taking the example of RPM: I want only RPM between 800 and 1500 passing thru the gate. Or ALL RPM EXCEPT those between 3000 and 5000.
Knowing you we either can do that already (and Mr Stupid missed it) or it's in the pipeline for v4.0?

In Mover 3, you can do something like:

Add(crop(value, min1, max1), crop(value, min2, max2))

This allows you to do the rpm example.
You can make a filter over it all.
Might generate a messy filter script.

Also, besides crop, you could try the logistic.
It limits the range, but represents all the values. OK, anything over the limits has less and less weight on the result, but in 30 degrees, you might still have some feedback of 50 degrees.


Meanwhile been setting a server to have the setups... Let's hope it works well.

Edit:
Main advantage in Mover 4 is the possibility to mix different values and to have logic with them.

Thanks alot for the insights! I couldn't imagine that cropping a cropped value would get such a result and therefore never tried it. I actually use Logistic and like it a lot. I have lowered the input gain from .6 to .3 and increased the steepness ('fastness') of the logistic curve a further bit. So I still have 1:1 response around the middle but also some slower movement up to 60°.
EDIT: In fact I replaced the .3 input gain by a .3 MUL that I placed right AFTER the Rollover. That's easier to handle for my poor mind than adjusting the Rollover value.

Hi there

Hope you are doing well!

Im curious. Its been a while between versions now. Perfectly fine of course im sure you are busy! Or could this be a hint that we may go straight to Mover 4?

Cheers!

Hi,

I'm releasing a new version soon:

Some corrected bugs
Small changes in FS2020
Many changes in IL2 Sturmovik with air and ground
And a new online setup sharing feature

All this work will be in 4.0 also, and 3.x is working as a test bench for it.
4.0 will take more time. I'm still having many small bugs and specially, some doubts on the base structure, specially on the plugins side and grouping of nodes (they are related).
Only when this is 100%, I can think on a release and beta testing.

Also, I want 4.0 to have all the features we have in 3.x.
Problem is that while the above is not 100%, I can't go ahead implementing all the sources we have currentlly.

So,
I'm mostly working in 4.0, reason for the lack of updates in 3.x.
Unfortunatelly, I don't have all the free time I wanted, so it's taking more time than what I expected.

Just finished today setting up the database and the server for the setup sharing. It will be the same for 4.0.
Working now on the UI of Mover 3.x to release it.

This is so exciting news, ony a few hours ago I said to myself: it's a pity IL-2 does not have separate filtering for ground and now I read it'll arrive and all I have to do is wait for it! And the online repository! I hope it will boost the community and help new users. I remember my beginnings, after I had set up my RIG and OUT modules I wanted so much to feel it in a sim, but felt kinda 'lost' with so much filtering possible. Well, most of the time I still feel so...
Thanks so much Pedro for giving us so much of your precious time!!

Hi ,
Someone can explain why I have this message error !
This happen when I stop the game and STOP All Outputs ... sometime is ok !!!! and if I do * ok * the Sim goes VERY fast at the PARK POSITION
Error : Error while trying to update data on the memory mapped file !
THANKS!!

Please, send me your setup and the Mover version

Edit:
Seems you are using motion compensation
Mover creates a MMF file with the data sent to the motion compensation software.
Seems that file might be already in use, or by another app or a crashed Mover?...
I will look at the code.
But do you remember if you closed and reopened the motion compensation, or if you have 2 of those modules?

i am getting good results from your DCS profile. very smooth. Thank you. . appreciating it! @J-1775

@pmvcda you are the best...we are lucky to have your time

hey @pmvcda is it possible for mover to be a server to send data to run a client mover?
i ask this because running DCS world, sim shaker software, mover software and virtual reality seems to tax the DCS performance... i think i have a descent rig with 9700k and 2080Ti...

Not in 3, but for 4.0 you can do it. Not yet, but it's on the list to implement.
But you can use the transducers in Mover to remove sim shaker

I know, it's not easy/intuitive to use...


Edit,

Wait give me a minute, you might be able to do it in 3.0

@hannibal ,

You can generate all the data in Mover, then send the pose over UDP to another PC.
In the other PC you make a custom UDP source to get the data and send it directlly to the output.

But this takes time and generates lag, but if you want to try, give some feedback