@woosh/meep-engine 3.23.0 → 3.25.0

package/src/shade/renderer/scene/TransformAuthority.js

@@ -1,33 +0,0 @@
-/**
- * Who writes a node's `local_translation` / `local_rotation` / `local_scale` in the scene
- * database's `transforms` table.
- *
- * Both sides can reach those fields — the CPU through {@link GPUSceneContext}, the GPU through the
- * pose accumulator's resolve pass — and neither can tell that the other wrote. Without a stated
- * owner the two race, and the race is not hypothetical: {@link Node3D.updateMatrices} recurses into
- * children, so moving a character's root marks every joint under it as changed, and the CPU would
- * push its own idea of each joint's pose over whatever the animation had just resolved.
- *
- * `global` and `prev_global` are not covered by this — they are GPU-derived for every node, whoever
- * owns the TRS they are composed from.
- *
- * @enum {number}
- */
-export const TransformAuthority = {
-    /**
-     * The CPU owns the TRS. Its scene-graph node is the truth, and changes to it are pushed to the
-     * row as they happen. This is the default, and it is what entity placement wants.
-     */
-    CPU: 0,
-
-    /**
-     * The GPU owns the TRS — animation clips, effects, anything writing through the pose
-     * accumulator. The CPU allocates and seeds the row, then never writes to it again, so the
-     * node's own `transform_local` stops describing it and should not be read as if it did.
-     *
-     * A node under GPU authority still follows a CPU-driven parent: the hierarchy pass composes
-     * `global` from this node's TRS and the parent chain, so the parent moving carries the child
-     * without anyone writing to the child's row.
-     */
-    GPU: 1,
-};