FlyPT Mover 3.7.0.9

Just checked.
It's a bug already solved.
Take a look here, I will post a new build today 3.7.0.8.
3.7.0.7 is out, but I did not post here.

Some info on DIV:

If division is done by zero, it returns maximum or minimum value allowed depending on sign of numerator.

Mover 3.7.0.7 BETA

Release notes for 3.7.0.7 (22-11-2024)

General:
Revert to .net8 (some problems with tasks...)
New code for serial that should solve the detection of some hardware.
Naming of the devices should be better. After the first detection some devices might be renamed on a second detection.

Sources:
Optimized air/ground code
Added Falcon 4.0 BMS

Added MSFS 2024 (same as MSFS 2020, just adding image and links to start/stop MSFS 2024).
Solved bug causing thread to pause while trying to connect to Simconnect.
Solved bug in image rotation (kept wrong image in some situations).

Outputs:
Corrected bug when pausing the data stream. Now the data flow stops.
Keep autoconnect checked when we loose connection due to an error.
Motion4Sim
Added shutdown button.
We can now select where the motion cueing is done (Mover or M4S).
If M4S, we are sending the rig pose instead of the actuators position (use the just pose rig, but any other rig also works)
Corrected bugs while testing for 24 bits actuators.
Corrected bug in key for direct actuators.
Corrected bug causing serial data problems (might have some yet).
Thanos:
Corrected bugs while testing for 16 bits actuators.
Corrected bug in key for direct actuator.

Known problems and bugs:
Thanos and Motion4Sim are stil WIP.
Pausing outputs while transitioning to connect/disconnect can cause jumps!
Missing features of 3.5.3 that are still WIP.
Crash in when opening default source/game/vehicle using high precision timer

Mover 3.7.0.8 BETA

Release notes for 3.7.0.8 (25-11-2024)

General:
Solved bug in DIV operation.
Added MAXSPEED and MAXACCEL filters (WIP, needs testing).

Sources:
Added Elite Dangerous(thanks to Wagnard hooks that are updated frequently)

Needs more testing. I think current hooks need to be updated.
It automatically get's the latest hooks.

Poses:
Adjusted size of tires (was wrong with scale on windows)

Rigs:
2DOF rotating now similar to Mover 3.5.3 (swap and swap swapped added).


Known problems and bugs:
Thanos and Motion4Sim are stil WIP.
Pausing outputs while transitioning to connect/disconnect can cause jumps!
Missing features of 3.5.3 that are still WIP.
Crash in when opening default source/game/vehicle using high precision timer

Hi i am making a survey of the 3.7 to fit it to our M4S and MXP 6DOF linear platforms. I don’t get the drawing explanation of the physical parameters Lx of the rig module on the right. It seems also there was change of denomination from 3.53 because in 3D viewer and with same values in same Lx, the rig is banking and also calculated height is different, Moreover, L5 is not explicated….is it normal I don’t have the same kind of drawing as in 3.53?
Also in the M4S output module, I could correct the 16/24bit for all actuators except for the first one that stay in red….
Thanks a lot

It's WIP. Drawings are still missing because I was considering some chages in the dimensions.

To use MotionXP Prime, use thhose dimensions:

This one includes colision detection for the pedals.

For MotionXP Bumble use:


In the next release you can select a pre defined rig and will get more for those rigs soon.
For the output, I have to check. Made some changes in the last build. Need more testing. But I think it stays red, but it's just a UI bug. I will check the output.

This is still WIP with frequent changes and optimizations. Be careful.

Edit: forgot to say about the actuators.
Click on the button setup of the linear actuators

There you need to set 24 bits and the range by sayin the minimum and maximum values
In prime -300 to 300
In bumble -200 to 200

if you are interested, I worked a lot on the DCS to FlyPT.lua file of the 3.5.3 to refine the code and add functions to the missile kills processes to stop the telemetry initially created by DerKlausi.
I have added the management of all kind of groud/sea/CVN/Tree/ buildings/obstacles crashes using check of velocity discontinuity through derivative survey.
I also added the management of ejection or pilote death where the telemetry, which is linked to the aircraft need to be stopped even if the pilot is under the chute tôcope with aircraft crash alone.
This takes also into account the normal flight with canopy ejected or open for warbirds as the test is done on the pilot. Works also in MP. The file has been disseminated by Hervé among MXP customers.

Wow, i have to check it. Can i use it in Mover?

yes it works well with 3.53, I could adapt it easily for the patch of the 3.7. I am going to ask Hervé to send it to you with the read me through whatsapp. I have checked the 0.8 with DCS this evening (not connected with M4S for now) it works well with same profiles as 3.53 (I just copied the filters and changed some like MINCROP and the Butterworth sintax that have an added third value I dont know is it for) but I find it quite smooth and lazy compared with the 3.53. I'm going to make an exhaustive comparison using .trk file same profile and making videos of both 3D view in same context to be sure. I also need to check the fencing protection but later on.

Hi Pedro, Just updated to 3.7.0.8. Excited to try the updates. but I'm not getting any data from MSFS data now. "Connect/Disconnect" flag is yellow. Tried 3.7.0.5 to make sure it wasn't something else and that it is still working. Also tried changing the values of the new pulldown "Enable Motion", but no luck.

Oh, I made something that broke it...
It was working. I think I might have undo something. I had the var type wrong and might have reverted it...
Will check and post a new build today.
I'm having problems with the crash event. And that one might not work as it should I have to test it better.

Hi, Hervé sent you the lua file this morning, I am working on slight improvement to restart of telemetry when change of slot in MP and will adapt the code to 3.7 patch. Will make it sent to you when ready and tested.

Thanks.
In the new Mover we can patch games with that little pen button. It's generating the lua file automatically.
I will share the lua files in the flyptmover site when this is stable to allow manual patch.
So if you use that, you might overwrite your own lua. Be careful.

The 3rd field in the Butterworth is for time between samples.
You can set the time in milliseconds (by default Mover works at 2ms loops) or keep it at zero and use the calculation elapsed time obtained by Mover itself (should be more precise).
The difference you are feelling might be related to that since in the old Mover I used the user defined calculation time and there's always some difference. To make it close, try to use 2 in the samples interval.
Idea is to have same results for 1ms, 2ms or 5ms. They are different because of the resolution, but you get more or less the same response.
There's no other reason for the difference in the filter because the code is the same.

Hi Pedro, thanks a lot - again - for the great work!

As regards Thanos, what do you exactly mean by WIP?

When connected to Thanos the test sliders in my rig module are ineffective whereas they are effective in v3.5. Is this normal?

Thanks
Best regards,
Alex

Need to check that.
It's wip because i want to add dedicated features to Thanos4u abd board type detecion
There's also bugs like what you found.
But, the new outputs should be way faster and allow a smoother control

I'm not sure it's a bug, that's why I was asking.

Maybe something I did wrong....

I just picked a rig module, selected the right com output in the Thanos module and selected the actuators corresponding to the rig in the thanos module. The link between the rig module and the Thanos module appears on the chart, the Thanos USB AMC controller's display says "receiving data" but when moving the sliders in the rig module nothing happens. I'll make pictures tomorrow if need be.

Thanks again!
Alex

Hello,

I am experimenting again with the older (non-beta) version and have managed to set up 2 Output Serial connections for SMC3. I linked [A<Axis1a>][B<Axis2a>] to COM3 for the front two actuators and [A<Axis3a>][B<Axis4a>] to COM5 for the rear two actuators.

I would like to add a rig in the 3.7.x Beta version, similar to a 3DOF with 4 linear actuators, but with the ability to swap directions. This is because I am using rotational motors. It is possible to do this in SimHub, but unfortunately, it does not support flight sims. While the official SimHub does not support 4 rotational motors, it works astonishingly well in my setup.

Will it be possible to add a feature in future versions to swap directions (in my case, Motor 2 at the front and Motor 2 at the back)? I would really like to use this setup to play DCS. Thank you in advance!

Additionally, I noticed that the speed setting of 500000 is no longer available in the dropdown menu. Only 460800 or 576000 are available, making it impossible to establish a connection.

The last version I tried was 3.7.0.3.

What is wrong?

Please show me your rig and the module you are using (settings)
In the latest version (3.7.0.8) you can edit the baudrate and write your own.

Yes, now Windows is like that... I had the files in Google for virus check and they where marked as virus.
Downloads where blocked.
So I started using github because Mover makes the update alone and replaces the exe with the new one if you want to. The links in the first page are for github now. They should work, unless your antivirus is marking them also...
You have to trust me. From what I know there's no virus in the files and I'm the only one with access to the files in github. So...
To solve this I would need to register Mover or something like that and pay. Well, I don't want to unless this brings me a bunch of money to pay for that. (and I would need to do it at each release and have an installer and ... and ... € and $ and fu*** them Sorry just a rant, it's the world we live in now).