Watches and Probes
Watches follow values. Probes capture the world around your code. Together they replace temporary logs with durable, structured evidence.
This page is a quick overview. For full detail, see the dedicated guides:
At a glance¶
| Tool | Answers | Opens in |
|---|---|---|
| Watch | What value changed, and why? | Watch Studio, Causal Flow |
| Probe | What did Unity's environment do? | Probe Map, Timeline Probes module |
Watches (summary)¶
Pin a member on a Scenario. During recording, TraceMind captures old/new values and optional causal stacks. After recording, use Watch Studio and Causal Flow to investigate writes.
Key rule: Tracking captures execution; Watches capture value change. Configure both for state bugs.
Probes (summary)¶
Enable categories on the Scenario (Scene, Object, Component, Coroutine, Animator, Hierarchy, Resource, Addressables). During recording, environment events appear in Probe Map and Timeline lanes.
Key rule: Enable only categories your bug can touch. Physics toggle does not produce capture data today.
Combined signals¶
| Signal | Best tool |
|---|---|
| A property flipped | Watch + Causal Flow |
| A scene swapped mid-bug | Probe Map Scenes lane |
| An object vanished | Probe Map Objects lane |
| A coroutine raced a write | Watches + Probes + Timeline |
| Animation drove state | Animator probes + Watch Studio |