Ansh — Week 3 Summary

Tasks Completed

Task 1: Camera preset consistency audit.
- Vanilla three.js: reliable camera preset switching and stable target/focus.
- R3F: reliable and predictable with state-driven camera controller.
- Thob: partially reliable. Direct multi-camera Make Default switching was unreliable, but 3-mesh visibility toggling workaround was stable.
Task 2: Scene preset / transform state switching audit.
- Vanilla three.js: reliable state switching, deterministic transforms/visibility, smooth transitions.
- R3F: reliable with clean state isolation and smooth interpolation.
- Thob: reliable with 3 prebuilt meshes + radio visibility toggles, but no transition animation.
Task 3: 3-step guided flow reliability audit.
- Vanilla three.js: reliable sequencing (forward/backward/jump/reset) with smooth camera/object transitions.
- R3F: reliable for repeated multi-step flow with predictable state behavior.
- Thob: reliable for sequencing using same 3-mesh radio-toggle approach, but instant step changes (no smooth transitions).
Task 4: Grouping / parent motion structural audit.
- Vanilla three.js: reliable true group hierarchy and parent-driven inheritance.
- R3F: reliable real hierarchy with predictable parent transform behavior.
- Thob: reliable. Parent -> child -> grandchild nesting worked correctly and inheritance stayed stable.

Structural hierarchy and visibility-based state switching.
Nesting meshes for parent-child-grandchild inheritance is stable.
Radio-button visibility toggling across prebuilt state meshes is repeatable and predictable.

Direct camera preset orchestration by toggling multiple cameras (Make Default) can be unreliable.
It can appear to work initially, then fail after repeated toggles or at certain positions.

1. Missing smooth transition primitives between authored states/steps (camera + transform + visibility blend).
1. No first-class guided-flow/state orchestration model (step bundles with transition settings and reset behavior).
1. Camera preset authoring and multi-camera default switching is not consistently trustworthy.

Add built-in transition controls (duration + easing) for state/step switches triggered by UI controls.

Interaction orchestration model is still workaround-heavy: advanced flows often require visibility swapping of separate meshes instead of native stateful runtime orchestration.

Partial
Why:
- Reliability is good for discrete state switching using prebuilt mesh visibility toggles.
- Structural grouping/hierarchy behavior is strong.
- But advanced storytelling quality is limited because transitions are instant and direct camera preset orchestration is not always reliable.