This article's documentation is for anything that uses the Source engine. Click here for more information.

$hierarchy: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
(cleanup and more info)
mNo edit summary
Line 1: Line 1:
This forces a specific bone hierarchy on the model, regardless of what's in the reference file. Normally, the bone hierarchy is generated based on the first occurrence of a parent child relationship. This commands allows you override it with any arbitrary hierarchy.
{{This is a|c0|name=$hierarchy}} It forces a specific bone hierarchy on the model, regardless of what's in the reference file. Normally, the bone hierarchy is generated based on the first occurrence of a parent child relationship. This commands allows you override it with any arbitrary hierarchy.


{{note|The model builder will now allow the animator to change the bone hierarchy between animations, at least in the source. The hierarchy is unified into a single fixed hierarchy for playback, but it's often easier to change this for certain hand animation tasks. The hierarchy is defined by the first instance of the parent->child relationship.}}
{{note|The model builder will now allow the animator to change the bone hierarchy between animations, at least in the source. The hierarchy is unified into a single fixed hierarchy for playback, but it's often easier to change this for certain hand animation tasks. The hierarchy is defined by the first instance of the parent->child relationship.}}

Revision as of 12:15, 22 September 2023

$hierarchy is a c0 available in all Source Source games. It forces a specific bone hierarchy on the model, regardless of what's in the reference file. Normally, the bone hierarchy is generated based on the first occurrence of a parent child relationship. This commands allows you override it with any arbitrary hierarchy.

Note.pngNote:The model builder will now allow the animator to change the bone hierarchy between animations, at least in the source. The hierarchy is unified into a single fixed hierarchy for playback, but it's often easier to change this for certain hand animation tasks. The hierarchy is defined by the first instance of the parent->child relationship.

Syntax

$hierarchy (child bone) (parent bone)