FlyPT Mover 3.7.0.17

Compared to 3.7.0.15? or the old one 3.5.x?
From the old Mover it's not compatible right now, I need to do an importer. For 3.7.x versions it should work, but I'm making some changes and there's some bugs I hope to solve in the next release.

I was trying to use files recorded with 3.7.0.15 version. Playing with 3.7.0.15 was perfect but now with 3.7.0.16 and 3.7.0.17 versions doing nothing.

It will work on the next release. Sorry for the problem.
I'm adding video to the recording and it's causing problems everywhere...

Hello, just two questions,

1. I can't move the sliders in the rig module

2. Is it possible to implement another parameter in "Follow pretenden pose even if out of range" over that "Prè follow"? To choose the End-of-stroke damping: sharp/steep deceleration near travel limit

Thank you a lot

I also have a feature request:

Would it be possible to have a choice-box in the "Pose from RPM" window so we can select the source for the RPM value? Currently it is fixed to "Engine RPM" which is perfect for car simulation. But for a helicopter the engine runs at around 50.000 rpm and thats not useful if I want to simulate rotor vibrations (usually 400 to 600 rpm).

A filter/operation field would be even better than a simple engine vs. propeller selection. This way I could experiment with my own variables or formulas.

Hi,
The sliders are already solved for the next release,
For #2, please explain it better, but changing pré follow should have the effect you want.

Yes it's possible, that's the reason to have propeller rpm. It's missing on the UI.
It would allow the use of both at the same time.
And I will add a filter/operation also.

I’d like to be able to choose the point at which the deceleration curve begins, so that I can control how sharp the deceleration is and save actuator stroke at the cost of a less comfortable slowdown.

I wouldn't want the entire actuator stroke to be modified—only the final portion. I understand this is a mathematical approximation, but something similar would still be useful.

Hello, while building my 2DOF platform, I encountered a problem with my ETs2, which I used to test the motors and connected. The FlyPT_ETS2_AMTS_MMF.dll file stopped working after upgrading to the new version. Everything worked fine with it before. Now, the connection indicator isn't even lit.

There's a new dll.
In the source window, you have a button to patch ets (pen icon) at the top right. This is going to install the updated dll.
Before. Not sure, but i think you can keep both dll, they use different memory files.

Sorry for my English, I'm using a translator. Yes, I did as you said, thank you. But it still doesn't work, and I don't even know what it's related to.

I also don’t know how to respond to your message specifically, so I’m sending it separately.

A sort of value like "Amount of the range used for infinite approach to the limit (0 to 1)" in the Logistic 3 function — not exactly the same, because this is not a curve but a ramp

Do it again to put the new patch.