There are known issues with using dynamic enum properties. I would strongly advise against using them to display any data that comes from Blender itself (so only use them to display dynamic data…
Again, I cannot reproduce this issue, I see no rotation difference in the head bone in Unity between Male_test_hair.fbx
and importing Male_test_hair.fbx
into Blender with the default settings…
I cannot reproduce the issue in Blender 3.4.0 or newer versions.
Left is the for_issue.blend
and right is the Male_test_hair.fbx
imported with the default import settings:
![image](/attachm…
The error I get when exporting was fixed in Blender 4.1: 0b19f1f4a0
Traceback (most recent call last):
…
The affected .fbx would be needed to determine if/where there is an issue here.
While Force Connect Children being enabled in the FBX Import settings would move the bone tails into a chain…
This is a known issue. When importing bones and the tail of a parent bone is in the same place as the head of a child bone, that child bone is set as Connected to the parent bone. Currently, there…
A note that setting numpy array of numpy np.int32 does work without errors though (
C.object['np_data'] = np.array([3,4,5])
), error occurs only when np.int32 are in default python list.
The…
Similar error to #104885 but I'm unsure if they're the same issue since this one is complaining about KeyError: None
.
I think the issue here is that there is a bone (LimbNode
) called root
…
TypeError: object of type 'numpy.int32' has no len()
assigning ID's custom attribute
Looks like a duplicate of #117656
The batch_mode
and use_batch_own_dir
properties drawn in export_main()
should also only be drawn when is_file_browser
because the new code in export_fbx_bin.py
is only run when batch_mode == 'OFF'
(the default value).
Hmm, how did you arrive in this state? If you link in a Collection from foo.blend which has an exporter set you shouldn't see anything in the UI as it's not intended to be exportable in the…
Other than a note about library linked Collections where I don't know if changes are needed, looks good to me.
Might want to consider whether performing a Collection export from a Collection linked from another file should be supported because a linked Collection can have the same name as a Collection local to the current file (or presumably another Collection linked from another different file).
Oops, didn't realise the review was still pending and not actually sent.
Now that self
is an Operator
rather than a Panel
, the operator
variable can be replaced with using self
.