Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add error handling when a model doesn't have any texture coordinates #228

Open
patrikhuber opened this issue Oct 18, 2018 · 2 comments
Open

Comments

@patrikhuber
Copy link
Owner

I've got a report that currently, when a model doesn't have any texture coordinates, eos::render::extract_texture just crashes. We should handle that a bit more gracefully.

@patrikhuber
Copy link
Owner Author

patrikhuber commented Jun 20, 2019

Yes indeed, and another user reported a segfault in #260 when trying to use extract_texture with the BFM, which obviously doesn't have texture coordinates.

@patrikhuber
Copy link
Owner Author

patrikhuber commented Jun 20, 2019

More people trying this and running into this crash/segfaults in #218 and #95.

It is quite clearly documented in the BFM2009 converter script though, and the BFM2017 converter script contains the same note. The part about "Note that eos only supports one uv-coordinate per vertex." is no longer true though, I guess I could remove that.

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

No branches or pull requests

1 participant