Diagnosing the engine

First locate the failure: project C#, native engine code or the graphics driver. A C# exception needs its message and stack; use a native debugger for process crashes, hangs or C++ failures.

Reproducible report

1. Copy the project and reduce it to one level and the action triggering the failure.
2. Record OS, GPU, driver, renderer and the exact executable build. Version 1.0.0 alone cannot distinguish builds.
3. Run the console executable with --path <project> --verbose. Add --editor for editor-only problems. Retain the full output, including messages preceding the crash.
4. Use native symbols from that exact build. debug_symbols=yes is a build option, not an installed-editor switch. Rebuilding the working installation is not required here.

Break on the first failure and save thread stacks. The final log line may describe consequences rather than the cause.

Choose a tool

• Memory corruption or undefined behavior: sanitizers.
• Vulkan failures: validation.
• Slow frames without a crash: Tracy or Perfetto.

Useful diagnosis produces a reproducible action and a stack or measurement, not merely a failure disappearing after settings change. A native debugger session was not executed for this guide.