Written while these changes are on the preview build and not on the live site.
Most of you open WASCAPE on a phone, and most phones made it look soft. It turned out to be two problems stacked on top of each other.
The first, fixed on 8 November, was resolution. A phone was pinned to one device pixel per CSS pixel on a screen with three, and a low-end quality step could then cut that to 0.6. Every frame was about a third of the panel’s resolution per axis, stretched to fit. Phones now draw at two device pixels per CSS pixel and keep the full render scale.
That helped less than it should have, which is how the second problem showed itself. A phone booted at three times a town’s coarse shell, on the idea that the frame-rate loop would raise the budget once it saw headroom. On the streamed towns that climb cannot happen. The memory pool is sized once, from the first budget, and every later budget is clamped to it. So the boot was the whole session. Ludlow drew about 407,000 splats on a phone and 4.56 million on a desktop.
The fix picks the ceiling before anything loads, from the memory the phone reports: 9 million splats at 8 GB, 5 million at 4 GB, 3 million at 2 GB or less. iPhones do not report memory, so they get 5 million. The 9 million rung plans about 794 MiB, past the 751 MiB that once got phone tabs killed, which is why only phones reporting 8 GB get it. A frame-rate loop can step a phone down when it struggles, but it cannot step it back from an out-of-memory kill, so memory has to decide first.
In Pixel 7 emulation in headed Chrome, Ludlow went from 407,000 splats drawn to its full 4.56 million, the same as a desktop. Emulation is not a phone. These rungs are a proposal until they have been run on real handsets, and some of them may come down when they are.