Please include the OBJ file here…
Tue, Feb 12
Confirmed, checking (caused by rB9ec944bbab7a)...
Fri, Feb 8
@Arjan Pottjewijd (Cuflee) Please open a new report, with all required information (in that case, precise steps and all data (like image files) need to reproduce the issue are mandatory). Resurrecting years old reports is generally a bad idea, code has changed a lot since then (you may reference an older report in a new one, though).
I can confirm the same error on Blender 2.78. I've added some screenshots and a .blend file that is raising this error for me, though it also happens with the startup file.
Thu, Feb 7
The main issue here is the 'blend mode' of the materials set to Alpha Blend, because of their MTL illum set to 4 (which, according to http://paulbourke.net/dataformats/mtl/, enables glass transparency and raytraced reflection). No idea why this is using that model, tbh.
This bug still seems to exist and is really getting in the way of our company pipeline.
I did some digging and seems like blenders vertex normals are exported to point normals
Let's leave this for upstream then:
Wed, Feb 6
Ok so the mesh is fine but the Materials seem to be not reading in properly. That is good to know. I can tell you that the mesh has been tested in multiple applications and the .mtl file is being read in correctly. No scrambled normal maps , no transparent materials etc.. So at least now I know the issue is with the .mtl reader.
Here's what the console shows me on Mac on build 766741b0aa8c
( 0.0001 sec | 0.0001 sec) Importing OBJ '/Users/admin/Downloads/OBJ_EXAMPLE/BODY_OBJ_EXAMPLE.obj'... ( 0.0017 sec | 0.0006 sec) Parsing OBJ file... ( 2.2181 sec | 2.2155 sec) Done, loading materials and images... WARNING, currently unsupported 'tf' filter color option, skipped. WARNING, currently unsupported 'tf' filter color option, skipped. WARNING, currently unsupported 'tf' filter color option, skipped. WARNING, currently unsupported 'tf' filter color option, skipped. WARNING, currently unsupported 'tf' filter color option, skipped. WARNING, currently unsupported 'tf' filter color option, skipped. WARNING, currently unsupported 'tf' filter color option, skipped. ( 2.2389 sec | 2.2363 sec) Done, building geometries (verts:84104 faces:84102 materials: 7 smoothgroups:1) ... ( 3.5119 sec | 3.5093 sec) Done. ( 3.5131 sec | 3.5120 sec) Finished importing: '/Users/admin/Downloads/OBJ_EXAMPLE/BODY_OBJ_EXAMPLE.obj' Progress: 100.00%
I have attached a zip with an OBJ and its textures. Just import it and select options : Don't change Vertex Order and Keep Polygroups.
Select Rendered Display render preview.
On FBX import it brings things in properly if the maps are in the same folder. This is not the case for obj import.
I included an image of the FBX import so you can see what it should look like.
Tue, Feb 5
Uuuh… this should have been updated since a long time already. :(
Fri, Feb 1
@Bastien Montagne (mont29), I know I just mentioned it in case that wasn't supposed to happen when trying to export.
Rule of thumb: never do that. the way FBX handles 'armatures' (aka chains of voids used as joints, basically, with some esoteric undocumented ways to distinguish what is actually part of a rig, from other 'empties' just used to create object hierarchies), you are pretty sure to run into issues with current FBX addon in Blender. This is kind of known limitation/unsupported feature (and we already have a report for that kind of issues, will merge).
In 2.8 I'm getting an assert on export:
BLI_assert failed: blender/source/blender/editors/interface/interface_layout.c:738, ui_item_enum_expand_exec(), at 'but->func == ((void *)0)'
You can compare the datum or the hash value https://developer.blender.org/diffusion/B/history/master/
How do I find the build that includes this fix? As far as I can see the only release so far is still just "Blender 2.80"
Thu, Jan 31
Will mark this as resolved then.
Wed, Jan 30
To see Python errors, just click on the Scripting workspace.
The wavefront importer uses the same code, this is already fixed in rB1ceaca7f646c
Sun, Jan 27
Fri, Jan 25
forgot to add all changes to git before posting the previous diff :/
Thanks! applied rBcaf0c86b45f088a942641980fd10238f80a67f0a
Thu, Jan 24
Many thanks for your continued endurance in looking into this!
Tssst… scaling issue remains, do not close that task you naughty bot!
Here is how Blender FBX importer sees the hierarchy of the FBX file (every increment means 'child of'):
Wed, Jan 23
Also, for what it's worth, Collada has the same basic problem as FBX. From what I can tell, this issue has less to do with the FBX format in particular and more to do with how Blender interprets and deals with hierarchies.
Tue, Jan 22
Since you asked for a smaller file, here you go. It's a 1MB file. It has a mere 4 mesh objects and a paltry 3 bones. That's about as simple as it gets.