FlyPT Mover 3.7.0.17

After installing version .16 and starting from scratch, the motors began working. I guess there was some kind of bug before. In version 3.5.3, there was an option for motor limits, but in the new beta version, I can’t find the motor limit settings. What’s the proper way to set up motor limits? Since I don’t have a hex rig and only have a seat mover 3DOF setup with two motors in the front and traction loss in the back, can traction loss only be added using a direct module to control it?

Yes, you have to use a direct for traction loss (use the WASHX filter there, this will be the final WASH filter, I will rename and erase the other WASH).
I can add a traction loss actuator to the that rig later.
For the actuator limits, you need to go here:

Where it says parameters for the actuators.
There you specify the specs, limits, bits mapping and filters (use CROP as a way of limiting the output)
There's some problems there with colors and I know some names are still wrong in some types of actuators.
In the direct it works the same way (there's a bug when using the slider manually - nothing happens...).

FlyPT Mover 3.7.0.17 BETA

Download here:
https://github.com/FlyPTMover/Releases/raw/refs/heads/main/Mover 3.7.0.17 BETA.zip

Release notes for 3.7.0.17 (06-10-2025)

Disabled rendering on resize of windows for a faster UI (might become an option)
Solved bug where Loop and noise was slooowwww when loading the setup
Added double click to module button - This now hides the module, just like double clicking the title
Corrected layout in options for correct scale adjustment (missing close button)
Corrected layout of main window menu for correct scale adjustment (disaligned and cropped menu buttons)
Also corrected wrong title rendering of main window when scale is changed
Corrected bug in control for plugins locations with bad behavior on scale change (options window)
Changed behavior of main window while loading a setup to avoid a "ghost" window
Corrected bug where updates where not made to the rigs when changing the actuators parameters
Corrected colors in the window to adjust actuators parameters
Removed radius from the rotating sliders actuators setting in the rotating slider hexapod (we set it outside of the window for two radius)
Updated source to get data from joysticks/keyboard/midi
Solved bug where hots where not saved/loaded

The updated joystick/keyboard/midi source:

Привет, меня очень заинтересовал ваш проект; в настоящее время я планирую создать 2dof-платформу.
Хочу спросить вас лично, что нужно прописать в последовательном порту Arduino Uno R3 с прошивкой smc3. Пока я ищу дополнительные средства для платформы, мне хотелось бы разобраться с программной частью. Заранее благодарю за замечательную программу.
Я общаюсь через переводчика, поэтому извините, если что-то непонятно.

I got something like this, but I'm not sure it's correct. It's just that your website says (example from the website): In the output string, use: "[A<Axis1a>][B<Axis2a>][C<Axis3a>]"
But the program doesn't have those axes.
Could you please tell me if I'm on the right track, as I don't really understand programming or code.

Thank you very much.

In Mover 3.5.2:
[A<Axis1a>][B<Axis2a>][C<Axis3a>]
In Mover 3.7.0.x:
[A<R0.A1.B>][B<R0.A2.B>][C<R0.A3.B>]

Version .17
Keys have been added to the "Keyboard..." module. The configuration has been saved. An error occurs when opening this configuration.

Version .17
When adding the "3D" module to the configuration, the arrow did not appear.

Version .17
We're displaying the graph. The arrow is there.

We're removing the display of any element, and the arrow is gone.

I'm using the 4Dof Linear rig, and the front actuators lean. Is there any way to keep them from doing that? IRL they are only free to lean forward/back..
Or is it just a visual thing, and the COR calculations won't be affected?

Really interesting trying a completely new concept after years of Simtools.



Also, the rear actuators IRL have no control over the roll, but the roll affects them too.
Can I do anything about what actuators do what more like I would in Simtools?

In your rig, it's not moving front/back?
Can you share some photos of the joints please.

There are a few retail rigs that have similar layout. Not sure how they solved the over/under constrain in the design, but the joints should be similar on all of them.








The front actuators are involved in pitch, heave and roll.
The rear actuators are involved in pitch, heave and yaw (TL).

The base of the front ones can only go front and back? I mean, rotate around the sway axis

You have a slider at the front to compensate the distance change between rods right?
I can add a rig like that, i thought it was like the one i added.

Exactly. The top rod ends of the actuators can slide a little.

I think all of the linear 4dof have the same behavior. The only difference is whether the have the elasticity on top like I have or in the bottom. You don’t have to add a rig specifically for mine, it’s better to make the current one more generic. As it is now, none of the 4dof linear rigs will behave right.

Either you can allow the distance between the top front joints to change or allow the bottom to rotate a little around the surge axis, returning to center. Or maybe there’s a smart way to do it

I wil do something. I thought yours was similar to this:
https://www.youtube.com/shorts/Sa0zZfYh9Ps

That’s exactly what I was trying to explain. Instead of having the sliding top they have rubber flex on the bottom. My rig and theirs move the same, you can see that the rear actuators do not work when the platform rolls.

Version 3.7 is a significant step forward. Thanks for all the work Pedro.

I am replicating a 3.5 rig and I have run into a few problems.

I used Rotating Actuator 2DOF and Rotating Actuator (2x6DOF) to go from

[A<Axis1a>][B<Axis2a>][C<Axis3a>] in Mover 3.5.2: to

[A<R0.A1.B>][B<R0.A2.B>][C<R1.A.B>] in Mover 3.7.0.x:

With sine wave test sources I am getting unusual serial output. The A and B channels are of the form A<#><#> or B<#><#> as expected.
Channel C is of the form
C'rapidly changing number or letter'<#>

Is this a config problem or a bug in (2x6DOF) serialization?


PS

There a couple of persistence bugs

Rotating Actuator 2DOF rig - actuator swap flags not persisted.

Rotating Actuator (2x6DOF)
- "Housing Joint" config not persisted
- "Crank direction" config not persisted

We tested Version 3.7.0.17 today. Works great!

I've just discovered a strange thing in the XPlane source.

If I'm standing still on the ground I think the vertical acceleration with gravity should be close to 9.81m/s² and the longitudinal acceleration should be clode to zero. However, they are exchanged. I've cross-checked with the old Mover 3.5. There it's also not quite right but at least different.

Vertical acceleration (without gravity) of 8.7m/s² is strange while standing on the ground. It could be that this is a bug of XPlane, but there must also be something wrong in Mover because V3.5 and V3.7 behave different.

On both, 3.7.0.16 and 3.7.0.17, looks that the player source is not playing previous recorded files.