Use when adding visual effects to a PlayCanvas app, to choose between particle systems, shader chunks, runtime meshes, and post-processing.
中文简介正在准备中。当前显示原文说明。
Use when reading state from a running PlayCanvas app, to reach its live Application through the Engine devtools hook without changing app code.
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
From Engine 2.23, every app announces itself to a hook at
globalThis[Symbol.for('playcanvas.inspector')]. Read live state through it instead of adding
window.app or debug code to the app.
scripts/devtools-hook.js relative to this skill and inject it as an init script that
runs before any page script. A hook defined later misses existing apps; reload instead.globalThis.__playcanvasApps, a Map from each live app to
{ version, revision, protocol }. app.init() adds the entry and app.destroy() removes it.devtools: false. The Engine swallows errors thrown by the hook.playcanvas/debug, build/playcanvas.dbg.*) announces apps; the
default import never calls the hook. Later 2.23 patches fix every build.frameend, so values reflect a rendered frame.app.root.findByName() and findByTag(), world positions and
meshInstance.aabb, app.stats.drawCallCount and frameTime, and
entity.anim.baseLayer.activeState.app.timeScale = 0; update still runs with a zero dt. Step one frame by restoring
the scale, then zeroing it again on the next frameend.@playcanvas/inspector adds a panel for people: new Inspector(app) shows the hierarchy, assets,
materials, shaders, textures, render targets, frame graph, and physics. It must import the app's
own playcanvas package, so add it only to development builds. It draws over the canvas and
applies view overrides, so destroy it before verify-pixels captures. Stepping through draws
needs the debug build.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Use when adding visual effects to a PlayCanvas app, to choose between particle systems, shader chunks, runtime meshes, and post-processing.
中文简介正在准备中。当前显示原文说明。
Use when writing PlayCanvas Engine code touching transforms, cameras, lights, materials, meshes, bounds, or imports, to apply Engine conventions and avoid legacy APIs.
中文简介正在准备中。当前显示原文说明。
Use when composing PlayCanvas entity hierarchies from models, colliders, rigid bodies, and scripts, so each object has one semantic root and clear lifecycle.
中文简介正在准备中。当前显示原文说明。
Use when static PlayCanvas lighting, shadows, or ambient occlusion cost too much per frame and should be baked into lightmaps.
中文简介正在准备中。当前显示原文说明。
Use when creating or restructuring a PlayCanvas app with the Engine API, @playcanvas/react, or @playcanvas/web-components, covering bootstrap, input, resize, physics, update loop, UI, and lifecycle.
中文简介正在准备中。当前显示原文说明。
Use before repeatedly placing GLB models in PlayCanvas to record each asset's uniform scale, grounding offset, pivot compensation, and yaw once.
中文简介正在准备中。当前显示原文说明。