FlyPT Mover 3.7.0.24

Hi ! I would like to chime in. A discord would be amazing. It is absolutely overwhelming/daunting to use FlyPT - mainly because trawling this thread for those of us that are time poor is just scary (I even tried using Claude to try to get it to summarise what I'd need to do for a setup - it came back "47 pages, are you sure you want me to do that?"). FlyPT is definitely a different league in that it's so advanced unlocking what it can do - documentation is critical and in particular how other people are using it. And generally I think you're going to use FlyPT *because* you're doing something advanced with it.

If it was split up into a discord with say: (which is basically how it's been done for SimFeedback, Simhub etc)

new releases
getting started
setup by motion type (eg channels for 3dof/6dof/tl/belt/gseat etc)
various controllers
bug reports
feature requests

I think it would make it much faster, and less dauting to get to the information you want.

The bonus is the more interesting project setups you could just look in those threads to follow along and get inspired etc. *and* as most of the projects/platforms/games have a discord it's all in one place (ie fish where the fishing is..).

Eg I want to try out FlyPt if I can make it work with a Thanos controller for this :



I'm like... eep.. where do I start, who's done the same, how can I solve the problems. If there was a g-seat oriented channel I could just live in there for a bit absorbing info, without seeing (and getting a wandering eye...) for 6DOF setups for instance.

My 2 cents, thanks @pmvcda I'll be trying flypt regardless but it would be amazing.

imagination is the limit

Same thing happened to me, without success.
And if I use the stick as a reference, it works, but only temporarily. After a while, I lose phase with the cockpit, I reset center , and the problem returns.
Let me know if you find a solution, because the only one I can think of right now is to change my VR headset, but that's not one of my priorities.

Let me know if it works !!!! Thanks again

First technical help question..

I got some data out of AC, and I'm trying to get it into a direct output as my actuators for the G-Seat are fairly simple.

I created a direct output, put my inputs to it, can see the test actuator moving in the UI.



I map the output by selecting from the dropdown (DO.A.B) into one of the outputs in the Thanos controller, and no data is getting sent (on #6)
I checked that it was 16bits, selected it from the drop down of available keys and.... nothing.

To verify that Channel 6 was working on the controller, I chose another actuator key from the 3DOF rig defined, and that sends data to #6 and gets the servo moving. (say RO.A4.B)



Looking at the output bits from the direct module, it all looks okay... wether I move the test slider disconnected from the game, or have output from the game, and can see that there's output bits, from the Direct Actuator, I can't see how to pipe that into the actual Thanos string...2
am I missing a magic button/checkbox? Or completely missed something in the direct actuator setup?

Thanks in advance.

[Edit I tried 3.5 mover and I could get the direct output assigned and sending data... ]

its normal "pose from motion" chechbox in the rig module is not activated?

Thanks, no - in this case these are direct outputs so they come straight from the sources not going via Pose.

I can feed them either AC or a Loop. I can see the data getting generated, and can see the direct module working- the output from the module changing with the loop going between 0 and 16bits.

The issue appears to arise on the output string to the Thanos controller
1- The output key seems to have A.B appended to it, not matter what I do. Eg I renamed the module key to GSR and I got GSR.A.B in the Actuator drop down list
2- Whenever I select that actuator - no data is sent in it's place in the string. Infact all 3 digits are just missing (not even 000, just gone) so whenever I select GSR.A.B regardless of what actuator position, no data.
3- I *am* generating data via Loop > Pose From Motion > Rig - that's working fine.


OOO - I just had another play with it.

If I manually change the string and instead of using GSR.A.B (seems to be [directoractuatormodule].a.b) I just put in GSR.B then it starts sending data. I don't know what the significance of the .B is on the end ? Not sure if it's correct data or not.

Seems like there's definitely an issue in selecting direct module output and inserting into the output string.

All of my direct's only get a .b appended when using a standard serial output. So it's somewhere in the Thanos module.

I have confirmed that the transients are only in the rig actuators. Not in my directs.
Should be noted that all 4 directs use the same acceleration data as the rig itself. Lat Long and Surge.