Troubleshoot by symptom
Choose a symptom
- Pack missing, failed to load or still looks old
- Black/white frames, missing sky or transparency
- MRT outputs and binding conflicts
- Feedback, writers, ordering and barriers
- Resize, stale pack state and history trails
- Missing Mod material matches and deferred mapping
- Static success but compile/link or FBO failure
Record first, then narrow the cause
Record host commit, pack/ZIP fingerprint, options, selection, published generation, actual extent, world/Mods, GPU/driver and the first error. Run pack validate, then scene/graph/interface, then compare the corresponding report and appearance. Avoid changing host, world, source and options together.
The repair lab includes three complete ZIPs clearly marked as negative examples. Source and fresh ZIP were rejected, then passed after restoration.
Use codes and provenance
Use stable codes/families and file/pointer for location. English messages supply context. One symptom can come from several layers and one family from several sources. See diagnostics and Analyzer for codes and exit contracts.