Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Adding support to meshes without object specification and per vertex color

See original GitHub issue

I’m dealing with a couple of obj file which are not being being properly parsed by PyWaveFront.

The traits are:

vertex information is provided without providing an object name per the o keyword, i.e. it’s a single nameless object.
they have per vertex color (see last two sentences of the “spec” entry).

I’m gonna extend the library to support these for my use case. Should I submit them here as well? I believe they’re both still within the specification.

Issue Analytics

State:
Created 6 years ago
Comments:36 (28 by maintainers)

Top GitHub Comments

1reaction

greenmosscommented, May 31, 2018

@SergioRAgostinho yes they are triggered automatically, but only on commits to master. I need to reconfigure it to test PRs too, and post the results. I’m guessing it won’t take long to do, I just have to actually “do” it 😄

1reaction

greenmosscommented, May 31, 2018

Thanks for the PRs! I feel smarter by proximity to the comments here 😉

I merged #31 and #33 from @einarf.

I don’t have the “official” circleci status up or documented yet, but note that I got some new failures:

https://circleci.com/gh/greenmoss/PyWavefront/21

Compare to previous iteration, which has only a failed gl call:

https://circleci.com/gh/greenmoss/PyWavefront/20