Build the moving parts of a shot's props into the scene a host assembled.
A prop's articulation is data everywhere else in the pipeline: forgeProp
gates it, sceneToNodes lowers it under the placement, and the performance
boundary bounds a clip that drives it. On screen it was nothing at all: the
viewer built one model object per scene node and added it to that node's
group, so a hinge existed in the artifact and had no object to turn. A shot
could therefore carry a validated, ROM-checked swing that rendered a door
standing still, which is the silent drop this package refuses everywhere
else.
Two things make the joint real, and they are separate:
The frame. Each declared joint becomes a THREE.Object3D at its own
local transform, parented to its declared parent joint or, for a root
joint, to the placement group the host already built. Its name is
placementChildNode's, the engine's own lowering law, so the object a
clip channel names is found by the same string the artifact was gated
against rather than by a second spelling of the prefix.
The part. A joint that names a mesh takes that part of the prop's model
out of the model root and carries it, so turning the joint turns something
visible. The part does not move when it changes hands: its authored
transform stays MODEL-local, which is the frame propOccupancyBounds
measures the prop's volume in and every containment, bearing and clearance
judgment is made against. A leaf hung on a hinge therefore stands exactly
where the record says it stands, and only what carries it changes.
Anything that cannot resolve throws rather than being skipped, the rule
buildScene states for an unresolvable node: a silently unparented leaf
renders frozen at its model's origin while every other part of the frame
looks right, and nothing downstream would report it.
A prop drawing an imported appearance has no addressable parts (see
createImportedModelObject), so a joint of one may name no mesh; its
frame is still built and still turns whatever it holds.
What this does NOT do is run a prop profile's drivers. A profile's limits and
drivers are resolved by resolveFrame, which is the engine's frame solver
rather than the viewer's, so a handle declared to mirror its hinge is honored
where the shot is gated and stands still where the shot is drawn. Only the
channels a clip carries move here, exactly as applyObjectMotions
states for every other object it drives.
Build the moving parts of a shot's props into the scene a host assembled.
A prop's articulation is data everywhere else in the pipeline:
forgePropgates it,sceneToNodeslowers it under the placement, and the performance boundary bounds a clip that drives it. On screen it was nothing at all: the viewer built one model object per scene node and added it to that node's group, so a hinge existed in the artifact and had no object to turn. A shot could therefore carry a validated, ROM-checked swing that rendered a door standing still, which is the silent drop this package refuses everywhere else.Two things make the joint real, and they are separate:
THREE.Object3Dat its own local transform, parented to its declared parent joint or, for a root joint, to the placement group the host already built. Its name is placementChildNode's, the engine's own lowering law, so the object a clip channel names is found by the same string the artifact was gated against rather than by a second spelling of the prefix.meshtakes that part of the prop's model out of the model root and carries it, so turning the joint turns something visible. The part does not move when it changes hands: its authored transform stays MODEL-local, which is the framepropOccupancyBoundsmeasures the prop's volume in and every containment, bearing and clearance judgment is made against. A leaf hung on a hinge therefore stands exactly where the record says it stands, and only what carries it changes.Anything that cannot resolve throws rather than being skipped, the rule buildScene states for an unresolvable node: a silently unparented leaf renders frozen at its model's origin while every other part of the frame looks right, and nothing downstream would report it.
A prop drawing an imported appearance has no addressable parts (see createImportedModelObject), so a joint of one may name no
mesh; its frame is still built and still turns whatever it holds.What this does NOT do is run a prop profile's drivers. A profile's limits and drivers are resolved by
resolveFrame, which is the engine's frame solver rather than the viewer's, so a handle declared to mirror its hinge is honored where the shot is gated and stands still where the shot is drawn. Only the channels a clip carries move here, exactly as applyObjectMotions states for every other object it drives.