@forgeax/engine-vfx-render 0.1.4 → 0.1.7

package/README.md

@@ -18,7 +18,9 @@ const vfx = createVfxRuntimeHost({
 const attached = await vfx.attachWorld({ world, assets });
 if (!attached.ok) return attached;
 
-const renderer = await createRenderer(canvas, { features: [vfx.feature] });
+const created = await createRenderer(canvas, { features: [vfx.feature] });
+if (!created.ok) throw created.error;
+const renderer = created.value;
 ```
 
 Create the host before the Renderer and pass `host.feature` at Renderer
@@ -27,19 +29,13 @@ FixedUpdate producer. `detachWorld` removes both the system and runtime
 resource. Material and mesh GUIDs resolve through the attached World's
 `AssetRegistry`.
 
-When the Registry comes from `createApp`, select
-`vfxGpuEffectContribution` in the App's `assetDecoders` option. The App and
-host share that exact GPU decoder lease; a different `particle-effect`
-decoder remains a closed owner conflict. A manually created Registry can use
-`installVfxRuntimeDecoder` before `attachWorld`.
-
 ## Frame path
 
 | Stage | Work |
 |:--|:--|
 | Extract | Read camera and ordered GPU tick intents from each attached World |
-| Prepare | Reuse/create program, particle, scan, indirect, per-tick uniform, per-renderer projection, mesh, and graphics resources |
-| Contribute | Record spawn/update/scan/compact, one projection dispatch per renderer, then dependent indirect draws |
+| Plan | Declare program, particle, scan, indirect, per-tick uniform, per-renderer projection, mesh, and graphics resources |
+| Record | Compile the plan into spawn/update/scan/compact dispatches, then dependent indirect draws |
 | Recover | Drop generation-owned GPU state and restart affected runtime players |
 | Dispose | Release feature-owned state; the Renderer resolver destroys RHI resources exactly once |
 
@@ -73,9 +69,7 @@ use the same owner path.
 - A material pass named `particle-billboard` or `particle-mesh` selects that renderer's authored
   shader module and render state. Ordinary `Forward` passes are ignored because their vertex layout
   is not a particle projection contract; absence of a matching particle pass uses the package-owned
-  built-in shader. The render owner derives whether the selected shader consumes a group-0
-  scene-depth texture from its binding contract, so authored shaders retain their own group-0
-  layout and are not given an unrelated depth binding.
+  built-in shader.
 - A custom particle material with a non-empty `parameters` schema receives the standard material
   bind group at group 1. Numeric parameters are uploaded through the shader-schema UBO layout;
   texture parameters resolve their authored TextureAsset and optional SamplerAsset through the