FreeHK Graphs
[
]
[
]
An LMT Animation consists of a list of entries, each with non-repeating IDs. Each LMT entry is made up of an LMT Action and a TIML Data Node. It's possible to set the entry id to -1 for it to be autocalculated but in most cases this isn't recommended, the animation ID determines what it's used for. Keep in mind that an LMT File node Entry Count is the number of entries including empty entries. Setting it to -1 will make it autocalculate the entry count, this is not recommended either, if the game calls an LMT file with an entry ID beyond it's range it will crash.
The tools in the node window affect all children nodes of the currently selected nodes on the currently open tree (children are nodes that connect to the left). This is useful for the rare cases one has multiple trees or multiple node setups open at the same time, or to only apply an operator to a number of selectetd actions.
[
]
A TIML Animation consists of a list of entries, each with non-repeating IDs. Each TIML entry is made up of a single TIML Data entry. A TIML Data entry consists of multiple TIML Action Entries which correspond to Blender Actions with an asterisk type of TIML Action.
[
]
EFX Nodes are somewhat more complicated. An efx has a timeline entry for each main attribute. Because of the complexity of EFX files the process this entries are found might have some shortcomings. EFX Files consist of a list of entries, each with non-repeating ID. The entry's id is the index of the main attribute it modifies. Each EFX Entry consists of multiple TIML Data entries.
JSON nodes allow exporting any FreeHK Node in JSON format. This are useful for debugging purposes and for legacy tools which allow manually injecting buffers into animation files. This nodes are considered pernicious to workflows however and their use is HIGHLY DISUADED. JSON Nodes should not serve any use for the regular user. Exporting them back is not feasible either.
As of Release version this Nodes were deprecated and removed.