2 Commits

Include renames

Author	SHA1	Message	Date
rootandClaude Fable 5.1	0e5e5ef925	Shaders draw in the sprite's own pass: a Mesh with the graph's fragment, no filter (#77) ... A sprite's picture is now a Mesh (unit quad, sibling of its Graphics node, which keeps only the hit area); a worn shader replaces Pixi's fragment in that draw, so there is no intermediate texture and no extra render pass. Measured on the HD 630: 400 shaded sprites hold 60 fps (was 34), 800 hold 56 (was 20). Two Pixi facts the code leans on: a mesh's texture is bound only for Pixi's own shader, so GraphShader.wear hands it over; and MeshPipe caches whether a mesh batches and re-checks it only in a frame without structure changes, so switching a shader on or off calls mesh.unload(). The console panel mirrors console.group/groupCollapsed/groupEnd and fills the %s %d %o %c directives, so Pixi's deprecation warning shows its head, not only its stack. E2E 12 guards against the addChild-on-Graphics warning, 28 counts shaders instead of filters. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>	2026-09-13 15:31:08 +02:00
rootandClaude Opus 5	82effb2c03	Shader performance: measure one filter pass per sprite (#67) ... The wiki carried an estimate ("fine for dozens, not for thousands"). Measured on the Intel HD 630 that CI uses, 48x48 sprites in a 640x360 camera, neutral values, three runs agreeing to 1 fps: sprites 25 50 100 200 400 800 fps 58 56 54 48 34 20 The same scene without shaders holds 60 fps at every one of those counts, 800 included. Quadrupling the sprite area (96x96) measures the same, so the cost is the render target switch, not the pixels: roughly 20 us per pass up to 200, 40 us at 800. tools/perf-shaders.mjs drives it (not run in CI, frame times are machine dependent). New hook __gm.filterCount() counts visible nodes carrying a filter and proves one pass per sprite; e2e 28 checks it. Two traps the tool guards against, both cost a wrong answer first: the median frame time is useless here (the distribution is bimodal under vsync, so the rate comes from frames/duration), and --disable-gpu-vsync has no effect in headless, so what is measured is the point where the frame rate breaks down. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-13 14:41:35 +02:00