FlyPT Mover

Hi,

Been looking for the bug, but that's not an easy one
Meanwhile, I downloaded your file again and saw the filter in the rig module (for the actuators).
Could you test without the filter? And see if the behaviour is still there.

Thanks.

Should be working, at least it works for me.
But there's some values swapped there and a bug still not solved.
You have to start FS2020 before connecting in Mover. This specially if you have auto connect enabled.

From what I see here could be quite normal behavior. The platform is running full speed from blocked “out of pose” state to the next valid one.

One suggestion to @pmvcda , could we imagine a smooth transition filter form “out of pose” to the next valid one ?

Is there a guide somewhere about how to set it up?
Do I follow the same SMC3 setup as with the SimTools, and then just use FlyPT to drive it? Will it recognize Arduino based on SMC3, driving 2 IBT-2 boards? Any setup tips?

I think, if such a thing is achievable, it would be a great improvement.

Hi,
sorry for the late answer, sure in the next few days I will make some tests. The rig is so high-performance that without these filters it risks tipping over despite the weight of 350 kg.

Thank you
Marco

Hi, I just uploaded a new video where you can see that the physical platform gets stuck even though the actuators in the mover continue to move. this behaves happens only when the rig is in the singularity event. I removed the filters in the rig as you advised and I attach the file in order that you could take a look.

Thank you a lot

Marco

I think „out of pose“ means stopped movement for the whole platform even if only one actuator has reached its limit.

Maybe I don’t look where I should but for now it’s looking fine to me.

You just have to avoid those singularities by reducing the motion range of each dof or turn this feature off, which can expose you to eventual problems of not mathematically predictable poses.

Nope "out of range" mean that the platform can't solve the position because at least one actuator as reached his limits but the geniality of the mover is that he can give you a position despite the unsolved position. To avoid the "out of range" as you mentioned "stopped movement for the whole platform even if only one actuator has reached its limit." You have to enable the option "Stay in last possible position"

That’s not the way how I understand it. Mover can’t give you the pose with one actuator stopped.

What you see actually is a hypothetical position which can’t be released by your physical platform

That's partly true, what you see in the 3D viewer is not the same the rig are doing when in singularity or "out if range" positions. When in 3D viewer you see the red actuator that's doesn't mean that get the stopped movement for the whole platform, unless you check the "Stay in last possible position" option and that's the magic.

Did you made your video with „Stay in the last possible position“ checked or unchecked?

If it’s checked, I can insure you, that there is no magic to calculate a mathematically accurate pose with one or more actuator „out of range“, so the platform stops completely.

On the other hand, when this feature is unchecked, what you see in the 3d Model when one actuator has reached his limit, can NOT correspond to the physical platform position by definition of IK.

It needs all 6 actuators being „in range“ in order to send the platform to the right pose.

It‘s how I see things unless I didn’t get the basic concept.

Of course unchecked, as magic I meant that other software stop the platform if in singularity. Is obvious that is mathematics.

I understand. Did you tried to match the „pose limits“ from rig module with range of pose module ?

Actually I didn't, that's could be a good advice, I will try be next days than I'll let you know.

Thanks

Request: Could you please add support for the Need for Speed Games? Would be great!

Had to include a Spectogram module in the new Mover to make better tests on the filters:

They don't have telemetry, and I don't have time to look for hooks (I'm not good at it).
If anyone want's to do it, I can add sources for it. Or they can use the hook source to put the memory values there.

Wow, this will be the swiss army knife of motion simulation. This will allow to do absolutely everything, like a programming language. I hope it won't become too computationally demanding for my CPU.

Amazing work! We are going to be so spoiled.

Might be nice to run this from a different pc that is dedicated to motion control.