Logs & diagnostics

Where DNA writes its records, and what to grab when you need to report a problem.

The Console

Most of what you need while working is right in the Console panel. It streams messages as you go — info, warnings, and errors — each tagged with a category and a time. When something doesn't behave, the Console is the first place to look: a failed file load, an unsupported input, or a node refusing to run will usually announce itself here. You can filter by severity and search the text.

Log files

DNA also writes a rolling log to disk, so there's a record even after you close the app or if it crashes. This is the file to attach when you report a bug — it captures far more detail than fits in the Console, including what happened in the moments before a crash.

If DNA crashed, a crash report is written automatically and its location is printed to the Console on the next launch. Grab that file plus the log when you file a report.

Reporting a problem

When something's wrong, a good report makes it fixable fast:

  1. Note what you did and what you expected vs what happened.

  2. Copy any red error text from the Console.

  3. Attach the log file (and the crash report, if there was a crash).

  4. If you can, include the project (or a trimmed-down version that still shows the problem).

Performance vs correctness

If the issue is slowness rather than a failure, the Performance panel is the better tool — it shows frame time and memory pressure so you can see what's heavy. Logs are for things going wrong; the Performance panel is for things going slow.

See also