FlyPT Mover

Mixing surge in pitch seems coherent to me.

Once mix checked it takes the surge « in » value and sends it to pitch which has independent filtering and out gain.

It has to send the surge native cue and not the modified (gained or filtered) Dof surge.

The purpose of it is to make them independent.

You see the blue indicator outputting the signal.

I see it does it correctly.

Thanks for clearing that up. I seem to have developed a huge blindspot and didnt see that lowest option.

Apologies for wasting your time on this @pmvcda

Quick question. On my motor/damper setup there is a minimum of minimum of 15 bit output (on a 10 bit setup) before anything moves.

I think i can do it with using 2 DOF. One with higher gain and crop and one with a lower gain. Is there another clever way to boost just the very low forces but still keep the bigger forces the same? Im thinking my method would probably not be that great and interfere/cancel out

I'm getting myself familiar with the mover software. Amazing stuff! However I run into 2 issues:

• a warning next to "set". I can click it, or change drive pose values but no difference. What does it mean/what am I doing wrong?
• I get the warning "out of range/singularity" when I try to use any filter with any value. All actuators however are around zero in both cases, and the angle is definitely above 10 degrees. But the 3D picture is also weird: the red rods are different on 4 actuators.

I read trough all 63 pages to avoid asking stupid/repetitive questions but unfortunately no answers. Help appreciated!

Drive pose is the default rig position.
If you want to set a position for Formula cars, you can put the rig in that position and press set to make it the default position.
Or you can have a more upright position for standard cars.
All movement is made around that default position.
The problem is that if you press set with the rig connected, the rig is going to jump, that red ! is just a warning for that, but badly explained.
Use the set, with the rig disconnected, or be ready for a jump!

There's two warnings, singularity and out of range.
Singularity happens if top platform is on the same plane of actuators.
Out of range if the requested position is not allowed by the actuators range.
The alert works for both, this does not mean it's a singularity problem, should be the out of range.
Yes, this needs work. Sorry.

And I find it really strange that you get out of range with those values. Been testing your measures and it works here.
Can you share the setup please.
Are you trying a recorded setup from the samples?

The basic setup needs more work, it was the first iteration on that one.
Some filters are overlapping, and some ranges can be reduced.
When I get to that again, I promise I will remind your observation.

I'm sorry, I'm a bit lost with the 15/10 bit.
You mean using 15 bits in a 10 bit setup to get some scale on the values?


(EDIT: I'm having so many requests lately, that I get lost with all of them. Try to reach everyone and in reality, don't help anyone... I will try to recover all that in the next week and organize it better.)

Hello everyone.
Just got back on my sim after 2 months break. I never got so much time and used it to renew my musical setup. But yesterday, I tried the new version with Asseto. It worked great, not a single bug for me so far.

My question is about recording a race (asseto, dirt rally) that I could replay, looking at the output data and adjusting the filters. How to do that? I'm a space sim player. I didn't invest much time in race game. So I hope someone tells me how to do that so I do not have to make the effort to look out for it (pure laziness).

It is sad if the telemetry is not the same, but I'll give it a go. Thanks.

Indeed, it may have changed a lot in 4 years. I looked for the AI mode and could not find it.

In Mover, you can record the motion received from the game.
But you are not going to have video.
But that's in my plans...

To record the motion press the red circle button:


You can replay the recorder file in the player source:

ok clear I get it

No worries, I can increase the singularity angle and see it becoming red in case of exceeding that value. So I can see if its an angle problem or out of range problem.

What I did: i opened the program for the first time, add source iracing, add pose from motion, add rig linear hexapod, put in rig dimensions. That's it. No changes at all, it works immediately. So far so good. But the moment I add a filtering on the actuators (in rig screen!) it gives the error on almost all filters, although the system seems to remain more or less functional. Actuator values remain within range, and no red indicators on those values. 3D representation also looks weird. Regardless of rig dimensions this issue remains.

It now do the filtering in the pose screen, since it allows me to filter for all the dof's individually. That works fine so far. Does that seem a logical approach to you @pmvcda ? That also poses the questions (pun not intended why should actuator filtering be used anyway? I'm using the thanos controller which also has some filtering options to reduce jitter and stuff.

See screenshots and config file. Hope this helps you, and us. As far as I'm concerned, no rush.

Hi,
Actuator filtering is there for rigs without filtering.
That's my case.
You can also make it faster in Mover than going to the hardware controller.
It's there for who wants to use it, but remember, actuator filtering doesn't show in the 3D viewer.
Pose filtering shows in the viewer.

I'm going to take a look at your setup.
I had someone else complaining with a similar problem. It seems to me that old setups might be causing the problem in more recent Mover versions. Might be the case of the setups I put in the download.
That would be a strange issue , but possible.
The other cause might be the actuators filters.
Avoid using a filter in the actuator. Use filters in the pose.
Like I said, actuators filters don't show in the rig, so the fact of getting red actuators might be related to some wrong code in the actuators filters.
(it was one of the changes I made lately)

If we get under the singularity angle (minimum angle we allow between platform and actuator), we get the out of range/singularity alarm, but the angle field goes red also.

ok thanks, makes sense. I will avoid actuator filtering. Btw, I didnt ever use a previous version and I didnt base the setup on an example.

This is so freeking awsome! You never cease to impress me pmvcda.

Very good, I also plan to use this software.

No worries, im just glad you are developing this. Its everything i dream of and more so take your time! Consider this a very low priority as its a luxury item i dont really need but would let me get a bit more detail.

What i meant (it was a bit cryptic) is that i have a 10 bit output with 1024 (of which i use 358 - 664 at a 0.300 scale) steps but it takes about 15 steps for my rig to move due to slack in the setup and using large wheel chair motors. So then im wondering if that somehow can be set as a minimum amount of steps to move so i get movement on the small things but still keep the gain the same for larger movements. Essentially its a higher gain for small movements than large.

Edit... by some magic things worked with no changes to the game

Hello, how are you?

I have a 6dof platform, 300mm, and I am testing the FlyPT Mover. Everything is going very well (im learning about filters but I loved it). Im using Xplane 11), but the ground isn't good yet. Landing is so so and the surge acceleration (mix with pitch) is reasonable, but when braking, it has not inclined much (pitch). In SimTools (which I used before), I could put + and - values and I could adjust that.

Some tips?

Thank you!

Mauricio Catelli