I managed to do a packet capture on a parsing error and discovered it's actually the heading field that occasionally switches to a value too large to fit in an int32.
I was able to verify that this version resolves the remaining protobuf error I had.
I managed to do a packet capture on a parsing error and discovered it's actually the heading field that occasionally switches to a value too large to fit in an int32.
I was able to verify that this version resolves the remaining protobuf error I had.