You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
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.The text was updated successfully, but these errors were encountered: