Steering Wheel throttled reaction at 100 ms latency

Hey, and thanks for VirtualHere and this support forum! I have been reading through quite some threads, and appreciate the insights!

Is there a max. latency for steering wheels, like for storage devices? On a 35 ms latency machine it reacts quickly.

I'm have around 100 ms latency, and the wheel (according to the cockpit animation) reacts choppy. It's a "consistent choppiness", as if communication was throttled, or as if every new update was waiting for the previous packets to report back, or so. – I wouldn't mind the latency. Is this a USB limitation maybe?

I have set high process priority. I tried to lower the compression threshold to see if smaller packets make it smoother.

The other thing I'm try to check is if there is a problem with the report rate from the wheel. But I don't have luck finding something so far.

PS: Why 100 ms? From Europe to NY. Relaxed driving, video is smooth 60 FPS. i wouldn't notice the latency otherwise. Why not connect to a machine in Europe? Because unfortunately there is packet loss at some hop (sigh).

#2

The USB spec has a max latency of 50ms however most devices are ok with higher latency. However wheels **are** sensitive, so the latency must be < 30ms or so and very consistent. In the virtualhere client right click USB Hubs->About->Statistics and it will give you a graph of the latency

" or as if every new update was waiting for the previous packets to report back," yes that is exactly how the USB protocol works. It needs a response before it can send the next packet. Its a pain for high latency connections in sensitive devices, but there is no way around it at the USB protocol level. This is usually solved at a higher level protocol in the stack

#3

Thanks for the explanation!

I'm really curious what the future holds for cloud gaming. Getting it all to work is quite some work, but VirtualHere helps a great deal!

I'll switch to another service provider with slightly higher charges, but consistently low latency.

Thanks again!