FlyPT Mover 3.7.0.9

Ok it's just a fake virus, but for mee i can't test because no RIG 2 DOF..... error with source : Flight simulator.

Hey @pmvcda ,

first of all: Congratulations! Hard work, many sleepless nights and lot of stress to bring life and this together I can imagine. Thanks a lot, really! ❤️

I'm on vacation at the moment but will try this ASAP when I'm back home. Thank you so much!

Best,

Ben

P.S.: And now continue in smaller iterations please, I guess it's better for your health.

Should be there... I made it as a plugin, let me check where it is...

In RIG module where I but range of linear actuator?

Or is L5 value something else than middle extension?

Not here...


More UI Bugs:
This is on Dirt Rally 2.0 source, others likely impacted similarly.



Text is cut off, IP address field gets garbled.

On the Rig page for linear hexapod:



Numbers are cut off. I think this has to do with the same problem that causes the issues on the source page as well. You must have your text size set at 100%. On my monitor in Windows 11 I have set undier System->Display->Scale to 150% (Recommended) with my high resolution screen which is what messes up the sizing here. This just means the UI library you're using is not aware of this setting and not rendering properly. It also means that the location data that is saved is not correct so when I have my setup saved and change my scale to 100% (to thest this) the Mover window ends up way off the screen when I load a profile that was saved with a different scaling setting. This is a problem. Once I change my scaling to 100% the text renders correctly.

Next issue:
When I just open up Mover and try to load a file I get prompted that my current settings are not saved. I haven't even loaded a single module yet, there should be no warning unless I actually created/made a change in the blank profile.

Next issue:
When I select Edit->Center All Modules on Screen. It centers the modules on the primary display, not on the display that the Mover main window is. This is unexpected and probably not ideal.

Next issue:
In Pose from Motion, the generated sway/surge/heave/yaw/pitch/roll values all read 0 even when I move the sliders around and the Result column shows a value, the bottom drop-down shows nothing just zeros.


What is L5 meant to represent? I figured it out, rather than the mid-point it's the min point now and range is defined within the Actuators.

So having listed the bugs above just on a cursory look of the interface I'm also going to say the new feature that I'm mainly interested in (safety fencing between actuators and pedal volume) seems to look and work fantastically well! This is all looking at it on the 3D view only so far, but the idea is really awesome!

The fact that any variable can be used in any filter in combinations along with the IF statement makes this extremely powerful!

One more suggestion: In the variable selection you can only select the output of a pose to be the input of a filter, I'd like to see the option to select the input of a pose to be the input of another pose. Case in point: I'd like the lateral acceleration and roll position to be together in a filter but I'd have to pick them from the source output today and if you have multiple sources the system breaks down or becomes painful as I'd have to add them all together (assuming inactive sources report 0). It's doable but seems a bit more complicated than having the ability to pick the input side which does the aggregation of sources all together already.

Again, this looks extremely promising and I'm super excited! As soon as there is iRacing source available and I have a bit more time I'll get this thing going on my rig.

L5 is the min point, so L5 = mid - (range/2), then you put -range/2 and range/2 into the actuator settings for Minimum and Maximum position values .

Also, ironically after adding a 3d viewer to my mover profile I could close the settings without it asking me to save changes. Seems like the logic that determines whether a profile is "dirty" is not working properly.

First of all, thank you very much for your effort. I have downloaded and tested it, and there have been significant changes in the UI (for version 3.5.3). I haven't adapted to it yet (actually, I still think the UI of version 3.5.3 looks better). I only tested the AC and have found an issue. When I click on the connection to output the serial port and then disconnect or change the output time, the output will get stuck. I need to close the software and restart it to solve this problem

Yes, the logic changed. Not sure it was for the best...

Pedro, I believe this is now absolutely the best position and motion software for motion simulators in the world! It's time to start a Patreon or something like that.
Please can you advise me on how can I limit the actuator's speed or the motor rotation speed? I remember we talked about this if I'm not remembering wrong (unless it's not locked yet)
Thank you a lot

Thanks, but to many bugs to call it a software...

Do you mean limiting actuator speed near limits or general?

For general, my idea is to have a filter that limits change rate, hope you understand what I mean.
The problem is that it should be used on the rig not the actuator or it affects VR compensation....
You can try the DELTAFOLLOW/DELTAMAX, but they are quantitive, not speed

Near the limits I have some new filters. With so many things, I don't even remember what I included...
I remember the LOGISTIC3.
I had to cleanup big chunks of code and some of them where experiments that included some filters. I have to see it better, but look at the new filters. They are many... No manual for now.

Yes, the DELTAMAX works very well, I will find the value more similar to my actuator's speed. Now I'm trying to put this function in (Setup of six linear actuators) and, if I'll meet too much discrepancy between the rig and the VR Motion compensation, I will move it in the rig.
About the "near the limits filters", I'll put LOGISTIC3 in the (Setup of six linear actuators) because, since should minimize the shock when each actuator reaches the limit, I will evaluate the effect the VR motion compensation

Havent been able to make Thanos AMC work trough serial. I suspect it is due to missing 250k baud rate. 230400 is available and that somewhat works on Mover 3.5.3 and 250k works as normal so it may be another issue. I suppose i will wait for the Thanos output to be enabled.

Im using the same string as custom string on 3.5.3 with <R0.A1.B> instead of <A1> Ive tried .P .T and so on
3.7
<255><255><R0.A1.B><R0.A3.B><R0.A2.B><0><0><b4><b2><0><0><0><0><10><13>

3.5.3
<255><255><a1><a3><a2><0><0><b4><b2><0><0><0><0><10><13>

When looking at the output of send when connecting it is identical but there is generally no reaction in the actuators though i can sometimes see them move slightly.

The new motion compensation alghorithm already does it for you.
It kind of makes a LOGISTIC for the pose whwn actuators reach limits or pose is near singularity

Just tried, and the filters/function in the (Setup of six linear actuators) have no effects on the 3d viewer modules

Did you set the correct number of bits in the rig?

Because the rig uses by default the new motion alghorithm. Try changing it to another one.

This one is important, but strange.
I can't reproduce this.
Scaling desktop is OK
Scaling text size also (only the menu size changes)
Help me, what am I missing?

As far as i can tell the setup is identical to 3.5.3 at 16 bit. 99% of the time there is no reaction and when there is the movement is very small on string.

EDIT: Upon further testing. 3.5.3 with Thanos and serial 250k baud will move the rig slowly to position but then sometimes after a short amount of time after reaching become higly erratic. When using Thanons output it is fine. 230k baud will move actuators slowly to full extension the be unstable moving back down. Using serial seems to be unstable. At least on my system. Only Thanos has an issue. I have multiple other serials connected to Ardunio that works normally

<255><255><R0.A1.B><R0.A3.B><R0.A2.B><0><0><0><0><0><0><0><0><10><13>

I Have tested with Mover 3.5 and 3.7 side by side and to make sure when only one version is open at a time. 3.5.3 works for initial movement and is slow to reach set position but seems to be highly unstable and causes erratic rig movements with no change in values while as stated using the Thanos output is working normally. 3.7 serial does not move. Outputs looks identical apart from baud rate.

Also tested these rigs.
Rig 3dof. tested 4 feet, 3 feet 1 front, 3 feet one at rear
Rig 4dof 4 feet

If i change one of them, it does not matter which to P or T instead of B the rig will move all actuators but become unstable and erratic an has to be disconnected/shut down before reaching limits. Changing more than one B to P/T will result in no movement. So it is clearly able to move the rig but something is wrong.

Example: <255><255><R0.A1.P><R0.A3.B><R0.A2.B><0><0><0><0><0><0><0><0><10><13>

P is position in mm
T is motor turns
B is bit value

Ok need to review this... will add the 250000 don't know how I missed it