FlyPT Mover

You need to copy the dll included in the download, inside the sources files folders.
The go to this game folder:

Create the folder plugins if the folder does not exist
And copy the file FlyPT_ETS2_AMTS_MMF.dll inside that plugins folder. Remember, this works only on 64 bits version of ETS2 (who uses the 32bit on those days...)

Don't know how I missed this source in the manual...

Where is the link for download?

Thank you

In the first post of this thread.
Or here: https://drive.google.com/open?id=1BUHXTpmRG-_RPOt8v7n8jOP4Auvmz49Q

Open the zip, inside you have a folder with files needed for some sources.
I'm sending 2.9.9, because latest version has some problems in outputs to serial.

Hi ,
Bug Report !

version 2.9.9 work well again !!!
Version 3.3.3 . Today after 1h playing with Condor2 , the control : Keyboard , Joystick freeze . Before that everything was ok ! ( I don't know if this bug have a relation with the program )

A few minuts later , switch for Version 3.3.4 and all outputs serials don't want connect !! ( back with 2.9.9 = Work good again ! ).
Thanks !

Yes, 3.3.4 is broken. Already solved for next version

FlyPT Mover 3.3.5 ALPHA

Go to first post to download it or use the menu in previous version.

-Hopefully, corrected some bugs on the Thanos output.
-Added some images and updated the 2 x traction loss rig (sfx100 type).
It's a 6DOF rig.
Still WIP, but calculations seem correct now:



Attention, all movement was thought for motion cueing.
So if you have some yaw, introducing sway generates some surge to compensate and create real sway.
In my opinion, 7 actuators to get limited motion on a 6dof, doesn't seem the ideal. But it has the advantage of space... Maybe.

Corrected some other bugs.

Made some changes in the transducers to solve crashes in some PC's (not tested).

Other WIP, not exposed yet.



EDIT:

Did not forget other requests. Really sorry for not achieving to include them yet.
-Other rigs
-Some small features
-Some sources, like Falcon BMS or VTOLVR <--------
I'm working on them all!

Thanks for this New version.
I will try and tell you if my motors are moving with this one.

And don't worry, at least from my point of view i could not imagine how i could be disapointed from some bugs or missing features/rigs.... I mean... You're doing this on your free time and software is free so...

thank you, it works perfectly

Hi ,
Bug Report V3.3.5 .
After 1 h with Condor2 it seem be good, except no wind !!( simple direct don't work ) and with V 2.9.9 it's ok
I Had somes littles jump( skip motor) sometime in my game that normaly I don't have before . But I must see that with other game !

Thanks !

Yes, @hannibal has the same problem with the direct.
Try to change the key to <BWind>.
I was making some test's and might have left that one behind. Will try to check it later.

i will test tonight!! thanks @pmvcda

Multi directs are broken. last working 3.3.

3.4 3.5 no movement

Hi !
Serial communication seems OK now with 3.3.5 so thanks for the update !

Tell me if I understand correctly : there is no way to setup that surge is sent to motor 1, sway to motor 2 etc... This is deduced from the rig you chose, am I right ?

Other thing : i don't understand in the rig module what are the top names like PPsway, PPsurge and so on... What can we do with those names ? What's the impact if we change them ?

Sorry for the beginer questions but i couldn't find the information in the first post or pdf files.

Chears,
Kevin

Those are keys, that you use later on the outputs to send the values to the hardware or other applications.
The values you mention in the rigs, are the pose values of the rig. Sway, surge, roll....
They are used for VR motion compensation.
You can rename them, because they need to be unique to be identified on the outputs.
Imagine you have 2 rigs (yes, it's possible), how would you distinguish the pose of each one?
I could make it automatic, but then it would be some chars and numbers making strange names.

This shows that Mover thinks a bit different to other softwares.
All calculations are made to calculate a pose (remember, sway, surge, heave, roll, ....)
When you define the rig, Mover calculates the actuators positions to achieve the desired pose.
That's why I have the values for motion compensation and other softwares don't.

Other softwares do it in the opposite way, you estimate how much of a value (%) you assign to one actuator.
You go by trial and error until you feel it good.
Mover tries to use the classical motion cueing algorithm to do it (search for the term in the web), and that works all around the pose.

It's different philosophies. Mover seems more complicated, but when you understand it, it seems natural to do it that way (well, for me).

But, in Mover you can control actuators the same way we do in other softwares.
That's the directs. A multi direct, allows you to assign more than one value to control one actuator.
You can add how many actuators you want. Just give them diferent key values to identify them in the outputs.
In Mover, the actuators can be rotating actuators, fans, leds, linear actuators, an rc servo moving a tachometer needle, whatever you want.

Going back a bit, Mover allows you to control two or more rigs running different games.
If the PC has enough power, it's possible to use 1 Mover to control a full room of rigs with different games.

Thank you for the clear answer.
I'll try to take this into account to make it match my rig (I still need some processing to make my brain working the same way Mover does )

YOU'RE SIMPLY THE BEST!
And thanks for all other explanations, too! Always VERY interesting to learn more.

I confirm that FlyPT is the only program for platforms where motion compensation works in virtual reality.

Hi @pmvcda I have two rigs, one is my 6DoF using 2.9.9 (fantastic) I have not transferred it over to Alpha.

I was very excited to be able to transfer my 2DoF over to alpha and start using Mover with it though.

But, I think you are being too literal with your 2DoF rig in the software. While I have two motors I should still be able to simulate more forces than just roll and pitch. With 3.3.5 I can only simulate roll and pitch as the other forces are greyed out and pose from motion gives no reaction testing anything but Roll and Pitch. Tilt forward and back (with rigs using a center pivot point) is usually used for roll, heave, and surge. While tilt side to side is used to simulate roll and sway. I know that these are not real DoF movements but we should still be able to simulate them as we have been in other software.

I know that you have a deeper understanding of this than I do and I apologize if it seems like I am patronizing you. That is not my intent at all.

This is the same issue that @articho is running into, regardless of how his motor setup differs from mine (mine is traditional two in the back connected to the top sides of the chair.

Again, I apologize if this is just something that I am not understanding and perhaps I am just not finding how to turn on the sway, heave, and surge forces.

You can still use the individual DOF assignments zo translate other poses. This way I have assigned pitch rate as well as surge to the pitch pose And roll rate as well as sway to the roll pose for my flight Sim.

@Avee , can you post screnshots to show what you mean? Thanks