> For the complete documentation index, see [llms.txt](https://postica.gitbook.io/binding-system-3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://postica.gitbook.io/binding-system-3/project-tools/diagnostics.md). # Diagnostics Answering questions about bindings, from one field to a whole project. A binding is quick to make. That is the point, and it is also the risk: a real project ends up with thousands of them, spread across scenes, prefabs and assets, made by several people over several months. The tools in this section exist because of that. All of them are editor only, and none of them cost anything in a build.
Diagnostics by scope
## Pick by the question
Live DebugWhat value is the binding producing, and where did it go wrong?Live DebugScreenshot 2026-09-28 at 17.33.30.png
Path Value PreviewWhat is at the end of this path before I commit to it?Path Value PreviewScreenshot 2026-09-28 at 17.38.19.png
Error VisualizationWhy is this field red?Error VisualizationScreenshot 2026-09-28 at 17.40.15.png
Bindings MonitorWhat is running, how often, and what does it cost?Bindings MonitorScreenshot 2026-09-27 at 18.25.26.png
Scene VisualizerWhat drives this object in the scene in front of me?Scene VisualizerScreenshot 2026-09-28 at 17.50.19.png
Bindings DependenciesWhere in the project is this member bound?Bindings DependenciesScreenshot 2026-09-28 at 18.02.11.png
Dependency GraphWhat is connected to what across the project?Dependency GraphScreenshot 2026-09-28 at 18.03.24.png
Bindings ValidatorIs anything in this project broken?Bindings ValidatorScreenshot 2026-09-27 at 11.48.26.png
RefactoringI renamed something. How do I repair the bindings?RefactoringScreenshot 2026-09-28 at 18.15.25.png
ReserializerI changed a field to Bind<T>. How do I keep its saved values?Reserializercover-reference.svg
## The order to reach for them **While authoring one binding**, the two switches on the row are enough. Turn on the [preview](/binding-system-3/project-tools/diagnostics/path-value-preview.md) to check a path without leaving edit mode, and turn on [Live Debug](/binding-system-3/project-tools/diagnostics/live-debug.md), then press play, when the result is not what you expected. [Errors](/binding-system-3/project-tools/diagnostics/errors.md) announce themselves either way. **While finding your way around a scene someone else built**, turn on the [Scene Visualizer](/binding-system-3/project-tools/diagnostics/scene-visualizer.md). It draws every binding of the open scenes as an arrow, in the Scene view, and answers "what drives this object?" without opening a single Inspector. **While tuning a scene**, open the [Bindings Monitor](/binding-system-3/project-tools/diagnostics/bindings-monitor.md). It is the only tool that shows cost, and it makes an expensive binding obvious in seconds. Leave it open and the [Scene Visualizer](/binding-system-3/project-tools/diagnostics/scene-visualizer.md) puts the same measurements on the objects themselves, as a heat meter per object. **Before a release, or after a refactor**, run the project-wide tools in this order: the [Validator](/binding-system-3/project-tools/diagnostics/validator.md) to find what is actually broken, [Refactoring](/binding-system-3/project-tools/diagnostics/refactoring.md) to redirect what a rename broke, [Dependencies](/binding-system-3/project-tools/diagnostics/dependencies.md) to see everything that exists, and [Optimized Accessors](/binding-system-3/project-tools/performance/optimized-accessors.md) to see what the build can turn into direct code. The first two are a pair. The validator finds the bindings whose member is gone; the refactor window takes them and redirects all of a member's bindings in one decision, including the ones in scenes nobody has open. ## Where they live
MenuWhat it opens
Window ▸ Binding System ▸ Bindings MonitorBindings Monitor
Window ▸ Binding System ▸ Bind Scene Visualizer, or the Bind Visualizer overlay in the Scene viewScene Visualizer
Window ▸ Binding System ▸ Bindings DependenciesBindings Dependencies
Window ▸ Binding System ▸ Bindings Dependency GraphDependency Graph
Window ▸ Binding System ▸ Bindings ValidatorBindings Validator
Window ▸ Binding System ▸ Validate Active Scene, Validate Whole ProjectBindings Validator, starting a run straight away
Window ▸ Binding System ▸ Bind VariablesBind Variables
Right click a GameObject, component or asset ▸ Binding ▸ Show DependenciesDependencies, scoped to what you clicked
Right click a GameObject, component or asset ▸ Binding ▸ Validate BindingsValidator, scoped to what you clicked
Project Settings ▸ Binding System ▸ ToolsAll of them, with a description each
Every one of them is also listed, with its purpose, in [Windows, Menus and Components](/binding-system-3/reference/windows-and-menus.md).