We developed our own driver a while ago that passes values for a joystick (via .NET and Wideclient) to offset 3BAA.
This was working fine on Prepar3D V3, but we are just trying to get it running on Prepar3D V4 and seeing some strange things.
The value we pass to the offset is in the range -16384 to +16384
If i use FSUIPC logging to monitor the offset, it shows the exact value we have passed in. So for example, we pass -2000, the logging shows a value of -2000 in 3BAA.
However when assigning the AXIS in FSUIPC, the "IN" values displayed, they are in the range -14,000 to +22000. I am not sure what the logic is for this as I had assumed the IN value would mirror exactly what we pass to the offset (and what displays in the logging screen).
We then see a further problem because the Axis Calibration page maxes out the IN value at 16384 so we cant realise the full range of movement we are passing in... and in fact anything past the centre position of the axis is effectively discarded.
I know the above is probably not a very clear explanation - but this code was working fine on V3 of Prepard3D so it seems to be a change in how these values are being passed to the offset that is causing the problem.
If anyone has any ideas on what might be happening or what we could try I would be very grateful!