FlyPT Mover 3.7

tried this and the send values look good just no movement

So bit values. You used

R0.A1.T
That is turns

R0.A1.B
Is bits

R0.A1.P
Is position in mm or º

So it should be:
x 0 <R0.A6.B> 5000 <13>x 1 <R0.A1.B> 5000<13>

Here R0 is the rig key
A1 to A6 is the actuators
T, B or P as above

Ok, don't remember if it really was bits or position...
If position use:
x 0 <R0.A6.P>>> 5000 <13>x 1 <R0.A1.P>>> 5000<13>

The number of > is the number of decimals (minus 1)
If you have <50>>>, it will write 50.00
the number or < is the minimum number of digits before the decimal
For <<<<50>>> you get 0050.00

Yeah I have tried T, B and P but none of them work. Maybe I have something else setup wrong but I cant see anything.

I'm confused.....
I'm using 0.3.6.0 with a special dll that fixed the positioning so OpenKneeBoard also gets moved around correctly (It was wrong in iRacing due to orientation being different/swapped).

The 0.3.7.0 was supposed to have that fixed but since I was already fixed I never upgraded to it. Now there is a 0.3..8.0 version that is supposed to have the order of translations match that of FlyPT (rotation first, lateral second).

Are you saying any of these versions of OXRMC are not doing it correctly today with Mover 3.5.3?

Will there be a fix for 3.5.3? Or is the issue only impacting Mover 3.7? I will try tonight and report back. I'll also post the profile that I'm testing with so you can see what I have.

Also, I have reduced my monitor resolution and use 100% scaling for now so I don't have the issue with the positioning and size of fields/text but let me know if you ever could repro and fix? you may need a 4k monitor to actually see the issue.

x 0 <R0.A6.P>>> 5000 <13>x 1 <R0.A1.P>>> 5000<13>

with this it moves about a 10th of a turn

I'm lost right now, sorry. Have to make some tests...

No problem when i move the sliders it does slightly turn the actuator.

In your old setup in the serial section, the data type is decimal. In your new setup, you are using binary, and Ascii. Could that be your problem?

Hi Craig,
maybe I am completely wrong, but If I remember correctly, the insectatec Odrive firmware was expecting encoder counts ? So if you have set your AMT 102 to 8192 counts per Revolution and you want 400mm travel (10mm ballscrew) you had to send 400/10x8192 = 327680 counts. This are integers and not decimals.
So if I understand the output rules correctly you should write : x 0 <<<<<<R0.A6.P> 5000 <13>x 1 <<<<<<R0.A1.P> 5000<13>
????

Firstly, thank you very much @pmvcda for your work, this is awesome, I can finally play EA WRC!

Question for anyone, have you guys been able to get telemetry for Dirt Rally 2.0? I tried Automobilista 2 and EA WRC and they work fine, but DR2 I can't get telemetry data although I have exactly the same parameters compared to the old Mover that is still working fine.

Any ideas? thanks.

Did you find any fix for this? I have the exact same issue, only if I set the display to 100% then it looks fine, but in my case I use a TV and the display needs to be at 200% so even worse. If I set the percentage to 100% and then open Mover, I can later change it to 200% and it's still fine.

0.3.8.0 with Mover 3.5.3 should be fine

@PeterW , insectatech still exists? It wad

You have to patch DR2, I have a new script to get some extra data.
Use the pen button on the source to apply the patch.
You can also use the joystick to do it.

I will add all the files and instructions latter for when those don't work.

Like @hexpod says.
For the new Mover it will work also, but I had some bugs already corrected for the new release. (almost ready)
For the monitor I'm checking it right now...

Thanks!

No that doesn't do anything either Sure it will be something simple somewhere going to try some more now


I have not seen Insectatech since October 2021

ascii is enabled so I guess it should work

ascii and decimal are the same
Reality is that bytes are converted to their ascii representation.

@SilentChill , could it be a . and , decimal separator problem? How was it showing in the olkd Mover compared to the new one?

Mover 3.7.0.2

Download link in the first post of this thread.

DONT USE THE THANOS OUTPUT
That is a test I made that I left there (forgot to disable). Far from the real thanos output


Worked on scaling problem. Think it's better, but...

Solved bugs in OXRMC (inverted yaw and filters)

Added possibility to specify location of game if not found by Mover

Added WASHL, WASHE and WASHLT filters:

WASHL is a linear wash where you specify the speed it goes back to zero (per sample)
WASHE is an exponential wash where you specify the speed it goes back to zero (per sample)
WASHLT is the same as WASHL, but we set speed in mm/s or º/s​

Update connect/disconnect info in diagram

Added some icons

Solved connect/Disconnect on the menu of the diagram

Added VTOLVR, still WIP (MOD is not available yet, need to check some vars causing crash in the MOD)

Other small bugs everywhere