Three engine adapters
Strict patterns recognize common Unity, Unreal Engine, and Godot compiler messages. Lines that do not match stay unknown.
OFFLINE SHADER BUILD TRIAGE
Find the signal in your
shader compile logs.
Review known diagnostics from Unity, Unreal Engine, and Godot. Group repeats, search the log, and export a report — your file stays in this tab.
Local onlyNo upload · No account · No dependencies
01 / INPUT
Choose a build log
0 / 20 MiB
02 / REPORT
Diagnostics overview
| Level | Engine | Diagnostic | Source | Line | Count |
|---|
No diagnostics match these filters.
Recognized patterns are heuristics. A grouped message is a repeated log line, not proof of a unique root cause. Review the original log before acting on a report.
Repeat grouping
Equivalent diagnostics are grouped by normalized fields. The report keeps first and last line numbers and the original first line.
Evidence, not guesses
CPU time is labelled as CPU time. Variant-space totals are kept separate from compiled counts. No predicted causes or build-time totals.
SCOPE
What ShaderTriage can and can’t tell you
- Reads one text file or pasted text up to 20 MiB.
- Never edits source files or sends log content anywhere.
- Parser coverage is version-dependent and incomplete.
- It does not compile shaders, inspect project assets, or establish root cause.