FlyPT Mover 3.7.0.22

Not working ACE, but from
ace/acr source working ACC))

Are you saying the ACC source is outputting the ACEvo motion data?

no, ACC on ACEvo source. But on this source should be work evo and rally

In the last release? It's working here... unless they updated something in the mmf, i have to check

No it is AC Evo's fault. New release .6 They are working on getting the MMF location announced.

Is this version of FLYPT Mover compatible with a DOF Reality H3- style rig. I am not asking about on the firmware side, but specifically about pose and rig calculations. I have spent the last few weeks trying to use the 2DOF rig with a direct for the traction loss but I cannot get the rig output to drive the actuators properly.

At first the rig was reversed with the u-joint in the front and the actuators in the rear. Once I corrected that by using negative measurements where needed in order to get the u-joint in the rear, I couldn't get Mover to drive the actuators through their full range, in virtual testing, and additionally the rig would show that the actuators reversed direction mid way through the range when manually moving the pitch slider in the pose. If there's no way to correct this then I will just return to SimHub

@loadleft ,

I will check the direction change in the actuator.

You mean this one?: https://dofreality.com/product/racing/motion-racing-rig-3-axis-hero-h3/
or the older one?

You can set dimensions to match the 2DOF (pitch and roll), but yaw needs a direct.
For the two front actuators you can use the rotating 2 dof rig.

I used this dimensions just for testing:


Dont forget to set the crank and rod sizes:

Note: I'm guessing values, you need to check

For yaw you can use a rotating actuator, i set it like this:

It's most certainlly wrong...

Connection string is serial and should be like:


The output is like SMC3, where yaw is actuator #3 in the string
Left actuator is #1 and right #2

It's on my plans to add the exact rigs from DOF Reality. I asked them for data, but never got it (dimensions).
that would give a better motion compensation in VR.

Maybe for now, use SimHub if they have the rig setup, they officially work with Simracing and Simtools. But keep an eye here.

Since the MMF location has changed you have to modify the AC Evo source? Not something we can DIY correct.

Just found this on Steam:
AC Evo .6 shared memory info
https://steamcommunity.com/sharedfiles/filedetails/?id=3707421508

Yes, i have to change the code
Next release

Due to not fully understanding the proper reference points I most likely have measured wrong. In the attached screenshots you can see in the 3D viewer the issues I'm having with range with range and geometry.

As for hardware, yes, I have the SFU version of the Hero rig you linked to, except that I've modified mine. I removed the DOF Reality controller, firmware and encoders. I replaced them with an Arduino Mega based controller that accepts the connection serial string actuator inputs formatted [right,rear,left] using a scale of 0 to 1000 (bottom of actuator travel to top) in order to accept 10 bit output with the last (top) 23 steps cropped, and I mounted AS5048S encoders on the control arm rotation shafts for better positional accuracy.

sorry for double posting pictures. I can't seem to edit the post now

You can disregard and thank you so much for the information. I just realized that I was mixing units of measurement. SMH on my part!

Mover 3.7.0.22

Release notes:

General:
Modified transforms to allow rotations at different locations

Added control to define COR (single or multi)
New icons (go to options and dissociate/associate again the files to the new Mover release)


Hot controls:
New Conncect/Disconnect button with toggle logic. Same for checkboxes.


Main window:
Corrected bug making added modules appear at strange locations (in menu it adds at center of diagram, with right click menu it shows at click location)

Sources:
Elite:
Made some changes and corrected bugs, now get's updated hooks online, and rotations where changed to speeds instead of angles
XPlane 11 and 12:
Reworked source, now you can patch XPlane with a plugin and set custom values by editing the cfg file. (please apply patch again)
It's way more efficient and faster than sending and receiving requests.
The plugin should also work in XPlane 10 (you need to patch manually)
Dirt Rally 2:
Correcetd bug while patching, the VR version was missing in the patch (please apply patch again)
rFactor2 and Le Mans Ultimate:
New plugins and updated patch code (please apply patch again)
New source for AC EVO with the new data
AC Rally dedicated source
New optimized AC and ACC source
Changes in the MMF sources internals (optimizations)

Rigs:
Changed rigs COR's to allow different centers of rotation for each rotation (using new control for COR)
All rigs and actuators changed to this new COR (need to review calculations for further optimisation)
Corrected bug where some actuators values where not saved (rotating actuator, linear slider and rotating slider)
Added Linear 3DOF rig
Limited the linear and rotating 3DOF rigs to be on the ground


Outputs:
Added tcp server output, now you can stream values over tcp (UI needs more work).


You can open the dash example from the module with the default string for a demo

Direct link: https://flyptmover.github.io/Dashes/Example1.html

Tools:
Added IPv4 to check what are the IPv4 of the system

Dashes:
Added demo dash for testing with the TCP server, you can run it in any device, phone tablet PC that lies on the same network of Mover

Known problems:
Many internal changes to solve bugs while opening and patching sources, there's still errors
New COR needs more testing and updates on the 3D rendering to show the axis as thwy are defined
Hot controls need testing, specially with MIDI feedback
Missing values for dashes
Dash example is not 100% active, some info is not connected yet

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

Awesome as ever good sir!! Back to bruised ribs in the sim rig from the new Rennesport 911 in ACEvo!

AC Evo now includes wheel slip angle information any of you geniuses out there want to talk about best ways to use that data to build a decent traction loss cue for Mover?