A card short of memory may refuse a texture or a buffer without throwing: the call only leaves OUT_OF_MEMORY for
getError(), which nothing read. Refused, the 64 MB atlas drew every city, label and marker as a black box while the
map stayed on the card (seen in Chromium by refusing it).
The big uploads now read it (glMem()): the atlas, the land for each zoom level, the tubes once a day, the cables.
The atlas tries 2048 px (16 MB) before giving up; any other refusal is the card's error, so draw() gives WebGL up
for the session and draws the same frame again in 2D. getError() is never read on an ordinary frame: each read waits
for the card.
tests/webgl-out-of-memory.test.js: a 4096 px atlas refused gives a 2048 px one; both refused, or the land or the
tubes refused, leave the map in 2D in that frame with no glitch for the player; panning reads no error.
- A sprite or disc drawn as the queue grows was written into the old array and
lost: the record is now taken before the array is read.
- A city's picture without an attack shared its cache key with step 0 of a
DDoS ring (always, with animations off): no attack is now phase -1, and
cityStatic() reads only what the key holds.
- Back at the title (or on a damaged save), drawFrame() returned before hiding
the card's layers, so the last network stayed behind the title: the layers
are now shown or hidden on entry.
- An error from the card (frame start, tube upload, atlas, sprite flush) now
gives WebGL up and draws the same frame in 2D, once; the 2D context, the
sprite queue and GLS.frame are reset whatever fails. Other errors still
reach tickErr() and leave WebGL on.
- Selecting a tube no longer rebuilds and uploads every tube, packet and
point (about 230 KB on the big-network fixture): its halo is its own small
buffer.
- Sea, land, waves, clouds, cables, tubes and packets are drawn by the
graphics card; the land is geometry built once, so panning and zooming
repaint nothing.
- Cities, labels and markers are painted once into a sprite atlas and drawn
in one call (with drawImage in 2D, which speeds up the 2D map too).
- Settings > Map drawing: Auto or Always 2D, per device. Browsers without
WebGL2, a lost context and puzzles keep the 2D map.
- npm run bench:gpu compares 2D and WebGL in a real browser on a real GPU;
?fps shows a frame meter.