Skip to content

A fast 2D and 3D game engine — TypeScript SDK, C++/WebAssembly core, visual editor. Ship one project to web, desktop, WeChat MiniGames, playable ads, and native Android / iOS.

docs(changelog): the picture comes back after the GPU is lost

esenginedd206138d178
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 8b1315c81..7442a540e 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -16,6 +16,14 @@ published separately; it ships inside the editor.
### Fixed
+- **The picture comes back after the GPU is lost.** When the graphics context went away — a
+ driver reset, Chrome's GPU process crashing on Windows, a laptop switching GPUs — the
+ engine reported "Device recovered" while the view stayed blank or came back without its
+ grid, meshes, materials or text. Each part of the renderer rebuilt its own GPU objects,
+ and the ones nothing rebuilt drew with dead handles. The device now rebuilds everything it
+ issued behind the same handles, puts back the contents it kept, and reloads the rest from
+ their assets, on WebGL2 and WebGPU alike.
+
- **A hot update on iOS, Android and desktop builds is still there after a restart
without a network.** The native host only stores cache files under plain names, and
hot update asked to store each downloaded asset under its full URL; every write was
diff --git a/tools/releaseNotes.mjs b/tools/releaseNotes.mjs
index e2b5c2a45..78e4e5a0b 100644
--- a/tools/releaseNotes.mjs
+++ b/tools/releaseNotes.mjs
@@ -28,6 +28,9 @@ export const NOTES_FLOOR = 'v0.65.0';
* the reader recognises anyway.
*/
export const NOTED = {
+ 'fix(render): the device rebuilds every object it issued behind the same handle':
+ { note: 'The picture comes back after the GPU is lost.' },
+
'fix(render): a vertex stage names gl_InstanceID only after its attributes':
{ note: '3D meshes draw on Windows with WebGL2 again.' },