Officially supported add-ons which come enabled by default in Blender.
Fri, Oct 16
Is there any update on this issue guys.
Thu, Oct 15
hi thanks for the reply, in this window if i select a directory and save de preference when i restart blender my selection
sorry my inglish is not so good
Not sure I understand correctly:
Wed, Oct 14
Tue, Oct 13
don`t understand Blender developers that import FBX camera is not working and no fixing this oldest BUG. I can`t import camera from other software in Blender with correct rotations and we don`t use blender precisely because of this problem.
This FBX uses bitflags based smoothing of polygons (aka poly smooth groups), support for this is not really implemented (we just use it as a boolean, so all different smooth groups get mixed together). This i a known TODO, not a bug.
Thanks for your help on this guys.
There is a prop definition in that FBX called babylonTransparencyMode with possible Values ['Opaque', 'Cutoff', 'Blend']
Now the actual value on Material("seatbeltad_env_mat1") is -1, so what should the code do? It can only be 0 ('Opaque'), 1('Cutoff') or 2('Blend')...
OK, glad you've found a solution.
On the blender side, this remains a Known Issue for now, will merge this report with T45176: FBX import - mismatch in camera rotation.
If you think this is a different issue, please provide an example .fbx file with exact import/export settings (we can repopen in the case this turns out to be different from T45176)
this One, my friend test it use my fbx data,it work perfect. and also it can read light type correctly, defaul fbx importer will read area light to point light,
I bought it,and use it to import my huge Scene. its very very slow!!!
I found better fbx importer plugin can solve this problem very perfect
Mon, Oct 12
@lee (lee_sfs) The stack trace shows a different error. Please create a new bug report through Help > Report a Bug in Blender and attach the minimal example fbx file that causes this issue on import.
I am also getting this error.
Last week I could import the same files.
When I export the same geometry from 3ds max, I get this error too.
Well, without having access to that FBX file, I am afraid this could be a duplicate of T45176: FBX import - mismatch in camera rotation -- a long standing issue unfortunately...
It looks like we're looking at multiple issues overlapped on top of each other. There are no GPU-related Python API changes mentioned in the 2.91 release notes, so I'll assume this is an issue with Blender and not with the add-on.
I have the same issue. On Blender 2.90 the add-on works fine and takes UI size into account. On current master (rB06c6fb8b93a83ddd0) I get the same result as above: thumbnails are gone, font is too small, and the font in the bottom-right corner is messed up.
Sun, Oct 11
No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.
Thu, Oct 8
As discussed in the bug report, exporter should be fixed.
so maybe this update could be a patch about compatibility :)
wait, I know what happen now...
my obj file hide the vt 0.0, 0.0
Shouldn't the exporter fix it? Does the spec allow for (any) index to be greater than total coordinates written ?
Tue, Oct 6
@michael campbell (3di) Please add the requested information.
According to my observations, the camera is incorrectly imported only from fbx created in Maya. They need to be completely inverted, this is not solved by choosing the correct axis.
Maybe just let people choose an inverted camera when importing? 9eddf664d68a