FlyPT Mover

I have it already with propeller rpm.
When you have an helicopter, the value is the rotor rpm, but i can separate them.
I'm only using the first rotor in helicopters while in planes it's an average of all the motors.

Wow, I am really excited to see what you do for DCS

Perhaps separate variables for apu and engine rumble for large jets unless that’s covered in engine rpm?

I did not find where to get rotor rpm.
But I will look better at it.

What would be the advantage of having the APU? It's just an engine rpm multiplier right?
Even on start, they should be a multiplier from one to the other.
Not 100% sure, but I thought it was that way.

Hi

can't wait to see this @pmvcda , great christmas gift !

Could you add some infos on DCS too ? like gun fire or death/ejection ? thanks

ANd is there a way to drive LEDS via ptmover ? in order to avoid using Simhub

Thanks

I will see what I can do.

Some more info on the new release:

Keys and variables are one of the main changes in the new release.
All modules have keys that we can change:

(by default S0, S1, S... are sources, P0, P1, ... poses R0, R1... rigs ...)

With those keys, we can reach the values from any filter/operation control, something like:

Notice that for sources with air and ground, you have a "sub key" before reaching the values.

We have variables for joysticks also:




A good way to get a list of all the variables is to look at the graphics:


So this gives us many possibilities, specially when using it with logic:


Also, still adding custom variables that I hope can come on release, where you can assign a value or a filter/operation to a variable.

All this comes with some nuances:
Calculation in Mover is made in a specific order. Sources are calculated before poses and poses before rigs.
So accessing vars will get you always the last value calculated.
In a pose, a pose var has the value of the last calculation loop, while in the rig, the value is already the one on the current loop because poses are calculated before rigs.

Hope this opens more possibilities for control and handling. Kind of an advanced user feature.

Ah, when ACC was running, everything was normal

May I ask if anyone can share the ACC four axis. Mover configuration file? Thank you very much

OMG in this way we can almost build our own filter. Wonderful, no words

Or make a filter/operation plugin, see last posts.

Logic is nice too. I was using Round functions with other logic to create 0 or 1 multipliers, so I already was kind of using that.

I came to find some info about a "403 error" on launching PTMover for mikL71 from racingfr.com

and I see these beautiful keys and variables
This has a great potential indeed!
congrats

Can it be somethin like this:

That's a filter/operation plugin for the new mover (might change the name from DELTAFOLLOW).
The filter follows the input value, but only allows a specific amount of change.
I have two other filters, the DELTA that is just the variation of value and the DELTAMAX, that just allows a maximum change in value, for example while the value is bigger than what we have in the last filter, it grows the maximum allowed, while the follow, if the value is greatter but decreasing, the last filtered value starts decreasing...

Well a bit of a mess. I'm not good at explaining...

As far as FFB joysticks are concerned, they have their own simconnect reading software and apply the effects so nothing is needed in FlyPT. I actually have 4 FFB axes running now- joystick XY, pedals, and collective.

All the vars I can think of now is if you could read PLANE IN PARKING STATE.. i think its active when the plane is in the hangar (main menu) because as it is now, some RPM effects still trickle through and i get some back and forth movement every few seconds..

Speaking of RPM- like PeterW said, can you separately get prop/rotor RPM vs engine RPM? turbines and jets spin very fast but we need the RPM telemetry to be of the prop or rotor. Or, if the Pose from Engine RPM page had a filter box, we could divide it ourselves by the gear ratio

My only other complaint is that with some planes, it seems the data being put into longitudinal acceleration is only engine thrust. And of course its the planes where you really want it to work- like the F/A-18, when you're on a catapult and you throttle up, the rig tilts back but you arent even moving yet. When the catapult launches, it doesnt feel any different. same thing happens when hitting the brakes after landing, the acceleration is only following the engine thrust and you dont feel the brakes working. I'm not sure if there is some other variable that has the right data to use.

Also, it always seems like it takes 2 presses of Alt-S to stop the source telemetry in MSFS.

Already done in some of the sims (FS2020). Need to check better DCS, but I don't think we have rotor there.

Is this specifically DCS? Need to check the values I'm using.

I'm aware of that, solved, but since i am using just one key to connect/disconnect. If you disconnect or connect one source manually and have another connected or disconnected, the behaviour is strange.
Same hapening in outputs.

no, MSFS. and unfortunately it's not all planes, just some of them..

Marvelous Pedro! There is also a way to to limit the max acceleration or deceleration speed? In order to limit the g force, we can therefore estimate the max payload for in base of the motors power

@pmvcda You seem to be at 300% really awesome.

Would like to know if it would be possible:

1-to have choice on advanced/basic user : most would be grayed or lock in basic, need a password to go advanced and modify them

2-limit pitch up and down differently (-25°/20° per example)

3-don't know if it makes sens, but for pitch and roll that we can mix, put a logistic for the sum of 2 ?

More important for me btw is the first one

Thanks !