FlyPT Mover

WARNING TO ALL!

Found a bug in the shared setups. Seems that when loading, data comes corrupt and some values are missing.
Seems to be stored in the server, but when loading, there's some mess.
This might be the reason some people testing other profiles get some strange behavior.

I looking at it right now

Hi,

Found the bug. Will be solved in next build (already published)

Mover 3.5.1

New release to solve a bunch of bugs...

-Main window position is now stored in the setup.
If any window is outside of the total desktop area (multiple monitors), window is automatically moved to stay inside limits.

-Name of shared setup should have at least 3 chars now to avoid empty names.
-Solved bug with name of shared setup in the save window.
-Changed the default setup description to be shorter.
-Reduced line height of the online setups (mouse hover description shows all text).
-Solved bug when loading the setups that was loosing any info where we had square roots like "Lateral acc. with gravity (m/s2)".
It was a UTF8 problem while reading.
All setups are stored correctlly, but where read wrongly, reverting to default values.

-Corrected bug in the Thanos output that showed the same rig multiple times in the drop down

-DCS: Added angle of attack to the received data.
Please, replace the Lua file in DCS.

-Transducers: Less rsolution to reduce lag. Think it's not noticeable.
-Transducers: Solved bug where sources where not correctlly separated in Air and Ground.

-Directs: Solved bug where sources where not correctlly separated in Air and Ground.

-Elite, GTAV and Squadrons without hooks updated (sorry).
Some setups will be shared to use the custom hook module and access the data.

Other comunicated bugs still WIP, but the online shared bug was a severe one!

Download at: https://www.flyptmover.com/downloads

So sorry @pmvcda to say that my upload issues are not gone with 3.5.1. After confirmation I don't see them in the repository.
For help in debugging I attach the two profiles, also a sample of my description text (any 'forbidden' characters)?
My auto-generated password has 20 characters/numbers.

@pmvcda there's one more thing you may want to know: 3.5.1 exe created a virus warning and was removed from my game system by Win10 native virus defender . However, F-Secure defender on my office system does NOT recognize a threat.

I cannot connect DCS with 3.5.1 in LUA script version 2.9.0 where I can take new LUA script?

It's in the zip file, inside the folder

Works fine for me ─ so great we have now separate poses for ground!
Only thing I noticed: when I record a flight and REPLAY it, ALL data is in column 'Air'. 'Ground' remains empty. However, this only concerns REPLAY!

hmmm, I will look at it

The problem is on the ' used in the description
I have to limit that or ... might have another idea.

I'm sorry. I download .zip, install. Connect 1 second and disconnected again. LUA script replaced. What's wrong?

Give me some time, I will test.
It was working, made something stupid for sure...

Please, try this Lua file:

Never mind, once I knew and could replace the apostrophe, my uploads worked fine! There's actually more forbidden characters, like ° and «». Those don't mess up with the upload, but they add strange additional characters...
I think it was a good idea to limit the height of the entries. But now the only way to read long descriptions is to pull the window wide open.
You probably regret to have built the online repository, because it suffers from all common 'childhood deseases', but in the long run it will be a very usefull tool that nobody wants to miss. THANKS!

@pmvcda, did you find any issues with the No Limits 2 telemetry?

@VirtualObsession : I have just uploaded a 6DoF NL2 profile. I didn't find any issues and it works quite satisfying for me. Maybe you want to have a look at it?

No, but still want to see better something.
It's related to a error that comes from the beginning of Mover. Not sure if I will change that. Need to think of the consequences.
Clue: allowed angles of the pose

That is solved for 4.0

Oh, then we do the same!
Seriously, motion profiling is a bit like coding. Open something you have done some weeks or months ago and you wonder 'Did I do that?' and 'Why did I do it THIS way?'. You know you should comment every line and write a documentation right after you finished ─ but who does? For me as a non-mathematician/technician profiling is a lot of 'trial and error' and when it finally does what I want I should go over it again and streamline it. And fully understand what I have done.

I had the idea of splitting up a pose module with 6 axis into 3 or more modules with only 1 or 2 activated axis ─ in order to give the modules names that describe my intention in the filtering. E.g. «Adding small acceleration movements to the basic position value» or «Handles >6 G values on touchdown».
Can anyone answer me whether such splitting would have a (notable) impact on performance?

It will work.
Worst for setups are graphics and 3d views.

Thanks. I'll test your profile with a recording of telemetry that has strange roll issues. I see you have a lot of spike filtering and that may smooth out those spikes.