-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Blender importer failing to import files that used to work #2016
Comments
Attached is a file that reproduces the issue. |
can/should i check this issue (reproduce and find the bug)? |
@jamesdolan i issued a pullrequest to solve this issue, caused by newly added CustomData support (base cause is somehow strange design: number of vertices (re)set when setting UVs, i commented the belonging part in the CustomData pullrequest). |
Thanks! For reference my loading flags are aiProcessPreset_TargetRealtime_MaxQuality | aiProcess_PreTransformVertices |
When updating to latest master, Blender files that used to load no longer do with error output similar to the following...
...and if I open the file in blender and look at the offending mesh (e.g. 'SomeMeshName') does indeed have verts (44 tris, 84 verts). And if I roll back to an older assimp, the particular mesh in question does get loaded without issue and is visible.
Previously was using this version: https://github.com/assimp/assimp/tree/45892d7fe99c6c35d89f491af43f313e84e1e395
The text was updated successfully, but these errors were encountered: