( Note: it is not entirely clear why the NULL entry is required.

Behind that object record, there is 13 zero bytes, which should then match up with the EndOffset. If so, recursively read an object record directly following the last property. To determine whether a nested list entry exists, check if there is bytes left until the EndOffset is reached. Reading a node record up to and including the properties is straightforward. NestedList is the nested list, presence of which is indicated by a NULL– record at the very end.Properties are written sequentially and with no padding. For the format, see section Property Record Format. The only case where this is 0 seems to be the lists top-level. NameLen is the length of the object name, in characters.This is the size required for storing NumProperties properties, which depends on the data type of the properties. PropertyListLen is the length of the property list.A nested list as last element is not counted as property. NumProperties is the number of properties in the value tuple associated with the node.This can be used to easily skip over unknown or not required records. EndOffset is the distance from the beginning of the file to the end of the node record (i.e., Īpplications have to parse the contents of these in order to access FBX geometry.Ī named node record has the following memory layout: Size (Bytes)

The core hierarchical building block (node) of a text-based FBX document is NodeType: SomeProperty0a, SomeProperty0b. Knowledge of the text-based format is relevant for this document, so here is a quick writeup.

Unity export fbx binary or ascii