- Web engine CMake: apply WITH_WEB_USD_PYTHON to blender_web_engine_core, embed /usd resources, link pxr Python bindings after the core archive and whole-archive the monolithic OpenUSD archive. Fixes the wm.usd_export abort and restores Alembic/USD embedded export. - ?ui=web menus: fix inverted localOnly gating and route queueLocalDesktopOperator and nativeAdd through the desktop operator channel with a VIEW_3D context; non-mesh edit-mode selection uses the native VIEW3D_SELECT bridge. - Refresh WebEngine wasm/js artifacts, manual/course pages and the complete course video asset. - Record focused Chromium probes for Add/F3/parameters/modifier/UV/curve/deform, scene operations, OPFS save/reopen and worker restart. Evidence is NOT_CLAIMED. Co-Authored-By: Claude Code <noreply@anthropic.com>
3.8 KiB
Web Blender Modeler V1 0.1.0-rc.1 Release Notes
Release candidate identity: web-blender-0.1.0-rc.1, engine
blender-wasm-0.1.0-rc.1.
This candidate is a Chromium-only Web product built around Blender 5.2 Main/WebEngine. It provides
the 31 capabilities in the support matrix, locally or through the official server/native backend;
the execution location (local / server / browser) is recorded per capability in
tools/web/manual/feature-matrix.json. The normative product boundary is in
V1_SCOPE.md.
Verified V1 capabilities
- Import
.blend, edit the declared Object, Mesh and Principled material subset, undo, redo, save atomically, restart the Storage and WebEngine Workers, reopen, and export a semantically checked GLB. - Preserve stable object, mesh and material identities across save/reopen and verify both the main-thread WebGL and OffscreenCanvas Worker production viewports with non-empty pixels.
- Select integrity-checked single-thread or pthread WebEngine artifacts from one versioned engine manifest. The pthread variant is used only when the isolated platform prerequisites pass.
- Store projects, snapshots and bounded assets in origin-bound OPFS/IndexedDB, including tested interruption, Worker restart, quota failure and recovery behavior.
- Exercise bounded 100k, 1M and 10M geometry, 4K/8K textures, 600-frame simulation cache and one-million-frame media indexing gates.
- Exercise deterministic WASM, OPFS, GPU and NanoVDB out-of-memory recovery, WebGL device loss,
network interruption, malformed
.blendinput and malicious archive rejection. - Deliver deterministic offline binary and corresponding-source archives with SHA-256 checksums, SPDX SBOM, licenses, source offer, deployment contract and operations diagnostics.
- Reproduce quick, Chromium and release CI lanes with lockfile, source, engine, archive and per-command log hash bindings.
Capability boundaries
LOCAL_EXACT and LOCAL_BOUNDED mean only the fixtures, operations and budgets declared in
V1_SCOPE.md and parity-ledger.json. Unsupported operations must
remain blocked or preserved; the release does not infer support from a readable Blender data block.
SERVER covers validated request/result boundaries for work such as Cycles rendering, complex physics
bakes and final video encoding. This offline candidate does not bundle or configure those services and
does not claim local-equivalent execution.
EXCLUDED includes arbitrary Python/Text autorun, add-on installation, native desktop windows and
native CUDA, Metal, HIP or OptiX backends. The UI must not report those operations as successful.
The legacy parity ledger is retained as historical planning data (updatedAt 2026-08-17). The
current capability claim source is tools/web/manual/feature-matrix.json, enforced by
tools/web/check-parity-claim.mjs (31/31 capabilities usable, local or backend). Source-unit
behavioral evidence remains tracked separately in tests/golden/WBV2/feature-completeness-audit.json.
Delivery evidence
Verify SHA256SUMS.txt, then verify RC_MANIFEST.json.sha256 and RC_MANIFEST.json before deployment.
The manifest binds the RC version, base commit, engine release ID, package lock, ledger, embedded release
metadata, SBOM, binary/source archives and operations reports.
Read Known limitations before deployment, especially the browser, engine variant, origin-bound storage, quota, WASM and GPU budget boundaries.
Use Release recovery to verify delivery evidence, export project backups and handle pre-switch failures, compatible rollback or blocked schema downgrade.
Deployment requirements and operator commands are in DEPLOYMENT.md. Stable error signals and recovery boundaries are in operations-diagnostics.json.