When a PLY model has vertex colors, they're typically saved as uchar rather than float properties.
For example, exporting a mesh with vertex colors from Blender will write it with uchar red, green, blue, and alpha properties.
Currently, Yocto is reading colors by casting to float without dividing uchar by 255. So the colors come out wrong.
This patch changes the logic to ensure that when colors are read, it will normalize any integral type to a floating point value. I didn't really find anything in PLY spec that defines the "right" way to normalize the various integral types, so this is just a best guess (that happens to work well for uint8). I can try to simplify this patch if we don't want to do general normalization and just handle uint8.
I created a PLY in Blender to test this, with a sample scene (materials5).
When a PLY model has vertex colors, they're typically saved as uchar rather than float properties. For example, exporting a mesh with vertex colors from Blender will write it with uchar red, green, blue, and alpha properties.
Currently, Yocto is reading colors by casting to float without dividing uchar by 255. So the colors come out wrong.
This patch changes the logic to ensure that when colors are read, it will normalize any integral type to a floating point value. I didn't really find anything in PLY spec that defines the "right" way to normalize the various integral types, so this is just a best guess (that happens to work well for uint8). I can try to simplify this patch if we don't want to do general normalization and just handle uint8.
I created a PLY in Blender to test this, with a sample scene (materials5).
This is what the render looks like before the patch:
And this is after: