FlyPT Mover 3.5.3

@Flymen , found a problem on yaw. It's an easy fix.

I have 4 output cards. Did some troubleshooting and think its related to VoiceMeeter or an issue that has made with windows. On my latest uninstall it completely broke my audio (no sound at all) so i did a sys restore. Not getting any error messages after that.

Not sure how this is related but serial completes its connection to the working ones where it just said starting and nothing before but still no joy on the others. The working is on port 4 and non working 14-15. Tried changing the port from 15 to 2 on the identical but no change. Edit, port 2 works after restarting the computer. Gonna do some more testing on ports and get back to you

Some quick testing as i need to pop out. Im quite sure double digit com ports does not work for serial now. changed 15 to 2 restarted, connected. Changed to 10 restarted, wont connect, changed to 9, connected.

I'm testing with the old code on Win10 latest update.
Mover locks when sending data to Arduino.
Works with Thanos, ESP32, no problems.
Arduino Uno , Due and Mega locks everything.

...

ok ( It's easy fix) with Simtool , But now with a new version 3.3 I want to follow with source ; Condor 2 ( UDP) .
I don't know what I do bad , but i no receive signal from Condor2.
I will see the message ( UDP data) that you have send at Pierre . ) @Pierre Lalancette
thanks

@Flymen what is your <CondorFolder>\settings\UDP.ini content?

Mover 3.3.1 ALPHA

Download in the first post.

-Updated the serial.
Should be working now for all Arduinos. At least the ones I have: DUO MEGA UNO
Also tested on Thanos and ESP32.
Relative to serial, using low calculation times is going to make the buffer big if the serial speed is low.
It will make memory usage increase like hell.
In my Arduino Uno, it's possible to get 1ms updates with write and read @115200 baud rate.
Certainly it depends on the amount of date. But keep this in mind.

-Corrected some small bugs

-Added poses to the outputs. Values are sent has doubles.
Using values from poses is different from values of the rig.
They are not cropped to the rig limits and not transformed by rig filters.
So to control a rig just with that , it's now possible, but the values are doubles (8 bytes).
Might add a key output with optional bit output.

-Corrected small bug in Condor. Yaw should now behave has it should.
To use Condor, we have to edit the config file:

Go to the installation folder of condor 2 and enter the setting folder.

Edit the UDP.ini to match the following:

Code:

[General]
Enabled=1

[Connection]
Host=127.0.0.1
Port=55278

[Misc]
SendIntervalMs=1
ExtendedData=1
ExtendedData1=1
LogToFile=1

@pmvcda In the UDP.ini [Connection] section isnt it better to use 127.0.0.1 (localhost) for the Host ?

Yes, you are right
Just made a copy of what I have...
I'm correcting the IP

Does this refer to the "Bit Output" field we have in the RIG modules? Unfortunately my platform requests that it is set to 16. With any other value the output string is completely ignored. So using the new POSE input in the OUTPUT module my platform remains silent.
However I noticed one other thing: When I move the 3 translational sliders in "POSE FROM MOTION" the values in the OUTPUT module change, but with the sliders of the 3 rotational axis, nothing happens.
Sorry for bothering you!

Anyone have issues with FLYPT just locking up? It becomes unresponsive, you can't click on any of the windows, not even to shut it down. They're just frozen on screen. Have to shut it down through the taskbar. Sucks if i didn't save a tune, as I have to do everything over again. Just tried the Alpha release and it also did it.

Just played Dirt Rally with 3.3.1. No issue so far.

Hi Pierre. Can you share your dirt rally setup with me? Having a really hard time getting it to work properly. I have a sfx-100 setup. What do you have?

The transducer module is the cause.
Even if you don't have any open
Will try to solve it today.

I will add it to the poses. Right now, it's just a double value

Sure. Here it is. I have a 6 DOF. I made a video yesterday night of my bad driving. I tried to do other videos before with the view of the game and Mover information, but we only see the top of the cockpit and it's at 5 fps. So, only my rig and my bad driving.

You have to push for it! It's Rally.
An old video I have:
The setup was wrong at the beginning, near half of the video I change it.

I must admit. You do push those actuators to their limits.
Impressive.

Aerofly FS2 connected but no data receive. What's wrong?

OH,

Forgot to attach the dll.
I need to update the manual.

Put the dll in the folder:
C:\Users\YOUR USERNAME\Documents\Aerofly FS 2\external_dll