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
chore(editor): pin the SortingGroup and SpriteMask pixel checks
esengine1ee3783fe0d8
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 0716da687..7c95f62e8 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -85,7 +85,10 @@ published separately; it ships inside the editor.What a frame CAN show is held by the `sprite-mask` pixel scene: one mask, both itssides, and a bar that never asked to be cut. Dropping the resolver paints the frame- red; mapping `TestOutside` to Equal leaves the right half black. And `space-shooter`+ red; mapping `TestOutside` to Equal leaves the right half black. An editor check+ carries it the rest of the way — through the scene file, the reconciler and the Add+ Component list — and asks what no picture can: that the component can be added at+ all, and that its range fields stay hidden until `limitRange` turns them on. And `space-shooter`now draws its hull as one, because a capability no game has called is a promise withnothing behind it — the fill is cut rather than scaled, so the art never stretcheswith the number, and the lost segment is the same mask's other side.@@ -115,10 +118,11 @@ published separately; it ships inside the editor.group and inside one replaces a projection (depth, shader, world Y) the author'sorder was overriding anyway.- Held at three levels, each watched failing first: the bit layout in a new header-only- `test_sort_key` harness, the draw path's resolution in `test_batch_builder`, and the+ Held at four levels, each watched failing first: the bit layout in a new header-only+ `test_sort_key` harness, the draw path's resolution in `test_batch_builder`, theeditor's picking — which mirrors all of this in `layerOrder.ts`, or a click selects- what the person cannot see. Two of the engine cases were TRIVIALLY satisfied when+ what the person cannot see — and an editor check on real pixels, where a member whose+ own layer would put it on top is drawn underneath and a click agrees. Two of the engine cases were TRIVIALLY satisfied whenfirst written (a stated order outranks both depth and world Y, so it cannot be whatmakes two layer rules disagree) and were rebuilt until sabotage reddened them.diff --git a/desktop b/desktopindex 6eb4424eb..da03743a9 160000--- a/desktop+++ b/desktop@@ -1 +1 @@-Subproject commit 6eb4424ebed6c6a29314c18caa64a3dbf66b3519+Subproject commit da03743a9a67f460fc9c072ca7b9bc8633d3c5bd