Repository navigation
Threedog 1.3.0
Threedog 1.3.0: WebGPU failures now name their cause, and a showcase scene can start without content.
npm install threedog@1.3.0 @threedog/tools@1.3.0Every change is in the changelog.
Fixed on WebGPU
- The engine asks the device for the adapter's own buffer, storage, texture and sampler limits instead of WebGPU's defaults.
voxelGIon a scene of a million triangles or more no longer fails every frame withBuffer size exceeds the max buffer size limit. sunShaftscompiles on D3D backends that use FXC. Shadow map compares are written astextureSampleCompareLevel(same picture), listed indescribe().threePatchesascompare-sample-level.- A post effect whose own pass the device refuses to build is held off and the frame draws without it.
describe().render.postshowson: falsewith the reason, and the page error has the codepost-effect-failed. Before, the effect showed as on while every frame was invalid. - A material that binds more textures or samplers per shader stage than the device allows stops at its build with a
texture-bindingserror naming the material, the mesh and the counts, instead of the device'sInvalid PipelineLayout.
New
threedog init --scene-onlystarts a showcase scene with a camera,picture/, start screen, autosave and Esc menu, and nocontent/and noassets.js.views.show({ position, target, fov })shows a pose with no view declared.threedog state view=x,y,z,tx,ty,tz[,fov]places the camera on a running page beforethreedog snap.
Changed
engine.budgethas a default guide of 7 forshadowMaps(a point light is six maps). Nothing is cut at it;engine.budget.enable({ shadowMaps: n })sets your own. The picture check prints the frame's triangles with it.
Tested on Chrome on Windows (D3D) with real WebGPU, one NVIDIA laptop GPU. Holding a refused post effect was run on that machine only. An effect that is only an expression, with no pass of its own, is still named by material only and is not held.