Muzzle flashes, tracers, hit feedback, building and collapse effects, explosions, splashes and tide surges, all pooled.
Acceptance
Particle counts stay within budget in a stress scene.
Hit feedback is clear in captures.
**Depends on:** A1, B8
Muzzle flashes, tracers, hit feedback, building and collapse effects, explosions, splashes and tide surges, all pooled.
**Acceptance**
- Particle counts stay within budget in a stress scene.
- Hit feedback is clear in captures.
claude
added this to the v0.6 Art, Audio and UI milestone 2026-11-09 05:28:39 +00:00
Deferred for the Monday 2026-11-16 build. The schedule is more than a day behind, so unprioritised issues wait until multiplayer, the client UI (#78, A9, A10) and release work are done. Hit feedback the player needs goes in N11 (#78) instead. This stays open. — tidewall-build
Deferred for the Monday 2026-11-16 build. The schedule is more than a day behind, so unprioritised issues wait until multiplayer, the client UI (#78, A9, A10) and release work are done. Hit feedback the player needs goes in N11 (#78) instead. This stays open. — tidewall-build
EffectsView (src/client/effects/): muzzle flashes placed at the held weapon's muzzle, tracer ribbons to each pellet's impact, streaks behind projectiles in flight, hit bursts on players (no blood), chips and dust by material and ground, keg blasts (flash, fireball, debris, smoke, a light), build dust, collapse clouds for broken pieces, splashes and surge spray along the shore.
Pooled: particles live in packed arrays and are drawn by two MultiMeshes and a small billboard shader. Pools are allocated once at the preset's budget (Low 256, Medium 512, High 1,024 particles; 64 tracers; 4 lights), so a fight costs three draw calls.
HUD: a reticle (there wasn't one), four ticks round it when your shot hits a player (HitFeedback), and a rust flash at the screen's edge when you're hurt.
Found on the way: Godot's stock billboard modes ignore a MultiMesh instance's scale (every particle drew at 1 m). The custom shader reads the size from custom data instead, and converts Palette's sRGB colours.
Tested
test_effects_view (12 tests): each recipe, tracers ending at their impacts, effects that are too far away skipped, the presets' budgets, HitFeedback, and the HUD. A stress scene of 24 shooters plus kegs every 10 frames for 2 s stays within each budget, fills it, drops the excess, and adds no nodes. A frame on a near-full pool took about 1.4 ms headless on this host. That's CPU time only, not a frame rate.
make check passed.
make effects-captures (fight, blast, work, stress), each opened and checked. The fight capture shows the flash at the muzzle, the burst on the target's chest and the hit marker. The blast also rendered in the Compatibility renderer, slightly darker as the rest of that renderer is.
Follow-ups: none filed. The muzzle flash for your own shots comes from the server's FX, so it lags by one round trip. Predicting it locally could come out of the R6 playtest if it feels late. — tidewall-build
Done in e8414fd.
**What changed**
- `EffectsView` (`src/client/effects/`): muzzle flashes placed at the held weapon's muzzle, tracer ribbons to each pellet's impact, streaks behind projectiles in flight, hit bursts on players (no blood), chips and dust by material and ground, keg blasts (flash, fireball, debris, smoke, a light), build dust, collapse clouds for broken pieces, splashes and surge spray along the shore.
- Pooled: particles live in packed arrays and are drawn by two MultiMeshes and a small billboard shader. Pools are allocated once at the preset's budget (Low 256, Medium 512, High 1,024 particles; 64 tracers; 4 lights), so a fight costs three draw calls.
- HUD: a reticle (there wasn't one), four ticks round it when your shot hits a player (`HitFeedback`), and a rust flash at the screen's edge when you're hurt.
- **Found on the way:** Godot's stock billboard modes ignore a MultiMesh instance's scale (every particle drew at 1 m). The custom shader reads the size from custom data instead, and converts Palette's sRGB colours.
**Tested**
- `test_effects_view` (12 tests): each recipe, tracers ending at their impacts, effects that are too far away skipped, the presets' budgets, `HitFeedback`, and the HUD. A stress scene of 24 shooters plus kegs every 10 frames for 2 s stays within each budget, fills it, drops the excess, and adds no nodes. A frame on a near-full pool took about 1.4 ms headless on this host. That's CPU time only, not a frame rate.
- `make check` passed.
- `make effects-captures` (fight, blast, work, stress), each opened and checked. The fight capture shows the flash at the muzzle, the burst on the target's chest and the hit marker. The blast also rendered in the Compatibility renderer, slightly darker as the rest of that renderer is.
**Follow-ups:** none filed. The muzzle flash for your own shots comes from the server's FX, so it lags by one round trip. Predicting it locally could come out of the R6 playtest if it feels late. — tidewall-build
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Depends on: A1, B8
Muzzle flashes, tracers, hit feedback, building and collapse effects, explosions, splashes and tide surges, all pooled.
Acceptance
Deferred for the Monday 2026-11-16 build. The schedule is more than a day behind, so unprioritised issues wait until multiplayer, the client UI (#78, A9, A10) and release work are done. Hit feedback the player needs goes in N11 (#78) instead. This stays open. — tidewall-build
Done in
e8414fd.What changed
EffectsView(src/client/effects/): muzzle flashes placed at the held weapon's muzzle, tracer ribbons to each pellet's impact, streaks behind projectiles in flight, hit bursts on players (no blood), chips and dust by material and ground, keg blasts (flash, fireball, debris, smoke, a light), build dust, collapse clouds for broken pieces, splashes and surge spray along the shore.HitFeedback), and a rust flash at the screen's edge when you're hurt.Tested
test_effects_view(12 tests): each recipe, tracers ending at their impacts, effects that are too far away skipped, the presets' budgets,HitFeedback, and the HUD. A stress scene of 24 shooters plus kegs every 10 frames for 2 s stays within each budget, fills it, drops the excess, and adds no nodes. A frame on a near-full pool took about 1.4 ms headless on this host. That's CPU time only, not a frame rate.make checkpassed.make effects-captures(fight, blast, work, stress), each opened and checked. The fight capture shows the flash at the muzzle, the burst on the target's chest and the hit marker. The blast also rendered in the Compatibility renderer, slightly darker as the rest of that renderer is.Follow-ups: none filed. The muzzle flash for your own shots comes from the server's FX, so it lags by one round trip. Predicting it locally could come out of the R6 playtest if it feels late. — tidewall-build