Skip to content

fix(showcase): commit jumping-jacks clip so the Mixamo hero works in production - #42

Merged
a-baran-orhan merged 1 commit into
mainfrom
feat/ship-jumping-jacks-clip
Jul 12, 2026
Merged

fix(showcase): commit jumping-jacks clip so the Mixamo hero works in production#42
a-baran-orhan merged 1 commit into
mainfrom
feat/ship-jumping-jacks-clip

Conversation

@a-baran-orhan

Copy link
Copy Markdown
Member

Description

Follow-up to #41. The Mixamo jumping-jacks hero still showed procedural in production after #41 merged. Root cause: the .fbx clips are gitignored and there is no /clips CDN rewrite in vercel.json, so the browser's request for /clips/jumping-jacks.fbx 404s in production and the viewer silently falls back to procedural. The clip only ever worked locally, where the gitignored file physically exists.

Evidence:

  • https://www.posecode.org/clips/jumping-jacks.fbxHTTP 404
  • https://www.posecode.org/models/character.glbHTTP 200 (this model is committed, which is why the skinned figure renders)
  • No .fbx is tracked in git; vercel.json has no /clips/* rewrite.

The "served from storage/CDN in production" comment described an intent that was never wired up.

Fix

Mirror how character.glb is already handled — commit the one clip the marketing surfaces use so Vercel serves it directly from public/. No CDN/infra required.

  • .gitignore — negate the ignore for jumping-jacks.fbx only; the other five large, unused Mixamo clips stay ignored.
  • playground/public/clips/jumping-jacks.fbx — committed (375 KB — smaller than the already-committed 702 KB character.glb).
  • playground/src/clips.ts — correct the stale "served from CDN" comment.

Reviewer notes

  • After deploy, /clips/jumping-jacks.fbx should return 200 and the landing hero + playground default should play the Mixamo loop (not procedural).
  • The build emits the clip into playground/dist/clips/jumping-jacks.fbx, confirming Vercel will serve it.
  • If a real CDN is preferred later, the alternative is a /clips/* rewrite in vercel.json + uploading the assets there; this PR deliberately avoids that to stay self-contained.

Type of Change

  • Bug fix (non-breaking change which fixes an issue) — production hero fell back to procedural

Checklist

  • My code follows the code style guidelines of this project
  • I have performed a self-review of my own code
  • My changes generate no new TypeScript/compiler warnings or errors:
    • Running npm run typecheck passes successfully
    • Running npm run build compiles without errors
  • I have run the unit test suite (npm test) and all tests pass
  • If applicable, I have run the fidelity evals (npm run eval) — n/a (asset/config only, no fidelity-invariant logic changed)
  • If I added a new movement, I ran node scripts/generate-content-pages.mjs — n/a (no new movement)

…production

The Mixamo hero/playground clip never actually played in production: the
.fbx files are gitignored and there is no /clips CDN rewrite in
vercel.json, so /clips/jumping-jacks.fbx 404s and silently falls back to
procedural. (Verified: prod /clips/jumping-jacks.fbx -> 404, while the
committed /models/character.glb -> 200.)

Fix mirrors how character.glb is already handled — commit the single clip
the marketing surfaces use so Vercel serves it directly:

- .gitignore: negate the ignore for jumping-jacks.fbx only; the other five
  large, unused Mixamo clips stay ignored
- playground/public/clips/jumping-jacks.fbx: committed (375 KB, smaller
  than the already-committed 702 KB character.glb)
- playground/src/clips.ts: correct the stale 'served from CDN' comment

No CDN/infra required. typecheck, build, and tests all pass; the clip is
emitted into playground/dist/clips/ by the build.
@vercel

vercel Bot commented Jul 12, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
posecode Ready Ready Preview, Comment Jul 12, 2026 6:40pm

@a-baran-orhan
a-baran-orhan merged commit 07fe312 into main Jul 12, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant