FlyPT Mover 3.7.0.21

I would like to express my gratitude to the developer. Today, I tested the Bass shaker in the Mover, and it works. I adjusted it to the engine speed and the road surface.

Hello @pmvcda

I know you may have plenty on your plate...I am trying to control a very simple rig on Fly PT using only 3 actuators

You surely already know it, its a "3 RPS"

The first joint is revolute -passive
The second joint is prismatic -active
The last joint is spherical -passive



Its very similar to Rotating 3DOF (3RRS) which already exists in FlyPT.

I was wondering if you had any idea how I could set up this type of rig in your software ?

Maybe some trigonometric transformation on the Rotating 3DOF rig type could do the trick?

Any idea for even a quick & dirty solution, this would really help.

Thank you for your kind help as always,

Sincerely

I will add it for the next release. It's an easy one i think.

Meanwhile you could try to add with 3 actuators but i think it's not going to work because you cant limit the motion of the bottom joint.
But without yaw sway and surge it might work.

Now you can use two poses on the actuator, one for the rod and one for the housing, use pose just in the rod

Awesome!!! I will try this hack in the meantime

Looking forward to your release so I can configure it properly (enter base radius, platform radius, actuators stroke and other parameters)

Thank you man, you are a legend !

Thanks for your replies. I am still banging my head against the wall and can't get LFS to link up with Mover.
I have opened all UDP ports in the firewall and even tried temporarily disabling it; still no luck.
Thanks for the tip about the patching of LFS I had not done this. I try and it still doesn't work.
How does Mover know where to patch files? I ask as I had installed LFS more than once and just wondered if a path is wrong somewhere. I also notice that even without LFS installed the patching seems to be allowed even though no LFS files are there, what does patching do and how do I know it has worked?
Can I ask what version of LFS you are using? I am on 0.7G and mover 3.7.0.21.
Any help is very welcome. I have my actuator moving with Mover and the noise/loop source so know it works.
Thanks in advance.

Also in addition to the message above. I notice in your screenshots when using LFS the Connect/Disconnect button is red. My one is always yellow. What does this mean?

Why Flypt mover project doesn't have a Discord?

I have it prepared, but never started because i had no time for it.
What sections would you like to have in that discord?

When we receive data, a transition is performed and the button becomes red (yellow to orange to red)
If you are not receiving data but are listening on the port, it's yellow

There where some problems when detecting the install folder. I added some log to the next release to track the errors.
Mover looks at the UninstallDisplayName to get the install folder. If you have more than one instalation it uses the first found.
In Live for Speed the UninstallDisplayName is "LFS"
You can check your location by using the Windows PowerShell
Type: Get-StartApps | where name -like 'LFS'



Usually in LFS, we need to edit the cfg.txt file that lies in the instalation folder.
NOTE: Run LFS at least one time before patching (LFS creates the cfg.txt file when you run it for the first time)
Open it in the notepad and search for OutSim or OutGauge:


In that section you need to edit the data to match the above text in blue:

Code:

OutSim Mode 2
OutSim Delay 1
OutSim IP 127.0.0.1
OutSim Port 4123
OutSim ID 0
OutSim Opts 1ff
OutGauge Mode 2
OutGauge Delay 1
OutGauge IP 127.0.0.1
OutGauge Port 4124
OutGauge ID 0

Now start LFS and it should work unless you have something blocking the port or another software getting the data from that port.

What I wrote above is what Mover does when patching.

1. news (where can wright only you), info about new beta version, any fix, updates.
2. separate secrions for 2dof, 3dof and other platform. Users can talk about platforms, designe, how to make it and etc.
3. Issue, if some one have a problem with Flypt.

for start I think that's enough. If need later can make new section.

Hi Pmvcda,
Thank you so much for your time on this.
You have fixed it for me - the issue was the OutSim Opts not being set to 1ff, it was set to 0. All the other settings I had correct and could see data in wireshark on the correct ports.
After setting the OutSim Opts to 1ff everything is working as expected.
Cheers!! Happy simming!