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): one vocabulary, and what it caught
esengined4af3f3ec021
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 13e36759b..3d7724b2c 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -53,6 +53,20 @@ published separately; it ships inside the editor.### Added+- **One attribute vocabulary for both vertex sources.** The 2D batch reads+ `0=position, 1=color, 2=texCoord`; the mesh channels were written+ `0=Position, 1=TexCoord0, 2=Color`. Neither was wrong alone, which is the+ problem — a shader written against one samples the other's colour as a UV, and+ only the frame says so. `MeshChannel` now matches the batch for its first+ three, and the engine's own uploads name their channels by semantic rather+ than repeating literal locations.++ This also closes something the resident path opened: a material's shader is+ built for the batch vertex source, so drawing GPU-resident geometry with one+ would place it at its local origin and leave the instance attributes+ unconsumed. Until a material can be compiled FOR this vertex source, the mesh+ program wins and the material is reported once rather than silently obeyed.+- **A mesh's normals light it.** `applyLighting2D` has always taken a normal —the 2D path passes it the constant (0,0,1), because a sprite has no other — andLight2D already carried Point, Directional, Ambient and Spot with a position