Skip to content

Analyzer and evidence ​

ShaderPackAnalyzer validates packs with the production Loader and explains schemas, resource graphs, scene routing and public interfaces. It helps identify structural and semantic problems before you run the game.

Get the current tool ​

The pinned tool distribution is docs-tools-f8aaa5c4-w1.1, for Windows x64 with a self-contained .NET runtime. Its binary assets currently reside in a GitHub Release that requires read access; an anonymous download is not yet available.

Source is available from the public Gitea repository. To build it yourself, check out the baseline commit and follow the upstream Analyzer README using the .NET 10 SDK. The commands below assume you already have a version-checked shaderpack-analyzer.exe.

Source: Analyzer build, distribution and command documentation · f8aaa5c4

Start with pack validation ​

powershell
shaderpack-analyzer.exe pack validate ./MyPack --format json

Check the exit code, valid and diagnostics first. Fix the reported file, JSON pointer, resource or program ID, then request a more specific explanation.

In these commands, ./MyPack is your own pack directory, not a downloadable example provided by this website.

Choose a command for the question ​

powershell
shaderpack-analyzer.exe scene explain ./MyPack --include-inactive --format json
powershell
shaderpack-analyzer.exe graph dump ./MyPack --contract 2 --include-inactive
powershell
shaderpack-analyzer.exe program interface ./MyPack --program "yourpack:post/present" --contract 2
powershell
shaderpack-analyzer.exe data interface ./MyPack --format json

Replace yourpack:post/present with a Program ID that exists in your pack. For the v5 Program interface, explicitly select contract 2; omitting it may still select an older interface projection.

What each successful check establishes ​

ResultWhat it establishesEvidence still needed
Schema validation passesStructure satisfies the corresponding schemaLoader semantics and versioned behavior
Loader validation passesThis pack passes the current loading and semantic checksDriver compilation, linking and resource creation
Offline graph / interface succeedsActive relationships and interfaces can be explained for the selected inputsAn actual device and game context
Valid driver reportDevice observations exist for the matching identityScene, lifecycle and visual acceptance
Game visuals and performance verifiedObservations for a particular device and sceneCoverage of other devices and configurations

The current documentation baseline retains driverStatus=notProvided, mappingStatus=deferred, runtimeEvaluated=false and liveWorldVerified=false. An offline success does not change those fields into claims of real-device verification.

A real diagnostic: DLTOOL2001 ​

Running docs verify-v5 on the original v5 guide reports DLTOOL2001: triple-backtick code blocks in a reconstructable guide require a language marker and file=<relative-path>. The guide contains an explanatory JSON block that does not meet this extraction contract.

The website retains that original failure and provides an independently identified dawnlight-v5-guide-site-v1 variant. The variant changes only the explanatory block's fence and adds an identity note. The seven file blocks remain unchanged, and extraction matches the pinned example exactly.

When a diagnostic appears, check the input document's purpose and code-block contract. A derived version passing a check does not mean the original input passed.

Source: Diagnostic code reference · f8aaa5c4

A repeatable investigation ​

  1. Record the host commit, Manifest/ABI version, exact source inventory and options. Run pack validate and fix the first error at its file and RFC 6901 JSON pointer.
  2. Use scene explain to confirm route ownership and fallback. Inspect graph resources, active commands and Program closure, then Program interface with contract 2 for v5.
  3. Load that exact source in a creative world. Export the current published generation's reports and match pack/source/options before interpreting device evidence.
  4. Repeat the failed command after repair, then reload, resize and return to BuiltIn. Keep old reports as history.

The configuration repair lab supplies three complete expected-rejected ZIPs with observed DLMAN0001, file/pointer, failed graph/interface queries and successful repairs. The symptom index links seven investigation paths.

Exits and option transport ​

Exit 0 means the requested check succeeded; 1 means contract or input failure, and 2 means command misuse. Inspect diagnostics even on exit 0. Read code, file and jsonPointer together; an empty pointer can describe the whole request. Fragment diagnostics retain the real fragment provenance. Never infer DLABI1002 merely from an unknown Provider name: the lab's actual code is DLMAN0001.

The option file is a JSON object keyed by full option IDs. Match boolean/integer/number types to the declaration. This pinned parser distinguishes integer and floating JSON tokens: use 1.0 for a number endpoint instead of an integer 1. Scene, Program interface and Data commands accept --options. Graph CLI on this baseline does not consume that override: request dawnlight/dumpGraph over JSON-RPC with contract 2 and explicit inputs.options. Do not label a default CLI graph as the selected branch.

Schema and editor association, WorldFinal snapshots and Scene/Data reports complete the workflow. Program interface contract 2 consumes a Data report; driver-report inspect consumes a Scene report. A report of the wrong kind is a contract error, not proof of a shader defect.

Author documentation · Manifest v5 / Scene ABI v2