Repository navigation
examples: pixi-3d (closed beta) spatial upscaling example - #101
Merged
Merged
Conversation
examples/pixi3d/hello runs the pixi adapter under a pixi-3d View3D (thin slats, glossy spheres, a metal knot): the view is sized to the render resolution, rendered into a half-res RenderTexture, upscaled by FSR1 and presented on a Sprite; keys switch spatial / bilinear / native. @pixi/3d is a closed beta (not on npm; testers keep its code and builds inside the beta), so it is never committed. The example resolves it from the release tarball unpacked into the gitignored examples/pixi3d/vendor/; without it, the vite config loads the page as a setup notice, so CI, Pages and anyone without the beta still build. The root typecheck/lint skip the beta; `tsc -p examples/pixi3d` checks the example with it. meshoptimizer (pixi-3d's one runtime dependency, public MIT) joins the devDependencies. Startup runs in an async main(), not top-level await: in a production build pixi-3d's backend chunk imports back from the entry chunk while app.init() awaits it, and the two deadlock (no canvas, no error). docs/pixi.md records it. GPU-verified with @pixi/3d 0.1.0-beta.2 + pixi.js 8.22 on Chrome (Metal): spatial, bilinear and native upright in dev and in the production build, FSR1 visibly sharper than bilinear on the slats, no WebGPU/pixi warnings. Without the beta: lint, typecheck, 585 tests, examples build (notice only, no beta code) and verify:packed-guides all pass. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Re-opened against main: #95 merged into
feat/go-monorepoafter #94 had already merged, so it never reached main. Same two commits. Adds a pixi-3d example: aView3Drenders a thin-slat fence, glossy spheres and a metal knot at reduced resolution. FSR1 upscales it, and aSpritepresents the result. Keys: 1 spatial, 2 bilinear, 3 native, space pauses.pixi-3d is a closed beta. Our example code is public, but the beta's code and builds are never committed.
@pixi/3dresolves from a release tarball unpacked into the gitignoredexamples/pixi3d/vendor/(setup:examples/pixi3d/README.md). Without it, the vite config loads the example as a setup notice, so CI and GitHub Pages build without the beta.examples/pixi3d/hello, a P2 gallery card, owntsconfig(pnpm exec tsc -p examples/pixi3dwith the beta present).meshoptimizerdevDependency (pixi-3d's one runtime dependency, public on npm).docs/pixi.md: the pixi-3d snippet, the production-build top-level-await hang (start fromasync function main()), and what pixi-3d still needs for the temporal path, tracked upstream as pixi-3d-beta chore(scripts): configurable harness ports, clean GPU-smoke teardown, separate Vite caches #26–bench: Q14 repro for #17 (thin-feature locks under noisy SSGI) — configuration, not core #29.Verified: lint, typecheck, 585 tests, examples build with and without the beta. On GPU (Chrome,
@pixi/3d0.1.0-beta.2, pixi.js 8.22), dev and production builds, spatial/bilinear/native render upright with no warnings, and FSR1 is visibly sharper than bilinear on the slats.🤖 Generated with Claude Code