FlyPT Mover 3.5.3

Hi @pmvcda this def falls under the "Holy Shit Batman " Category .. this is already looking to be awesome , your gonna hear this from a lot of us mate, but this is unbelievable work, and already looking as though is will be very configurable, so should hit the sweet spot no matter what the mechanical 6DOF platform setup you have ....MASSIVE BIG THANKS for the work you put into this and more so for placing it here on this Great Forum .....Man I really do need to get my system running again . im drooling over the possibilities with this option .WOW

can't wait !

@pmvcda, Ive been enjoying Iracing on your old interface for a month now! Just now getting used to it and you go and change it all around!?

Just messing with you, awesome job and congrats on this new endeavor! Im excited to start figuring out how to implement this on my 6dof rig and hope I can pick up right where I left off!

That looks AMAZING! I'm very much looking forward to testing it. =)

Will I be able to set custom upper and lower servo arm limits outside the typical range? My upper limit is about 47° and lower limit is about 101°. This is a limitation of my build and can't be changed so I hope you can support it! <---Video clip you can see my (bad) geometry.

Not in initial releases. Sorry, but I want to make it work with custom rigs. I'm working on that. So... give me some time.

Current state:

Almost ready for first tests...

Some strange names there.... made some replaces to rename some variables and changed labels also. So, I have some names to correct

It just amazes me as to how you can do so much in such little time. I cannot begin to grasp what is possible and or how to use it within the interface. Theres just too much involved and not basic enough for me to understand ..

I can be patient. =)

It looks like this will be the ultimate solution for the kind of tinkering I have been wanting to do!

That's not so much. Could be way faster.
Here the trick is to lay a good foundation that enables you to build everything over it.
With that it's faster to build new features.
That's the reason for FlyPT Mover compared to the previous one.
The old foundation didn't allowed much more.

This might look hard at first look. But I think it's not. The logic repeats in all windows/modules.
What I'm afraid is that we loose what is open. I hope I was able to achieve something understandable.
Some of those modules/windows, you use only once and will never touch again, unless there's some hardware changes.

Just think like this:

All modules receive information
All modules treat that info
All modules send out the treated info to another module

Not all modules receive or send info to all other modules. Usually a kind of module sends data to another kind of module.
The classification used right now is this:



So for example, in the image I posted in the last post, that's something just for testing, unless you want to control two rigs with different settings at the same time.
You can do it, but 99.9% of us are not going to use that feature. That's a consequence of the new foundation. Imagination is the limit (well, almost).

I will be around to help.

EDIT: The diagram is basic. Some info lacking. I will make a better one and post in the start of the thread.

I'm updating the first posts with updated images and new info.
Will be available in the next hours, maximum tomorrow night.

Please don't expect to much... It's a new world. (of confusion)
I had to cut some features for release or I will never make the first release.

looking forward to trying it out

Me too!

FlyPT Mover version 1.0 Beta

Here's the first build.
Go to first post in this thread for download.

Some things better than FlyPT Hexapod Interface, but you will notice that some are not working so good.

Known problems/alerts:
- There's no default setup for now.
- Missing tool tips and help texts.
- Some strange names due to some replacement strings (please report them, I missed many).
- To much modules, and there's no scrollbar to access them in the main window.
- No Limits 2 as some data problems that I need to solve. Seems the transforms are not correct.
- Graphic viewer with some problems. Data is not always saved (selections), graphics could be more clear. Needs more work.
- 3D viewer keeps rig even when you removed the rig, causing a crash if it's used.
- Outputs to serial could report connection problems in a better way.
- Memory cleanup needed.
- Speed optimisation in early stages.
- Bugs everywhere. Please report them.
- Missing some announced features.
- Missing license text. I'm lazy, hate those things
- Bug on rig scale. Solving it right now. New build soon.
- Serial output seems to fail sometimes... I have to be near the rig to test it better.

Edit:
- SimTools connection not working. It's getting a new plugin.

@FlyPT How difficult would it be to use a certain input value (load on aircraft suspension) to turn a pose on and off?

So that when there is weight on the aircraft suspension (on ground) I can have a pose that allows high frequency heave/surge/sway but once I leave the ground that pose turns off.

So in theory just have to be able to do something like the following:

If suspension position > lowest position then pose 2 on
If suspension position =/< lowest position then pose 2 off

This is just a rough example, details likely incorrect but hopefully enough to give you my idea.

Thanks FlyPT, this is great stuff. I'm reading through this thread 100% start to finish right now, halfway down first page.

What is the difference between poses you want for DCS?
I have more than one solution in mind.
Explain me better and I will put it the the new build I'm working on.
That's something I want to solve!

OK, I have it solved.
Give me some minutes, I'm preparing a new build with this included.

And some bugs corrected...

Only when on ground:
High Pass heave for runway bumps etc. (can probably achieve this using suspension pose but not the rest)
High Pass surge for hitting brakes and sudden acceleration like aircraft carrier launch
Surge/pitch tilt coordination with large values for accelerating down the runway (much bigger tilt than in-air)
High Pass sway for steering while taxiing to the runway and takeoff/landing (higher frequency than in-air)
Sway/roll tilt coordination with large values for steering on ground, making turns onto taxiways etc.

All of the above for only on ground. Very undesirable cues in the air so they must turn off when not on the ground. =)

The modular setup of Mover is amazing, so I think best solution would be to just have ground detection (DCS has no ground detection so we must use wheel suspension data to learn when the aircraft is on the ground) able to turn a pose on and off.

If you wish to discuss with me on Discord voice just let me know when. I have a discord I can send invite, or I can join yours if you have one. I will PM you invite to mine.

I now have two poses, one for ground, one for air
Just some minutes...

=O I did not expect anything nearly so fast, you are amazing!

Now I just need to get the needed suspension data out of DCS. I think I am going to attempt to learn how to edit the LUA, wish me luck, this is way over my head and time is very limited but I think I'll try. I have a BFF LUA with DCS ground detection I'll look at, Dirty's DCS LUA with rotational rates, and FlyPT LUA that talks directly to FlyPT Mover. I will try to learn enough to copy and paste some bits. =)

Nevermind that, I see it's already been edited! I'll be testing in just a few minutes.

FlyPT Mover Version 1.1 Beta

New/solved:
- New SimTools plugin, specific for FlyPT Mover (see this post for information).
- Solved scale bug.
- Corrected text errors. If you find any English error, please report.
- New Lua file and extra source for DCS (see this post for information).

Known problems/alerts:
- There's no default setup for now.
- Missing tool tips and help texts.
- To much modules, and there's no scrollbar to access them in the main window.
- No Limits 2 as some data problems that I need to solve. Seems the transforms are not correct.
- Graphic viewer with some problems. Data is not always saved (selections), graphics could be more clear. Needs more work.
- 3D viewer keeps rig even when you removed the rig, causing a crash if it's used.
- Outputs to serial could report connection problems in a better way.
- Memory cleanup needed.
- Speed optimisation in early stages.
- Bugs everywhere. Please report them.
- Missing some announced features.
- Missing license text. I'm lazy, hate those things
- Serial output seems to fail sometimes... I have to be near the rig to test it better.

Download:
In the first post of the thread