v0.111.1 Says Why

A web game that stops while it is running now says so, and tells the player what went wrong, where it used to leave the last picture on screen. And a web game puts half as much on the graphics card in a single frame while it loads, which is what a phone's browser has the least room for.

A web game that stops says so

• At any moment, not just while it starts. If the engine stopped after the game was on screen, the page used to keep showing the last frame, often the game's own loading screen, with nothing to say it had stopped. It now shows the panel with what stopped it and how much memory the game was using.
• What the graphics card refused reaches the page. A shader or texture the browser's graphics refused used to leave no trace in a web build. It is now written to the page's log and kept with the run.
• The next visit says when there were errors. A run that logged engine errors is offered on the next visit with "Show what it said", the same as a run that stopped, so the player can copy it and send it to you.

Gentler on phones while a level loads

A web game loading its models was meant to put at most 32 MB on the graphics card each frame. Because a frame asked twice, it was putting up to twice that. It now keeps to one budget a frame, so the memory the browser holds for those uploads stays half the size.

Upgrading

Export your web build again and upload it. Nothing in your project changes.