FlyPT Mover 3.7.0.15

Are you using 19 bits?

Edit: Are you using WYBOsimu as a controller?

In fact i only want to move longer, due to the resolution of AMT102 is 8192 pulses per revolution, so if the output range is 19 bits the pulse will be 524,288, it will twist the ball screw 64 times, but current situation is still move tiny. so i think maybe the other parameter i didn't set correct.

Hello,
Dear colleagues, I've been using FlyPt for years. I'm very happy with it. I have a question: is it possible to use the platform from photos?
If so, could you tell me where I can find such a tool?
Best regards, Tadek

Hello,
Version 3.7.0.14. I created a settings file and saved it. It gives an error when loading. The settings file is in the application.
It was also saved as default settings. When I tried to launch the program, it froze, preventing me from doing anything. Manually deleting references to FlyPT in the registry helped.

Another error. When disconnecting from MSFS2024, an error message appears.

Same here.

Is there a solution for Motion Compensation using triple screens and Movers compensation output?

What are these filters for? I assumed that the pose data would be filtered before being sent to the actuators. This doesn't work in version 3.7.0.14.
I'm setting up a logistics filter, but the platform's movements are outside the set limits.
Am I missing something, or is this a bug?

Selected the item.
Received an error.

Hi Pedro. I noticed that from 3.7.0.10 on I can't load profiles saved with earlier versions anymore. That is, the modules are loaded, but with default values. That isn't a tragedy, as I can load a second (older) instance of Mover and copy'n'paste values or whole filters ─ I've done this before.
However I wonder whether there is some caveat when doing this? There must be some reason why a simple migration is not possible anymore...

Hi!
The logistic function doesn't work in this formula: LOGISTIC(EMALP(EMALP(EMAHP(VALUE;2000);72);1200);160;1) . Am I doing something wrong?

I tried replacing it with LOGISTIC3. It doesn't work either.

Just for information updating to 3.7.0.15 freezes at 100%

Sorry for late reply.
You can for example limit the motion of the rig in those filters. It's the main reason for their existence.
You can also use for crash filters.
But until 3.7.0.15 there was a bug where the filters where not working.

There's to many changes internally. I will try to do an importer, but only when it's more stable.
That's also the reason profile sharing is disabled for now. It's all done there, but with some changes still to do it would be a bad idea.
Sorry

Mover 3.7.0.15 Beta

Release notes:

Work in MIDI controls (not working yet...)
Added new tool: Video recorder, for future integration with source recording
Updated Racerrom telemetry
Solved many bugs, worst in the rig module where the filters where tnot working
Updates in UI controls, scale and colors (still WIP)
Updated 2DOF rigs user interface
Many other small updates
Flight Simulator DLL's now embedded in the EXE, so mow Mover is only a single exe file

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

Already working on the next one...

Could it be that the latest ZIP file (3.7.0.15) is only 2 bytes long? I don't think I've done something wrong with github because version 3.7.0.14 works.

@Aerosmith and @S2. ,

Updated the file in github. It should work now.
Sorry, I renamed the original file in github and it seems that might be the cause of the problem

We updated Sven's rig from Mover 3.5 to 3.7, yesterday. After having sorted out the issues with the broken file of V3.7.0.15 everything worked quite well. The new motion algorithms and the hierarchical naming of variable are definitely an improvement. I also noticed that automatical connection to Xplane now works.

The fact that old setup files (from V3.5) can't be loaded or converted is bit annyoing. We had to type in all values from the old setup manually. Even exchanging files from V3.7.0.9 to 3.7.0.15 doesn't work. At least the pose filter settings were ignored, everything else seems to work.

Another idea: What's also quite time consuming is the fact that there is no manual or no cleaned-up online help available for the new Mover. The links on the first page of this discussion are very helpful but you still have to browse multiple pages to find the information you're looking for.

I have to admit that I know this problem well as I develop and sell software by myself. If I have the choice between implementing new features or spending time on the documentation the paperwork looses almost all the time. But what about delegating this unpleasant task to an AI? Has anyone tried asking ChatGPT to extract the information from this thread and writing a user manual? Or we could create a shared Google document where any user of FlyPT Mover could add a chapter whenever he/she found out something new so that everybody else doesn't have to ask again.