fix(web): force CPU compositor preview evaluation
Some checks failed
M6 deployable RC / quick (push) Has been cancelled
M6 deployable RC / chromium (push) Has been cancelled
M6 deployable RC / release (push) Has been cancelled

Temporarily select the CPU compositor device for the embedded preview so the
GPU-context requirement no longer aborts. A valid RGB→Composite graph still
returns COMPOSITOR_RESULT_MISSING; recorded as a residual.

Co-Authored-By: Claude Code <noreply@anthropic.com>
This commit is contained in:
mes123456
2026-11-14 07:48:55 +08:00
parent 71a8e8c95e
commit fe253bd9b2
8 changed files with 236 additions and 15 deletions

View File

@@ -456,6 +456,17 @@
`INVALID_ARGUMENT: COMPOSITOR_NODE_GROUP_MISSING: scene has no
compositing node group`。此前错误对象被渲染为 `[object Object]`,已在
`App.tsx` 规范化 code/message;证据 `probe-compositor.mjs`。
- Compositor 求值(2026-11-14 深挖):
- 提交图后调用 `WASM 合成求值` 曾报
`Browser draw manager must be created once per WM canvas`;已在
`web_engine_blend_main_compositor_evaluate` 中临时把
`scene.r.compositor_device` 切到 CPU(求值后恢复),消除该 GPU
上下文依赖(WASM `198d2f01...`)。
- 用正确命令 `setCompositorNodeGraph` 提交 `RGB → Composite` 图(原生
树确认为 `CompositorNodeRGB.Color → NodeGroupOutput.Image`)后,
`compositorEvaluate` 仍返回 `INVALID_ARGUMENT: COMPOSITOR_RESULT_MISSING`。
这是当前 WASM 合成求值的真实残余阻塞,需要补齐 RenderResult/
have_combined 初始化;证据 `probe-compositor-eval.mjs`。
## 下一动作