FlyPT Mover 3.7

we still have a hard kicking back in this feature.
If I recall well you corrected it in between but this commit got lost.

@pmvcda do you think it will be a good Idea to make your own discord for FlyPt?
you can organize the topics or a bug report where everything is line up?

many people dont like this xsimulator forum and it's getting hard to follow with update or bug in the same long thread
thanks

Seriously no pressure! I see movement and it excites me!

I'd venture to say GitHub is probably the right tool for this but I digress....

You can still be closed source with GitHub but publish readme and sw revisions and still utilize the bug tracking feature.

Discord is not the answer to everything for sure and nor is a linear thread on a message board.

I'm a SWE so looking at this problem with a different set of eyes probably than your average end user.

One new issue: Save a Mover profile on a device with two monitors with Mover main screen being on the secondary monitor. When you open the profile on another PC with only one monitor the mover window is off screen and no way to get to it.

Hopefully the fix will include GTSports too.

... I thought this was solved. It's one of those nightmares.
On the list of bugs...

Need to get the old ps3 test gt6. She's somewhere...

Solved

I have a channel, but not using it (hidden)
Having it without having time to follow would be worst in my opinion
Might use GitHub soon...

The singularity is there:

The one in red

The pre-follow is a parameter for the follow pretended pose alghorithm.
As you increase the value, the rig starts following the pretended position sooner.
Use it with low values, 1 will stop moving the rig, or almost nothing.

Better try than explain:
Put 0.1 on the value
Reset to 0 all pose sliders
Move just yaw
You can see the pretended position and the calculated one that goes behind the pretended
With a value not zero you start getting behind sooner. This means you get more motion for bigger out of range values...

Hope you understand what i mean.

This looks like a scaler because from the beginning the assigned pose is not 100% followed. Interesting.

concerning „stay on the last good, please look in the attached Beta. Maybe it will help you remember what you did

„We get more motion for bigger out of range“ BUT we get less motion „in rage“. Is my assumption correct?

About this, it would be nice if the motion algorithm option "Follow pretended pose even if out of range" would have the the option to choose the distance of engaging also filter, like in the Logistic 3

What happens if you do logistic directly on the actuator level in combination with „follow pretended“. It doesn’t give you results you are asking for?

If you use the Logistic filter directly on the actuator you loose the motion compensation in some extreme position, also the 3D view will be not correct but 3D view is not so important. @pmvcda developer the "motion algorithm" on purpose

And what happens if you do logistic on each dof in combination with pre-follow?

Question: since there is no more limit on the rig, how does one limit the sum of poses? I guess by using Pose Filters in the Rig?

pmvcda advice to not use the Logistic filter on the actuators unless you not use the motion compensation, otherwise the motion compensation will not be coherent with the positions

I am talking about dofs degrees of freedom. (Yaw-Pitch-Roll etc.)