Closed benemer closed 1 year ago
Hello @benemer,
Firstly, thank you for finding the typographical error in the helipr file player. It is clear that the type for point.offset_time should be uint32_t, not uint16_t. In reality, the section with the error isn't critical as it is only called once. After that call, the section without the error is always used.
However, I really agree with your suggestion since it can confuse users.
I truly appreciate your input, and please continue to pay attention to our work.
Thank you!
Hey!
Shouldnt' the type for the avia offset_time be uint32_t? This is at least the case just below when reading the serialized data.