@woosh/meep-engine 3.34.0 → 3.35.0

package/src/shade/playground/particle_ecs/README.md

@@ -115,8 +115,13 @@ Two things to know before editing one:
 - **The flame does not darken what is behind it.** Additive emitters write the emission accumulator,
   which the resolve adds outside the coverage normalization — so the fire lights the frame instead of
   taking coverage from it. The smoke, which is matter, does cover.
-- **The soot flakes cross in front of the flame and are lit by nothing**, and still read, because
-  they are dark against something bright. That is the cheapest depth cue in the set.
+- **The smoke is lit, not painted.** Its gradient is an albedo — tar-brown near the fire, paling to
+  grey as it thins — and `EMITTER_FLAG.LIGHTING` does the rest: the firelight warms its underside,
+  the moon greys the column above, both shadowed, both read out of the froxel volume that lights
+  the fog. Orbit until the moon is behind it: the thin edges pass moonlight through (back-face
+  transmission) and the dense core holds it back.
+- **The soot flakes cross in front of the flame** and read because they are near-black — lit like the
+  smoke, with an albedo to match. That is the cheapest depth cue in the set.
 - **Orbit around it.** The particles and the transparent surfaces composite against each other with
   no order between them — both write extinction into one voxel volume and both resolve out of the
   same accumulators. Switch the renderer to MBOIT and the particles vanish while everything else
@@ -140,11 +145,8 @@ ask for it.
 
 ## What it deliberately does not do
 
-- **No emitter opts into `EMITTER_FLAG.LIGHTING`.** The shipped hook is
-  `chunk_particle_lighting_unlit`, a pass-through, so the flag would cost a bit in a record and
-  change no pixel. The smoke and the soot are *painted* lit instead: their gradients carry the fire's
-  warmth low down and the moon's blue higher up, over the particle's own age. When a lit hook lands,
-  those gradients are the thing to reconsider.
+- **The flame and the embers are not lit.** They are additive and they are the light; the firelight
+  is a point light at the fire, because a particle does not light anything.
 - **No emitter opts into culling.** One fire, always on screen; the frustum test in the tick pass
   would never be taken. The measured bounds are still published every frame and still read by the
   occupancy pass.
@@ -201,3 +203,7 @@ The four programs are around 620 VM instructions each in UPDATE, most of which i
 is twelve of them for a divergence-free field: over a metre of flame nobody can tell, and the four
 effects share the register budget above — the editor's toolbar reports both numbers after every
 recompile, which is the cheapest way to notice an edit that has gone past them.
+
+Lighting the smoke and the soot costs the particle draw +200..275 us at 1898x926 and +0.8..1.2 ms at
+3818x2006 on an RTX 4090, over ~450 us and ~2.1 ms unlit; `renderer/particles/DESIGN.md` has how that was
+measured and where it goes.

package/src/shade/playground/particle_ecs/bonfire_effects.d.ts

@@ -115,11 +115,11 @@ export function bonfire_sprite_urls(textures?: object): {
  *
  * ## Lighting
  *
- * None of these opt into `EMITTER_FLAG.LIGHTING`, and that is not an oversight: the shipped lighting
- * hook is `chunk_particle_lighting_unlit`, a pass-through, so the flag would cost a bit in a record
- * and change no pixel. The smoke and the soot are *painted* lit instead — their gradients carry the
- * fire's warmth low down where the fire would light them and the moon's blue higher up, over the
- * particle's own age. When the lit hook lands the gradients are what to reconsider.
+ * The smoke and the soot are lit (`EMITTER_FLAG.LIGHTING`), so their gradients are albedo: the smoke
+ * tar-brown at birth paling to grey as it thins, the soot near-black throughout — the alpha ramps are
+ * the same as when the gradients were painted lit, emitted colour carrying the fire's warmth low down
+ * and the moon's blue higher up. The fire and the moon now do that. The flame and the embers are
+ * additive and unlit: they are the light.
  */
 /**
  * The four saved documents, by the key the page knows them by.

package/src/shade/playground/particle_ecs/bonfire_effects.js

@@ -62,11 +62,11 @@ import soot_json from "./effects/soot.json";
  *
  * ## Lighting
  *
- * None of these opt into `EMITTER_FLAG.LIGHTING`, and that is not an oversight: the shipped lighting
- * hook is `chunk_particle_lighting_unlit`, a pass-through, so the flag would cost a bit in a record
- * and change no pixel. The smoke and the soot are *painted* lit instead — their gradients carry the
- * fire's warmth low down where the fire would light them and the moon's blue higher up, over the
- * particle's own age. When the lit hook lands the gradients are what to reconsider.
+ * The smoke and the soot are lit (`EMITTER_FLAG.LIGHTING`), so their gradients are albedo: the smoke
+ * tar-brown at birth paling to grey as it thins, the soot near-black throughout — the alpha ramps are
+ * the same as when the gradients were painted lit, emitted colour carrying the fire's warmth low down
+ * and the moon's blue higher up. The fire and the moon now do that. The flame and the embers are
+ * additive and unlit: they are the light.
  */
 
 /**