Verify FFB sample rate at 400Hz

[coasting-nc]

Verify this issue and fix it if confirmed:
"a significantly reduced sample rate (100Hz FFB rather than 400Hz coming from the game)"

Is the app actually using or outputting a sample rate at 100Hz FFB rather than 400Hz?
Is there anything in the app code that causes the FFB sample rate at 100Hz FFB rather than 400Hz?

Also, for troubleshooting, can we check the FFB signals (from various channels) that we get from the game, check that we are getting effectively a sample rate at 400Hz (eg. verify value changing 400 times each second), and output a warning in the console if we detect a sample rate lower than 400Hz?

[coasting-nc]

"it attempts to read steering torque which only ticks at 100Hz. It does not use the native 400Hz stream "

[coasting-nc]

Verify we are using the correct stream or channel for steering torque. Verify the tick rate of all the steering torque channels, monitoring them and printing warnings on console.

[coasting-nc]

Verify: Discovered that LMU provides a native 400Hz torque stream via generic.FFBTorque in shared memory, whereas the standard mSteeringShaftTorque in TelemInfoV01 often ticks at 100Hz.

Verify if there are other channels in generic. or outside of TelemInfoV01 that we should use.

[coasting-nc]

See the newer version in the post below.

[coasting-nc]

Updated preview build which logs more info about the sample rate of more telemetry channels>
lmuffb.0.7.50-preview.zip