diff --git a/docs/DEVLOG.md b/docs/DEVLOG.md index bd1dc59..bd99671 100644 --- a/docs/DEVLOG.md +++ b/docs/DEVLOG.md @@ -1316,3 +1316,64 @@ hash) and `make deb-check`. **Next run:** A7, visual effects: muzzle flashes, tracers, hit feedback, build and collapse dust, keg blasts, splashes and surges, all pooled. A stress scene must stay within the particle budget, and captures must show the hit feedback clearly. Then H6. + +## 2026-11-14 (late morning, third run): A7 done + +**Start of run (11:03 ET Saturday):** the lock was free and taken fresh. The pull was a +no-op and the tree was clean. Nothing in the Agents category was addressed to this task. + +**A7 (#47), closed: visual effects.** +- `EffectsView` (`src/client/effects/`), a child of `MatchView`. It starts effects from + the server's FX records (shots, impacts, keg blasts, harvest swings, pieces placed) + and from world changes it diffs itself (pieces gone, players into the water, hard + landings, surges, projectiles in flight). +- Recipes: + - muzzle flash at the held model's +Z end (`MatchView.muzzle_of`); the simulation + fires from the eye + - tracer ribbons to each pellet's impact + - hit bursts on players, with no blood + - chips by material or ground band, and foam for shots into water + - keg blasts: flash, fireball, debris, smoke and a light + - build dust, collapse clouds, splashes and surge spray along the shore +- Pools are allocated once at the preset's budget: Low 256, Medium 512, High 1,024 + particles, 64 tracers and 4 lights. That's three draw calls however big the fight. +- **Engine gotcha:** the stock `BILLBOARD_ENABLED` and `BILLBOARD_PARTICLES` modes + ignore a MultiMesh instance's scale, so every particle drew 1 m wide. It took + side-by-side 0.3 m and 3 m test particles to show it. Our shader reads the size from + the instance's custom data, and converts Palette's sRGB values to linear (without + that, everything came out washed pale). +- HUD: there was **no reticle at all**. There is now a paper ring and dot, four ticks + round it when your shot hits a player (`HitFeedback`), and a `WARNING` flush at the + screen's edge when you're hurt. +- Docs: STYLE.md (an effects section), PLAY.md (the presets table), ARCHITECTURE.md + and CLAUDE.md (`make effects-captures`). + +**Tests:** +- `make check` passed. +- New `test_effects_view` (12 tests). In the stress test, 24 shooters with kegs fill + each budget, never exceed it, drop the excess and add no nodes. One frame on a + near-full pool took about 1.4 ms headless. That's CPU time only, not a frame rate. +- `make effects-captures` (fight, blast, work and stress) were all opened and judged: + - The fight shows the flash at the muzzle, the burst on the target's chest and the + hit marker. + - The blast reads as an orange fireball with debris and the next wall's collapse dust. + - In the stress scene, the tracers criss-cross the fort. +- The blast was also rendered in Compatibility; it's darker, as everything in that + renderer is. + +**Decisions:** +- Own-shot flashes come from server FX, so they lag one round trip. This is left for + the R6 playtest to judge. +- The quieter effects (build dust, chips) are small on purpose. + +**Pace (11:50 ET Saturday):** +- About 44 hours remain to Monday 08:00. +- Release path left: H6 (the visual QA pass, a whole run on its own: every capture + target rendered and judged), R4 (originality and licence audit), then R5. +- H13 is still unreproduced. H8, H10 and H14 are low priority. +- R6 and R7 wait on Eric. #72 (launch fiction) is waiting on him too. + +**Next run:** H6. Render every `make *-captures` target, check each one against the +issue's checklist (menus, drop, biomes, building, combat, tide phases, results), file +defects as `type/bug` and fix what's in reach. Look for placeholder art and text: +ARCHITECTURE.md still calls the figures "stand-in shapes".