I'm trying to use DracoPy to encode point clouds, and send them to a frontend I have, where they are decoded using Draco again (but in typescript, so with Three.js, not DracoPy). I used to do this by writing to temporary files using the draco binaries, reading from the files, and sending over those bytes. This worked, but I'd much prefer to just use DracoPy.
When I encode and decode using DracoPy, it works well. However, when I encode using DracoPy, and then decode using TypeScript, the colors get all messed up. My only working theory is that the Draco versions that DracoPy is incompatible with the one I am using on my frontend, which is believable because the snapshot of Draco that DracoPy points to isn't an exact version. Thus, the submodule should point to: google/draco@bd1e8de, rather than https://github.com/google/draco/commits/befe2d880992e6fdbfd29fe20a3b8664460b92cd.
Note: the specific way in which the colors are screwed up is that they are being interpreted as 0-1 when they are being sent as 0-255.
I'm trying to use DracoPy to encode point clouds, and send them to a frontend I have, where they are decoded using Draco again (but in typescript, so with Three.js, not DracoPy). I used to do this by writing to temporary files using the draco binaries, reading from the files, and sending over those bytes. This worked, but I'd much prefer to just use DracoPy.
When I encode and decode using DracoPy, it works well. However, when I encode using DracoPy, and then decode using TypeScript, the colors get all messed up. My only working theory is that the Draco versions that DracoPy is incompatible with the one I am using on my frontend, which is believable because the snapshot of Draco that DracoPy points to isn't an exact version. Thus, the submodule should point to: google/draco@bd1e8de, rather than https://github.com/google/draco/commits/befe2d880992e6fdbfd29fe20a3b8664460b92cd.
Note: the specific way in which the colors are screwed up is that they are being interpreted as 0-1 when they are being sent as 0-255.