Skip to content

Conversation

HaruoOgawa
Copy link

No description provided.

Copy link

google-cla bot commented Sep 4, 2025

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@ondys
Copy link
Collaborator

ondys commented Sep 4, 2025

while adding texcoord support to ply decoding would be a nice feature to have, I'm not sure if the code in this PR would actually work for most cases. It would certainly not work for texture coordinates encoded with our PlyEncoder which would be probably the main requirement.
The most common way to store texcoord in ply is by using an face element list property, something like:

element face numFaces
...
property list uint8 float texcoord

Is there any software that produces per-vertex texcoords with texture_u and texture_v properties as proposed in this PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants