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.
TypeScript 2d-game-engine3d3d-game-engineandroidcppecsgame-editorgame-enginegamedeviostypescriptwebassemblywebglwebgpuwechat-minigame
docs(changelog): the frame has one GPU timer, and the notes say so
esengine0a0033ee0654
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex ff04f1c3b..28563e1b9 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -117,9 +117,18 @@ published separately; it ships inside the editor.`RenderGraph` compiles unconditionally now rather than behind`ES_ENABLE_POSTPROCESS` — the frame declares its own passes to it whether or- not a post stack was built in. The frame's GPU time is the graph's, not the- submit timer plus the chain: the scene runs inside the graph, so adding them- would have counted it twice.+ not a post stack was built in. The frame's GPU time is the graph's, because the+ scene runs inside it.++ That is now the frame's ONLY GPU timer, and `render.submit` is no longer+ reported as a GPU scope. A second timer opened around the scene sat inside the+ graph's own span, which is not a thing either backend does: GL has one global+ `TIME_ELAPSED` target, so the inner query failed to open, the inner `endQuery`+ closed the OUTER one, and both numbers were wrong; WebGPU says nothing and let+ the two drain one queue in turns, each reporting whichever pass came next. The+ scene's own share was never a nested region — it is a pass of the graph, and a+ per-pass question. Nothing read the `submit` key, and one that always read -1+ was worse than an absent one.- **An effect can read the scene's DEPTH.** Nothing could: the depth attachmentwas written every frame and sampled by nothing, and on WebGPU it was not even