FlyPT Mover 3.7

Thanks for the proposal, but it didnt change the behavior :-/

Well that is a bummer :-(

Sorry for late reply.

Here's how you can set the output strings:

In binary format, bit values are sent with the number of bytes specified for the actuators.
The other values (like mm, º or turns) are sent as a 4 byte float or a 8 byte double.
Using a letter or any other key sends it's ASCII value as a byte.
Example:
<RIG.YAW> is a 4 byte float
<<RIG.YAW> is a 8 byte double
A<RIG.YAW> is the byte 65 for letter A followed by 4 bytes for the float value
You can also send specific values:
<233> is the byte 233
233 is not the byte 233, but 3 bytes for the chars specified: 50, 51, 51
<23464> does not fit in one byte, the byte shown is only the last byte for that value: 168
<<23464> fits in two bytes and shows with two bytes: 91, 168
<<<23464> shows with 3 bytes: 0, 91, 168
Resuming, the number of < used in the variables and values format the output by defining the amount of bytes used.

In ASCII format, you can send invisible chars sending their value:
<27> is the invisible ASCII char ESCAPE
<64> is the visible char @
Visible char can be set directlly
You can also set the minimum amount of digits shown before the decimal dot and the number of decimals shown.
If the variable value is 2.234456 then:
<VARIABLE> shows the variable value as an int: 2
<<<VARIABLE>>> shows the variable value with at least 3 digits before the dot and 2 decimal places: 002.23
<<<VARIABLE> shows the variable value with at least 3 digists and no decimal places: 002
Resuming, the number of < used in the variables set the minimum number of digits shown before the decimal dot. The number of > used (minus one) is the number of decimals shown after the dot.


So for ascii, you can set the amount of digits before and after the decimal separator
The idea is to allow more control over the result.
To get more decimals, use moer > at the end, only one is an integer.

Sorry for this, I should have explained it already, but it's to many things...

@PeterW , please see the above post.

Sorry for late reply...

OK, I did some more testing tonight.

The good:
- Running Mover with NoAudioDevices as a command line parameter works, I have sound.
- Serial Output to Arduino to drive wind works (kinda, see below)
- Motion Compensation works (kinda, see below)

The bad:
1) The serial output to Arduino does not pick up the source data until I open the Direct Source at which point it reads the correct value (0) and starts sending that. Until I open the Source it sends a value (likely from the default value of the slider, which in my case is 100). The same can be seen/experienced with the Belt, another Direct Source in my config. So this is likely a bug in the Source module, not the Output module.

2) Motion Compensation sends data but it's not the correct data. It's correct-ish. When I just start up the rig and connect, the data is too little movement compared to what the rig moves, the only filter I have on the MC output is an EMALP filter. If I change the value type from Double to Float it goes to total garbage but if I swap back to Double, disconnect, reconnect and restart OXRMC then the lateral movements seem to be correct, the angular movements are still too little. I think there is some math conversion problem here. Additionally the output field does not seem to match what I have in 3.5.3 so I know the data is likely not good. Also, the values are moving around even when there is no change in the source, it's all just 100% steady, the values that are on the debug display are constantly changing.

So these are the two major issues that are show stoppers today for me in addition to the other problems I have mentioned before. We really need a bog tracking solution otherwise it's hard to know what you have ACK'd what you fixed, what you're planning on fixing and what you can't repro, and what you don't want to fix.

I'd suggest delaying a new release until these issues are addressed at the very least.

Another bug is that the red/white triangles in the corner are lagging and sometimes don't update unless you hover over them so it's hard to tell whether things are on/off line.

@GTakacs ,

All to be solved
When you meant source, you mean direct?

How many low pass samples are you using for VR?

https://github.com/BuzzteeBear/OpenXR-MotionCompensation/releases/tag/v0.3.8.0-beta

Yes, that is an important correction.
Should make it way better.

I have VR but don't use it due to nauseas.
Been working on VTOLVR and just from testing...
It's a pain to do sources for VR products. Specially VTOLVR, you make the mod, load the game, test and find the directions are wrong. Close, cange mod, reload everything, put VR and find the units must be wrong...
This for all the vars...

@hexpod ,

Do you have IL2 in Steam?

Correct on the Sources it's the Direct source that has issues of not sending correct data whether to a serial by itself (Arduino) or part of the packet (belt for M4S).

I'm doing 150 samples for the filter, same one I use and works correctly in 3.5.3

Not sure 100% but I think it’s a non-steam thing. You can see the path to the exe in the screenshot

@hexpod ,

Please, can you check this:

In the menu, go to Tools:


Select the above menu and see what shows in IL2
If you right click, tehe tex shown can be pasted here.
You can also try to lauch the game by clicking on it.

I detect those 3 launchers. If it's not on the launchers it should be detected also... but something is wrong, not sure what.
Since it's not detecting it, Mover doesn't know the instalation path...


... Yes the Sims4... Arghh, my daughter uses this laptop. I have 99% of the games in portable SSD's (rig->laptop->house)

Do you have steam open?

I opened steam only to double check if I have Il2 in the library (no Il2 there). Normally I use WMR with open composite to bypass SteamVR for all my flying games.

@hexpod

Sorry for being so .....

Can you do this:

First window that pop's ignore, i want the second one (install path)
You have to write IL-2 and press enter

It’s not the Launcher which has a different name ?

... Sorry, can you try with il-2 closed also.