FlyPT Mover

Glad to hear it

Can you believe that WRC 2023 has telemetry only for DBox...

Same here - glad to hear you're on it, and glad to see you seem to be fine enough to post here

@pmvcda we love you

I would like to know when will be available the commercial version because I'm starting to commercialize my 6DOF and I need to sell your Flypt in bundle with my machine (just hoping without a subscription for commercial usage )

Hey Pedro,

thanks, the server error got me a heart attack. If you need support regards servers for the FlyPT project, give me a note.

Thanks for all the passion and work you put in to the project. It gives me a good time.

Best,

Ben

Glad to see that you are back at it, Pedro!

I belive the latest update (released yesterday) for WRC 23 included UDP fpr PC!

I noticed, I added it last night and it's working:


But there's still so many bugs on the new version and some missing sources like FS2020...

There's a new source for joysticks, it now allows keyboard keys and behaviors:

Thank you Pedro for your efforts, do you have estimated a time about the release of the fixed version?
I'm aware this argument bothering you, and I'm sorry for that.

It's not bothering, but wish I could say when.
Each time I add something, I find another bug, and some are nasty.
I want to release this year at least, even with some bugs, but not the nasty ones.

Thank you for your continued development.

What I currently miss is a speed limiting function for poses. Mover works by adding up pose commands, but there is no possibility to limit speeds for individual pose effects (other than dampening with filters, but this is not absolute).

What I was thinking of is a MAXMOVEMENT(Value; StepLimit) filter. This would limit the commanded pose to be within a circumference around last commanded rig pose.

So say I am at -1 pitch, I woiuld like the platform to move to +5 pitch, but in such a way that the rotation is not discernable to the VR user. So I limit the movement with the fiter MAXMOVEMENT(Value; 0.002). So with a standard loop time of 2ms, it would move by one degree per second.

Internally, the filter would act like a CROP(Value-RigPosition; -1*StepLimit; StepLimit)

In my example, this would give MAXMOVEMENT(5; 0.002) == CROP(5-(-1); -1*0.002; 0.002) == -0.98

I would use this filter for motion queing, where it would take care of both the mixing in of sway in roll and surge in pitch, and also all the washouts. These are all things which should not be discernable to the user. By making the platform constantly, slowly "chase" surge and sway by rotations, I could simply give cues without adding wash out, because the washout is always provided by the platform chasing the surge and sway rotation. a 6dof would also have pose filters to slowly move all other dimensions to 0.

Edit: it would maybe be easier to have discrete commands for all dimensions, that would remove the complexity in determining the difference between the commanded dimension and the rig pose. Those discrete commands could simply reference a single dimension of the platform instead of calculating a "bubble".

Alternatively, this could also be implemented as a "pose from motion with speed limit". Where one would add targets for all dimensions as a normal pose, but Mover would execute them within the confines around the current position, specified in degrees/s or mm/s.

That's a great feature which other users requests as well, also a linear acceleration/deceleration ramp would be really useful.

I will add MAXMOVEMENT or something like MAXVARIATION to make it for all values, not just movement.
There's another feature I did not talk, I'm adding plugins, and for now only the filter/operations is working.
Can't show much, but it's in the menu and some of the filters in the lists are plugins for testing:

Ignore the main window, it's WIP, and the menu needs cleanup

By the way, we can now assign keys to modules:



And reach the values of the modules in any filter/operation control or use them in the outputs.
Something like:


The module in the example is a new pose, generated just with filters/operations:

An example of an ADD plugin code:


(There's a bug there with to many decimal places, but the code is similar to this)

Another feature:




When possible, sources allow you to patch/unpatch the associated game and start/stop the associated game
In the images the source is for 3 games, so we can select the one we want (images are rotating)

The info about the game is searched in the registry to make it easier.

Another feature is that we can now store a default setup in the registry, that opens with Mover.
That way you can define the rig and outputs for the hardware you have and it's always present at startup for empty projects.

Hi

I am so happy to see you again ! can't wait to see the new version

Thanks a lot for you work, it makes dreams possible

If the new Version supports Filter plugins, this probably means that Movers Filter System can be dynamically extended with new functions, just by placing a compiled C# dll in a plugin folder.

Thats great news, as Developers can then code filters themselves, thereby reducing the amount of feature requests you constantly get.

Just ended a full review on MSFS...



Any special requests for extra vars?

Please, please add spoiler flaps ! Thanks a lot!!

OK, added SPOILERS LEFT POSITION and SPOILERS RIGHT POSITION vars.

Was also thinking on those that want to make ffb joysticks and helicopter (cyclic and collective) controls, wich vars could be needed?
Anyone?

Vars are here: https://docs.flightsimulator.com/html/Programming_Tools/SimVars/Helicopter_Variables.htm
and here: https://docs.flightsimulator.com/html/Programming_Tools/SimVars/Helicopter_Variables.htm

Its me again: when flying helicopters, the vibrations comming from the rotor through the axis accelerations are quite soft. So it would be great to add some more vibration with help of "pose from rpm". BUT in helicopters the motor is sometimes a turbine with a much higher rpm than the rotor-rpm. So its not possible to use the motor rpm in this case.
Long story short: it would be great to be able to receive and set rotor rpm as an alternative to motor rpm.
Thanks again a lot! You are THE hero!!