Skip to content

Aura3D 2.0.3

Latest
Latest

Choose a tag to compare

View all tags
@gchahal1982 gchahal1982 released this 16 Aug 08:23
· 59 commits to main since this release
v2.0.3
a89acd6

Aura3D 2.0.3 Release Notes

Version: 2.0.3

Status: published to npm, GitHub, and https://aura3d.auraone.ai/ on 2026-08-16

Aura3D 2.0.3 is a showcase and test-harness patch. It keeps the 2.0.2 public
architecture and claim boundaries, aligns the 29 public packages and scaffold
pins, and fixes the local evidence and responsive route defects found in the
full public-example audit. It does not change renderer or engine capability.

Showcase and test-harness corrections

  • Vite-ready browser specs. Vite 7 colorizes its ready-line port. The gallery
    and wow screenshot specs now strip ANSI escape sequences before matching that
    line, restoring 11 previously blocked gallery tests and the wow spec.
  • Smart City stress evidence. The medium gallery level now renders 328
    instances, above the ≥300 gate. The Littlest Tokyo-only hero, building
    keepout, and exclusion of authored tram/train/bus nodes are unchanged.
  • Interactive draw-range proof. Geometry Draw Range now has the control its
    card promises: ↑/↓/Space/click cycles indexed 12↔24 and array 6↔12 ranges.
    Every state remains partial; the route never adds a full-range step.
  • 390px route hygiene. The examples catalog hides nonessential version and
    ghost-action chrome at narrow widths, and geometry-drawrange collapses its
    route-local grid so neither route overflows a 390px viewport.
  • Favicon links. Fifteen route entry points link /favicon.svg, removing
    local-dev favicon 404 noise. The production /favicon.ico remains unchanged.
  • Collision recovery. Turbo Drift Circuit now budgets enough adaptive CCD
    substeps for the high-velocity separation frame after a Rapier impact. The
    former ceiling could reject that frame, stop the mounted loop, and leave the
    car and HUD frozen; the browser regression now drives through contact and
    verifies that race frames and progress continue afterward.
  • Example launch controls. Marketing posters keep lightweight embedded
    previews on chrome=hidden, while an intentional click opens the live route
    with chrome=visible so its controls and option panels are immediately
    available.

Audit evidence retained

The audit exercised all 36 public routes with zero console/page errors, operated
the advertised controls with pixel or runtime evidence, completed Turbo Drift,
Blockfall, Skyline, and Clash end to end, and rechecked production HTTP 200s for
the routes, favicon, Draco decoder, catalog images, and Clash playable path.
Those results are evidence for the named showcase routes and release hygiene;
they do not broaden the root createAuraApp claim boundary.

Claim boundary

No renderer, engine, physics-owner, asset-pipeline, or public API capability is
introduced by this patch. The 2.0.2 boundaries remain in force: route-local
showcase behavior is labeled at its proven scope, root-safe claims require
root-only browser evidence, and the repository-locked three@0.185.1
comparison remains bounded rather than a universal parity claim.

Templates and install

All 19 public scaffolds pin their @aura3d/* dependencies to 2.0.3, matching
the package version used by the release build.

npx create-aura3d@2.0.3 my-scene --template product-viewer
npm install @aura3d/engine@2.0.3

Use @aura3d/lean/product for typed product scenes and
@aura3d/lean/game for deterministic arcade motion. Use @aura3d/engine@2.0.3
when an application intentionally needs the broader compatibility-heavy safe
authoring surface.

Superseded versions and publication

All 29 public npm packages were published at 2.0.3 with the repository
release publisher. Every corresponding 2.0.2 version is now deprecated with
the exact message: Aura3D 2.0.3 supersedes this release. Upgrade to 2.0.3.
The previously deprecated 2.0.1 versions remain deprecated. The active
2.0.3 versions are not deprecated.

The release commit is pushed to main at a89acd6d; the follow-up collision
and marketing interaction fix is pushed at fec457c2. The marketing site was
built from the monorepo and promoted through Vercel to the canonical
https://aura3d.auraone.ai/ domain. Production checks returned HTTP 200 for
/favicon.ico, /assets/draco/draco_decoder.wasm, the examples catalog, the
product configurator, and /showcase/aura-clash/playable/; the 390px catalog
viewport had no horizontal overflow, and the configurator had no browser page
or console errors. All 83 deployed HTML routes contain 2.0.3 copy with no
remaining 2.0.2 references.

Assets 2
Loading