fix: fix conversion in key point and keyline 3d #167
Conversation
chrisochoatri
changed the title
There was a problem hiding this comment.
Nice catch, thanks Chris!
Reviewed 1 of 1 files at r1, 1 of 1 files at r2.
Reviewable status: 0 of 2 files reviewed, all discussions resolved
There was a problem hiding this comment.
Reviewed 1 of 1 files at r3.
Reviewable status: all files reviewed (commit messages unreviewed), all discussions resolved (waiting on @chrisochoatri)
There was a problem hiding this comment.
Reviewed 1 of 1 files at r1, 1 of 1 files at r2.
Reviewable status: all files reviewed (commit messages unreviewed), all discussions resolved (waiting on @chrisochoatri)
There was a problem hiding this comment.
Reviewed 1 of 1 files at r3, all commit messages.
Reviewable status:complete! all files reviewed, all discussions resolved (waiting on @chrisochoatri)
Keypoint and keyline 3d were being converted to integers on saving, the proto definition expects floats. This leads to loss of precision on saving.
This change is