Skip to content
Resource

Preferences

Preferences keep TraceMind selective, comfortable, and matched to your project. Open them from the TraceMind window bottom actions.

Preference categories

Exact controls evolve with product updates, so treat this as a map of intent rather than a field-by-field reference.

General

Broad product behavior and defaults that apply across the suite.

Appearance

Visual comfort and presentation options for the TraceMind window.

Scenarios

Scenario workflow defaults, so new playbooks start the way your team prefers.

Recording

Capture behavior and related recording options. Treat anything that makes every recording heavier as a deliberate choice for a hard investigation.

Probes

Environment probe behavior across scenes, objects, coroutines, animator, and resources.

Watches

Watch capture strategies and depth related options. Start here when watched values look shallower than expected.

Flow

Scope Flow and graph playback preferences, including controls that help with dense call activity.

MindBoard

Canvas behavior, zoom sensitivity, and relationship vocabulary, including custom relationship definitions for your team.

Workspace

Workspace chrome and layout related options for how surfaces are arranged.

Storage

Database location and maintenance actions: reveal the folder, compact storage, inspect diagnostics, or reset the project data.

Reset is destructive

Resetting the database removes stored TraceMind investigation data for the project. Export important Reports or notes first if you need them outside Unity.

Guiding principles

Stay selective

If a setting would make every recording heavier, treat it as a deliberate choice, not a permanent default.

Match the question

Lighter Profiles for everyday bugs, deeper snapshot options for nested mysteries, Flow controls for dense call activity.

Scenario first

Many preference problems are really scope problems. Tighten Tracking before maxing global capture.

Updates and About

From TraceMind you can check for updates, open About for version details, and copy diagnostics useful for issue reports. Keep TraceMind current when update prompts appear, especially for investigation-critical fixes.

Leave defaults for week one

Learn the product before tuning anything.

Standardize habits

Agree on Scenario naming and Profile habits before deep preference tuning.

Add custom vocabulary later

Introduce custom MindBoard relationships once the team feels the default set.

Maintain storage

Use Storage compact periodically on long-lived projects.