Field update

Read the field, not the fog

dWars v0.5.5 · 12 August 2026

Command mode is cleaner, every campaign level is fully armed, and the <http://itch.io|itch.io> crash from v0.5.4 is fixed.

New

Players on unsupported GPUs now see a warning — with a Discord link for support — before any assets download. No more silent failure after a 250 MB wait.
Map Builder: drag the whole selection region with the Move cross. The "Saved At" timestamp now updates live instead of freezing at the designer's last typed date.

Command mode now shows each battalion as a clean strategic circle — hero and base units only. The overview reads as a map, not a crowd.
All campaign levels now field three battalions per side. Burwood Girls and Summer Hill had their missing battalions added.
Unit collision radii tuned across Drone, Roller, and Tank — brought closer to their visual footprint.
Mousewheel on the Level List scrolls smoothly. Each notch now moves a third of a row instead of jumping a full one.
Supply propagation is now consistent at speed boundaries — the timer no longer skips a step when it falls exactly on an interval.

Out-of-memory crash on <http://itch.io|itch.io> introduced in v0.5.4. The root cause was GPU texture handles accumulating across map loads; fixed with a texture-lease audit.
Waves kept arriving after a team's base was destroyed. Both the CPU scheduler and GPU spawner now stop on the same condition.
Large unit spawns were silently skipping positions, so fewer units deployed than ordered.
Draw order in command mode was wrong — friendly battalions could render beneath enemies; selected battalions could render beneath unselected ones.
LoadOut screen could freeze blank on low-VRAM devices after a WebGPU memory probe. It now recovers with a path back to Home.
WebGPU players were incorrectly shown the "Your GPU does not meet minimum requirements" gate. WebGPU reports a fixed shader level that the old check misread as SM 4.5.

Six battalions per map. The field is fully staffed. — Neesa