Renewal RSM files (2.2 and 2.3) feature per-mesh keyframed animations, all of which include an unaccounted float member. Tokei calls this field "data" and writes that they're unused. While I can easily believe that, the values don't seem to be random (i.e., it might not be garbage bytes). So to make sure that these fields are nonsense and can safely be discarded, a few more steps would be in order:
[ ] Aggregate the values (via the existing data mining toolkit) to see if there's a discernible pattern
[ ] Modify the values (zero out, garbage bytes, max/min values) to see how the client reacts to this
[ ] Publish the findings as part of the existing documentation (RSM specification and/or model rendering section)
Renewal RSM files (2.2 and 2.3) feature per-mesh keyframed animations, all of which include an unaccounted
floatmember. Tokei calls this field "data" and writes that they're unused. While I can easily believe that, the values don't seem to be random (i.e., it might not be garbage bytes). So to make sure that these fields are nonsense and can safely be discarded, a few more steps would be in order: