FlyPT Mover 3.7

Strange, I have those cuts everywhere now.

Ok so one has to start a new config from scratch in order to avoid transmission issues

Hi @pmvcda and @SilentChill:
You are right, Insectatech is offline since a long time.
The reason why I talk about Insectatech is, that Insectatech was the creator of the custom-Odrive-firmware that was and still is shared here in the community.
Personal I use the official Odrive-Firmware for Odrive 3.6. There are some important new features like limiting the torque. Since the day I set this parameter, I never had an Odrive/actuator switching off and falling down

So I just fired iRacing up tonight with 3.7.0.2 and this is actually now workable! Kudos!
There still some of the existing bugs that are already known but OXRMC works! It is doing what it's supposed to be doing with OXRMC 0.3.8beta. Looks and feels solid, things are genuinely looking strong.

The issue with directs not outputing values from their source until you open them still exists, although I have more feedback here. So I opened up the directs while already connected to output but not to source and I used the sliders to move things around and they impacted the output on both my M4S serial and my Arduino Fan serial. But once I closed the directs and started iRacing and connected to the source the data wasn't sent from the directs until I re-opened their window with iRacing connected and running.

The issue with positioning of the fields when display scaling is not at 100% seems to have been resolved! It looks good at 125%. There are some text fields that are undersized for the text that in them, in the rig module:


Singularity angle, Angle to Ground And Actuators radius are cut off as well as Motion Algorithm.


Same with Heave in the Pose module.

I haven't looked in detail everything else, but reporting what I'm seeing.


Sound in iRacing still doesn't work without the NoSound option on the command line.

But overall this is great progress! I'm going to start looking at the safety fencing feature, probably a bit later in the week and see if I can increase the motion envelope of my rig from 15 degrees rotational and 100m lateral to 200mm lateral and 25 degrees rotational. This would be a massive change!

I'm also super excited about the washout filters that can perform washout with rotational/movement speed limits, once we have telemetry option I'll start modifying my profiles to see if I can incorporate them into my filter flow.

Question/ask: is there a way to also do the same on the onset of a filter? Ie. I'd like to add rotation mix from sway and surge but I want to limit the rotation rate so it stays under the perceptible limit.

So yeah, there is definitely a few rough edges that need polishing but 3.7 for my use case works almost as good as 3.5.3 with the few exceptions and I'm eager to utilize the extra features that are not available in 3.5.3 at all.

This is probably the most exciting time to be a FlyPT user since 2021 .