FlyPT Mover 3.7.0.9

Hi @pmvcda,
today I wanted to adjust my heli-profiles to the MSFS24, and I am wondering, why I cant set In Gains lower that 0.000. So If I want to set this to 0.100 or 0.010 nothing seems to change. Pls. see my video for this:

https://youtube.com/shorts/qk9ReyRyvGw?si=bfEODX7GricO-O6u
(Sorry - the slider is nearly completely hidden on the right of the window, but you can see it a little that there are no changes..)

Hi,
I'm not on the pc right now.
For the next release I have some changes in the numeric controls. I think that is solved.
It will be easier (I hope) to change with touch screen.
Next release is taking more time since I have some big changes inside to allow dedicated modules (specific OEM hardware).

I finally took the time to test the Rig 2 Dof under a car simulation.

Apart from the fact that I'm still not good with filters (I really need to work on them...), everything works very well!

Attached is a photo of the assembly that works under Project Cars 2.



Nice job!

I'm in the process of replacing the transducers (I have a bassshaker), and in the old flypt mover, it was very simple, I added 3 transducers for the vibrations and it worked much better than simhaptic!

But in the new one there are no (or I haven't found) shortcuts already made for the RPM variables, gear shift etc... It was super simple.

Question, are there the same shortcuts already ready somewhere, or can you add them for the transducers?

Thanks again for all the work!

I will add them. But you can copy the values generated by those buttons. It's mostlly the same UI but with upgraded code behing. Multichannel should be working ok now.

What am I doing wrong? My platform is not going up. He doesn't react in any way. 4 actuators . Le bois. Attached my old settings

Send me the 3.7 setup you are testing. You sent me an old setup.

I apologize if I'm writing something wrong. I use a translator. and he doesn't translate everything well, as I understand it. that's why I don't understand a lot. I read the forum for 4 hours or more yesterday. I didn't find anything.

I built the installation a year ago. srt80. I used the old FlyPT. But they sent me a ready-made setup with standard settings. then I just adjusted it a little bit for myself. then the wrc ea game came out and there was no plugin. I started using simtools, but for some reason the platform does not work correctly in it. in case of sudden emergency situations, accidents or difficult road conditions, the platform turned over. There was no such thing in fly ppt. later, simhub motion appeared. It's the same in him. and I do not know how to deal with it. I really hope that everything will work out.

I will be very grateful to anyone who has an SRT 80 from Lebois Racing. 3DOF. If you send your ready-made settings. next, I'll look into it in more detail. but it's very difficult for me to figure it out from scratch.

The transducers work, however my second arduino for the wind simulation does not work, I put the com module config here (this is where it is wrong I think....).

In the input data I selected the bit data (like in the old mover where it works very well), to control the 2 fans by direct inputs which receive the RPM data from the game (I checked ).

So I don't know where I made the mistake??

Ok, first thing I see wrong:


When you specify the actuators, you set it like <R0.A1>
So this is the actuator 1 in the rig Ro. But actuators have multiple values and you have to select wich value to use. Look at them in the right pane.
.B is bit values
.P is the position in mm
.T is the turns of the motor
and so on

For the controller you are using, it expects bit values, so you need to use <R0.A1.B>
The new Mover tries to use this type of logic everywhere. In reality it works like vars and you can access them on any filter/operaion in the new Mover.

Now for the pose filters:
Mover allows you to fine tune everything to you liking. So this is kind of just pointing you the general direction.
Also, different controllers/motors have different responses and a setup can be different between different rigs.
Another also, the idea is to cheat your brain and the way someone feels cheated is different from another person. There's studies that point a general direction, but sometime the idea of the user is so strong that anything you say is useless. Resuming, we want to cheat the brain, our brain, not the brain of another person.

That said, the idea is to fit the movements of a vehicle inside the limits of the rig. Usually I look at it this way:
Constant acceleration should be represented by tilting the rig. Example if you are accelerating the car, the rig tilts up to make you feel a constant load on your back.
Variations of acceleration are shorter and to represent them we use surge. Things like gear shift cause those type of variations and usually go to surge.
How to get the constant and the variations?
We apply filters. Low pass filters remove the noise (EMALP) and give you the constant value.
EMAHP, are hight pass filters (only high frequencies pass) and you get the noise.
So for example for pitch I would use EMALP(EMALP(VALUE;100);100) to get the constant acceleration
and in surge EMALP(EMAHP(VALUE;100);100)
There's and extra EMALP to smooth the values.

So resuming:
Surge = EMALP(EMAHP(VALUE;100);100)
Mix surge in pitch = EMALP(EMALP(VALUE;100);100) -> puts constant accelerations in pitch

In pure pitch I would use the pitch position of the car to get the track slope.
If you don't have surge, then play with the values of the filters to let pass some more higher frequencies to the pitch to feel the variations

The EMAHP also gives you a way of moving the rig to zero like a wash filter. So in heave I would use something like EMALP(EMAHP(VALUE;200);50)
I'm softening the movement with the 50 values and letting pass more than just the noise with 200 in the high pass.

Big values in high pass, gives you more amplitude of movement, low values gives you only noise and smaller amplitudes of movement.
Big values in low pass smooths everything and in cosequence introduces some lag.

In yaw if you had it in the rig I usually use speed of rotation and apply the same idea of EMALP(EMAHP)

But this is just the basic and some basic values you hould explore to see what is the best for your rig and your brain.
There's some extra filters you can use like the LOGISTIC that limits the range of motion, but keeps some movement even when the value is out of the limits (never reaches the defined limits to allow this).

Example in pitch, if you want to use just 10º for the slopes of the road, you could use:
LOGISTIC(VALUE;10;1)
If you get a value of 20º in the slope, the filter returns 9.64º
For 45º the filter returns 9.998º
For 10º the filter returns 7.16º
It's kind of a compression of movement

Also some people use two EMALP to smooth entry and exit to avoid sudden return of the rig to zero after a constant acceleration (the idea is to not feel the rotations used for constant accelerations)

There's many filters, but this is probaly enough.
Values are just references. Test it yourself. Start with heave for example and lock the other movements by checking the manual in the pose module for the dof's you are not testing.

I know it seems complicated, but after understanding the logic it gives you endless possibilities.
I also recomend the use of the suspension pose added to the motion pose, but do it step by step.

Soon ther'es going to be a "Black box" module for cars with generic adjustments to hide the filters to make it easier for use, but I think understanding what is behind gives you more power.

Please experiment and share your findings.
(sorry for my English also...)

EDIT: The above is thinking for cars. Aircrafts are a bit different.

Did you set the actuators correctlly?
Please show me the window of the actuators.
Click on Direct Actuator. There's a bug on the actuators (already solved for the next release) that might be causing this....

When you open that window, the values might be wrong. Set them again and try please.

thank you very much for the detailed answer. but unfortunately, my platform still does not rise. I can't fully understand what else and where to specify that motion would at least rise

In Add CRC put None

nothing helped((((

Ok, the photo is here , i'm don't undestrand why actuator is in mm or °, me, it's just a motor go to 0 at 255 in bit value ?

Sorry for the delay.

Ok I checked the output for the SRT80 of Lebois.
You have to use this:


I'm prepairing Mover to have some pré defined stuff. I will add this also

Ok, it should work.
The mm/º is to ignore. In directs we don't use units, because they can be anything you wish...
If you have time and want, I would like you to test with MMF and see if the values in the debug change with the source. I can also test on my side, but not right away.

I want to test in MMF, nothing more for the wind simulation, the actuators move well, the com receives the data in bits, but nothing moves at the fan level....?

Must be a bug??