FlyPT Mover 3.7.0.9

I trust you since years my friend. 3.7.4 is not marked as a virus too.

three/four 3DOF ; choose 4 actuators.

in simhub I am using 3 DOF as well.

the picture in 3.5.2 shows actuator 1 = FR, 2 = BR, 3 = BL and 4= FL. I change this to 4,2, 3, 1 because first output is for the front part and second to the back part.

when I am try manual heave from motion pose all sliders in the rig goes to the same direction. What I am need is to swap the out put for front right and back left motor. And how can I minimal tune, because when I am move the heave slider a minimum the rig is going to maximum (wrong heave). Even when I set output gain to 0.05

Just released a mod for VTOL VR.
It's on the workshop for VTOL VR Mod Loader:



Data changed a relative to the original one, so it works only on the new Mover:


Current Mover already includes this source.
Unfortunatelly I could not get all the values I wanted. So some of them are wrong, but the main ones are ok.

Hello,
same thing for me, seems that no more data are received from MS FS2024

thanks for your help !

First of all, I’d like to thank you for creating such an amazing piece of software! I’ve been a big fan and really appreciate all the effort you’ve put into it.

I recently upgraded from version 3.5.3 to the latest one and noticed something while using it with Assetto Corsa (AC). After configuring the settings, I realized that the motion for pitch (during acceleration/braking) and roll (for cornering) seems to be missing. Instead, I’m only getting movements for surge and yaw.

Could you please let me know how to set it up so I can use pitch and roll to simulate these accelerations? Thanks in advance!

Let me test. Could be a bug.

Sorry, was supposed to have a release with that bug fix, but been trying to solve it...
Today we get a release working, but not with the feature i wanted.
It's missing the crash detection that's causing me to many problems. It should be something stupid...

Mover 3.7.0.9

Download in first post of this topic

Release notes

Rigs:
Added some pré definitions for hexapods (temporary solution)
Limited gain to a range between 0 and 1 (for safety reasons)

Sources:
MSFS solved bug causing connection problem.
VTOL VR now with the corresponding mod in the Steam VTOL VR Mod Loader workshop (not VTOL VR workshop)

Known problems and bugs:
MSFS enable/disable motion in crash is not working!

Pedro, if you are not too busy, which you probably you are, may I remind you to add the parameter in the "Follow pretended pose even if out of range" motion algorithm where it is possible to set at which point the deceleration curve starts to recover the actuator's stroke?

Getting virus detected warning on windows 11 btw

Thank you for your reply, I’m looking forward to your test results. If it turns out to be an issue with my settings, could you please let me know where I can adjust the parameters for acceleration and centrifugal force on the pitch and roll axes?

It's working for me.
Can you post a screenshot of your pose and output please.

@pmvcda Thank you very much for converting my rig to the new Mover. It's moving, but I have some problem with trying to scale the rotation to sync with the actual angles. First time I tried scale 0.6 around 0 and added a filter to the value EMALP(VALUE;50) - same I had on my previous file, the rig crashed. No I'm trying without the filter, but after I added a scale 0.9 around 0, closed that window, then reopen - it show some weird scaling values - I never entered -50!
Each time I open the dialog I see different scaling values in both fields. When I try to slowly change the scaling in any direction, all actuators keep moving down wether I press up or down arrows, until they hit the end of the range.
Without scaling it's moving correctly in all axes, so I think you have some kind of a bug with scaling, or I misunderstand how it's supposed to work.

Ok, thank's will take a look.
I think it's just UI but need to test. Usually I ignore scale for testing so I might have left that behind.
Where the COM ports correctlly recognised?
In my rig I use two COM ports and don't have problems even on the old Mover.

Is the actuator scale the correct way to match the requested angle to the actual angle of the rig? If so, something fishy was going on there for sure. I tested twice and both ways the rig kept moving to the crash position. Eventually 2 of my temporary plastic motor arms broke. So can't test further as I won't be printing new ones because I should be able to fabricate metal ones in a few days, hopefully.

The new Mover remembers the COM ports correctly, the old one forgot all of them. I had a similar problem with the old Mover even with 1 Arduino on my 2DOF - sometimes it saved the port, but often it forgot them and I had no idea why. There is one bug or a quirk with the ports in the new Mover. Here's how they are set on my PC:

COM11 is my DIY button box so ignore it. The rig is 31,32,33. But here is how the Mover sees them:



For some reason, the last one is always seen under a different name, despite the boards and their firmware being identical. It doesn't seem to affect the operation, but I'm just reporting this in case it may be a sign of something that matters.

And just in case, I opened the scaling again and I saw the -50 again, which I never entered:

I don't think it's just the UI, because the rig kept moving down and eventually crashed twice, despite me setting "scale around" to 0 and trying to increase or decrease the scale with the little arrows. The rig kept moving down slowly and crashed, so I think it somehow actually moved the center from 0 somewhere way outside of the range, like -50 sounds about right. I tried it several times, but I was able to press the Emergency Stop in time for other attempts not to crash the rig. The first time I left the "scale around" to its default setting - somehow it had "45" there. Or "-45", not sure. I just tried to check"use scale" and enter "0.7" that I had in the old Mover. That didn't go well. Then I tried the same with "0" in "scale around". And got the results I described.

Thank's,

I checked the code and from what I see, the error is when showing the scale because I make a mix of updates in the controls. The UI is causing the mess.
I'm correcting it right now and making a revision on the actuators to be sure. (removing default that is useless also).
For the USB, can you go to tools->devices and expand the joysticks.
You get something like this:

Post here so I can check one possible bug in the naming.

Edit:
Please expand also the Serial port devices...

Somehow I see Joystick and Midi sections twice

Thanks, I will look at it after the actuators.
It's amazing how I use everything in my rig without problems, then someone comes and finds bugs everywhere...
I need to diversify the tests. Usually I'm testing new sources/features and don't touch in those areas. Sorry.

Nothing to be sorry about It's a complicated piece of software that is doing an amazing job in a wide range of rigs. Bugs are inevitable. I'm very excited for it to be on track with the completion of my 6DOF build. Such a serendipity! Hopefully, if I don't hit a brick wall like a wooden frame too weak, or motors not powerful enough etc. I will have the rig fully working in a couple of weeks.

Could it be that the Virus Warning is triggered because Flypt is distributed as a single .exe file and extracts its components (.dll files) at runtime…?

FWIW I didn't have any virus warnings on Win11 when downloading and installing the latest beta.