V2 Remote Protocol Broken
I'd recently discovered the V2 remote protocol was a bit broken. I suspect it's due to individual datagram types being sent as separate messages, resulting in up to 5 different messages being sent in a single cycle. The extra messages seem to be having an impact on latency and are inducing more jitter, rendering the protocol completely useless.
I'm creating the ticket merely to make people aware that the protocol is broken and that they should stick to V1 instead. I'll need more relevant test cases in the future to benchmark with, but that will require a bit more effort to make sure it correctly replicates the data loads we are expecting.