Skip to content
Resource

Troubleshooting

Most issues come down to Scenario scope, Play Mode timing, or expectations about what was captured. Work through these in order.

Common situations

Recording will not start

If validation says recording cannot start, trust it and resolve the listed issues first.

  • First Run Scenario Validation and fix blockers
  • Then Confirm the Scenario has meaningful Tracking targets
  • Then Check Preferences for recording constraints
  • Finally Restart the window and review Scenario Console messages

Report is empty or thin

Thin Reports are usually a setup problem, not a product failure.

  • Tracking too narrow Track the owning type or caller boundary
  • No Watches Add a Watch on the symptom member
  • No Probes Enable relevant environment probes
  • Profile too light Move from Minimal toward Standard or Deep
  • Missed window Record a cleaner, shorter take

Report is too noisy

Noise is a signal that the Scenario needs editing, not that you should read harder.

  • Reduce Shrink the Tracking surface area
  • Prefer Track Public Only on large types
  • Disable Probe categories that are irrelevant
  • Shorten Record a briefer take
  • Filter Use Timeline and Flow filters such as Hide Tiny

Causal Flow is incomplete

Confirm each of the following, then re-record. Causal Flow quality follows Scenario quality.

  • Watch The member is actually watched
  • Timing The write occurred during the recording window
  • Tracking Includes the methods that should appear in the chain
  • Depth Profile supports the detail you expect

Watch values look shallow

Verify the Watch is enabled, increase Profile depth for the next take, and review Preferences under Watches. Prefer watching the decisive member rather than an enormous parent object on first passes.

Probe Map has little activity

Confirm Probes are enabled on the Scenario and that the reproduction actually triggered those environment events. Check Probe Preferences, then re-record while deliberately causing the scene, object, animator, or resource event.

MindBoard item did not appear

Use Reveal in MindBoard if the reference may already exist, confirm you used Add to MindBoard from the intended surface, refresh the workspace, and verify you are on the expected active board.

Tasks scanner finds nothing

Confirm markers use supported forms such as TODO, FIXME, HACK, BUG, and NOTE. Refresh or rescan from the Tasks tab, ensure scripts are under Assets, and clear filters and search text.

Sketch disappeared after restart

Sketch strokes persist with the board. Confirm you were drawing on the intended board, avoid clearing without noticing the confirmation, check Storage diagnostics if broader persistence looks wrong, and reopen MindBoard after a domain reload once compilation has finished.

Database or persistence concerns

Open Preferences under Storage, reveal the database folder and confirm Library/TraceMind exists, compact if the project is old and heavy, and reset only after exporting anything you must keep.

Still stuck?

Gather details

Open About and copy details, and export Scenario Console output if relevant.

Note versions

Record your Unity version and TraceMind version.

Report it

File through the public issue tracker.

Getting Started Scenarios Preferences FAQ