anshk/builder-research
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
builder-research/Week-3/Task-4/builder/BuilderNotes.md

4.3 KiB
Raw Permalink Blame History

Builder Notes (Thob) — Task 4: Parent-Child Group Motion

Thob Observations from Task Notes

  • Possible: Partial
  • Implementation used: Mesh-inside-mesh (parent with children offsets), parent rotation/motion, and Perspective Camera setup.
  • What worked as expected:
    • Parent-child hierarchy setup is straightforward.
    • Rotating the parent makes children inherit rotation while keeping offset distance.
    • Basic grouped motion behavior is achievable visually.
  • Main limitation observed:
    • Perspective Camera rotation appears unreliable: objects disappear regardless of rotation axis changes.
    • Because camera rotation is unstable, full parity with the planned step-guided camera behavior is blocked.
    • Multi-step orchestration remains harder to validate when preview state is unstable.
  • Builder flow used:
    1. Create parent mesh/group container.
    2. Add child meshes with local offsets.
    3. Rotate/move parent to verify inheritance.
    4. Configure Perspective Camera and test camera orientation adjustments.
    5. Validate whether grouped motion plus camera framing can be repeated reliably.
  • Complexity: Easy for hierarchy behavior, Medium for complete camera-guided flow due runtime issues.
  • Main limitation signals: Runtime + Editor UX + Unknown investigation needed.
  • Workaround status: Partial workaround only (keep parent-driven motion, avoid direct camera rotation, prefer camera position/look target adjustments).

Console Warnings/Errors Seen (Deduplicated) and Probable Meaning

warn: Permissions-Policy header: Unrecognized feature: 'browsing-topics'

  • Type: Browser/header compatibility warning.
  • Probable meaning: Response includes a policy directive unsupported by current browser/runtime.
  • Impact: Usually low for core feature behavior; mainly environment-level noise.

error: GET https://builder.thob.studio/builder/<id> 404 (Not Found)

  • Type: Network/resource error.
  • Probable meaning: Builder project/resource URL is stale, missing, or inaccessible in the current session.
  • Impact: High for workflow continuity; can interrupt loading and testing stability.

warn: Unchecked runtime.lastError: The message port closed before a response was received

  • Type: Browser runtime/extension messaging warning.
  • Probable meaning: Background/bridge message channel closed before callback completion.
  • Impact: Usually non-fatal for scene logic, but adds debugging noise.

warn: No HydrateFallback element provided to render during initial hydration

  • Type: Hydration/lifecycle warning.
  • Probable meaning: Hydration path expects a fallback UI but none is configured.
  • Impact: Can cause unstable initial render state in editor/preview panels.

warn: Found both blacklist and siteRules — using siteRules

  • Type: Configuration precedence warning.
  • Probable meaning: Two rule sources are present, runtime picks one (siteRules).
  • Impact: Generally non-blocking, but indicates overlapping configuration surfaces.

warn: undefined is changing from uncontrolled to controlled and RadioGroup is changing from uncontrolled to controlled

  • Type: React state-management warning.
  • Probable meaning: Controls mount with undefined/default state and later become controlled.
  • Impact: Property controls may behave inconsistently, making camera/property tuning harder.

warn: GetBindingData<id> method already registered (repeated)

  • Type: Duplicate registration warning.
  • Probable meaning: Binding handlers are being registered repeatedly across rerenders/remounts without cleanup.
  • Impact: High log noise and risk of duplicate event executions, especially problematic for interactive scene controls.

Overall Read

  • Task 4 core hierarchy behavior works in builder: parent rotation correctly drives child motion with preserved local offsets.
  • The major blocker is camera reliability: direct Perspective Camera rotation can make objects disappear, reducing feature parity confidence.
  • Repeated binding-registration and controlled/uncontrolled warnings suggest editor/runtime instability that can amplify interaction and camera issues.
  • Product priority for this task should focus on camera rotation reliability first, then interaction-state stability for repeatable multi-step scene authoring.