Samuli Raivio
@bqqbarbhg.bsky.social
Programmer, mostly graphics, he/him
Recently, single-source file FBX importer: https://ufbx.github.io/
Recently, single-source file FBX importer: https://ufbx.github.io/
Skin deformers are definitely the safest way to go if you need to support arbitrary files.
The skeleton hierarchy _should_ have ufbx_bone attachments in the nodes (ufbx_node.bone), with the root bone having ufbx_bone.is_root set if that helps. FBX being FBX though you may run into surprises :D
The skeleton hierarchy _should_ have ufbx_bone attachments in the nodes (ufbx_node.bone), with the root bone having ufbx_bone.is_root set if that helps. FBX being FBX though you may run into surprises :D
November 1, 2024 at 11:39 PM
Skin deformers are definitely the safest way to go if you need to support arbitrary files.
The skeleton hierarchy _should_ have ufbx_bone attachments in the nodes (ufbx_node.bone), with the root bone having ufbx_bone.is_root set if that helps. FBX being FBX though you may run into surprises :D
The skeleton hierarchy _should_ have ufbx_bone attachments in the nodes (ufbx_node.bone), with the root bone having ufbx_bone.is_root set if that helps. FBX being FBX though you may run into surprises :D
ufbx is structured to be very read-focused so I doubt it itself would help too much (except maybe reading the source for "documentation" on the format).
Writing an exporter should be a lot less involved in general fortunately, since most of ufbx deals with old/strange ways of writing the same data.
Writing an exporter should be a lot less involved in general fortunately, since most of ufbx deals with old/strange ways of writing the same data.
October 24, 2024 at 3:57 PM
ufbx is structured to be very read-focused so I doubt it itself would help too much (except maybe reading the source for "documentation" on the format).
Writing an exporter should be a lot less involved in general fortunately, since most of ufbx deals with old/strange ways of writing the same data.
Writing an exporter should be a lot less involved in general fortunately, since most of ufbx deals with old/strange ways of writing the same data.