Skip to content
Warp

Debug workflow

Start with the smallest surface that reproduces the issue:

  1. Run cargo check -p warp_core and cargo check -p warp_editor to separate engine/editor compilation issues from project issues.
  2. Open the project in the editor and inspect Output and Problems.
  3. Verify the selected warp_app.toml, target, asset root, and Cargo package name.
  4. If the picture is wrong, reduce the project to a few RenderContext primitives before debugging atlas or post-processing data.

For runtime behavior, remember that the project owns the Renderer implementation. Warp forwards input and calls render/GUI hooks, but it cannot diagnose project-specific simulation rules. For Android, verify the project hook is reached and inspect platform lifecycle logs around surface recreation and suspend cancellation.

The current repository also includes performance, profiler, shader, Git, terminal, and diagnostic panels. Their presence does not make every integration portable or stable across targets.