> 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/help/troubleshooting.md). # Troubleshooting Symptom, cause, fix. ## A binding does nothing

Check	Why
Is the bind toggle actually on?	Check this first. An unbound field uses its plain value and looks normal. Note that Enable Binding alone does not bind a field: it adds the hexagon, and the hexagon has to be on. Switching it off keeps the setup, so a binding you configured and then toggled off is still there, just idle. See Proxy Bindings.
Is there an error on the row?	See Error Visualization. Hover the error point.
Does it have an update point?	A proxy binding needs one, and a new one starts with UPDATE already ticked, so this is only a problem if it was unticked or the project default was changed. Before treating an empty panel as the bug, check whether the binding is meant to be driven from code or by a `UnityEvent`, in which case the panel is correct and the missing piece is the call. A `Bind<T>` resolves when your code reads it, so check that your code reads it.
Is the mode right?	A `Read` binding will not push a value out. Click the mode icon.
Is the source resolving?	Name, tag and pattern modes show a status light. Red means nothing matched.
Is it paused?	Check the Bindings Monitor with Show Inactive on.

Turn on [Live Debug](/binding-system-3/project-tools/diagnostics/live-debug.md) and the answer is usually visible immediately. If it is more than one binding, or you would rather be told than go looking, run the [validator](/binding-system-3/project-tools/diagnostics/validator.md) over the scene. It resolves every binding the way the runtime would and names the ones that cannot work, which covers most of the table above in one pass. ## The value is wrong, not absent Live Debug shows every stage. Read it top to bottom and find the first stage whose output surprises you.

The wrong value appears at	What it means
The path stage	The path points somewhere other than you thought. Turn on the preview and re-check.
The converter	An unsafe conversion is falling back. Check the fallback value and the input.
A modifier	Check the order. Clamp then remap is not remap then clamp.
The output only	Something else is writing to your field after the binding does. Look for another binding, or your own code.

## Two things fight over one value Symptom: the value flickers, or one control appears to be ignored. Usually two bindings write to the same target, or a binding writes to something your `Update` also assigns. The [Dependency Graph](/binding-system-3/project-tools/diagnostics/dependency-graph.md) with the target in **Focus** shows every binding pointing at it. For a value that genuinely has several controls, that is what **Link To Bindable** and **Set Value** are for. See [multi-controlled values](/binding-system-3/pipeline/modifiers.md#multi-controlled-values). ## It works in the editor, not in a build

Cause	What to do
The binding used the EDITOR update point only	That point does not exist in a build. Add a real one.
The source is an editor-only object	Nothing in `UnityEditor` exists in a build. Static source mode already filters those out, but a direct reference can still be wrong.
Code stripping removed the member	Add a `link.xml` entry, or lower the managed stripping level.
The scene is not in the build	Check the Build only filter in Bindings Dependencies.

## An exception in the Console, from a binding Binding System prefixes its own log output, so filter on that first.

Message shape	What to do
Null somewhere in the path	Decide what you want: Propagate Nulls on to get a default and silence, or off to keep the error. See Nulls along the path.
is not write enabled	Something wrote to a `Read` binding. Check the mode, or guard with `CanWrite`.
An exception inside a converter or modifier	Turn on Live Debug: the exception is shown at the stage that threw, with its stack trace.

## The bind path menu is empty, or missing what I want

Cause	What to do
Nothing on the source can feed this type	The menu only lists compatible members. Check the field's type, and whether a converter exists for the pair.
Methods are hidden	Turn Methods back on in the Visualization panel.
The member is hidden by an attribute	`[HideMember]` on the member, or a global filter. See Attributes.
The path is deeper than the limit	Raise Max Bind Path Depth, or bind in two hops.
The mode restricts it	A read-only binding does not list write-only members, and the reverse.

## Bind fields draw as raw serialized data The editor assembly did not load. Check the Console for compile errors and reimport the package. With Odin installed, see [Odin Inspector](/binding-system-3/reference/integrations/odin-inspector.md). ## The project-wide tools see less than expected The scanner reads serialized YAML, so **Project Settings ▸ Editor ▸ Asset Serialization** has to be **Force Text**. Under Force Binary or Mixed you get the [legacy window](/binding-system-3/project-tools/diagnostics/dependencies.md#the-legacy-window) instead, which only sees objects that are currently loaded. If serialization is already text, delete `Library/BindDB.json`, `PrefabsDB.json` and `BindDeltaDB.json` and reimport. They are caches. ## Renaming broke things Start by running the [validator](/binding-system-3/project-tools/diagnostics/validator.md) over the whole project. It names every binding a rename broke, including the ones in scenes nobody has open, which is the half that used to go unnoticed.

Case	What happens
A field or method rename	Reported as Path no longer exists. Refactoring redirects every binding of that member in one decision. Use Refactor renamed members in the validator, and check that Enable Refactoring is on.
A class rename	Reported as Source type no longer exists. Refactoring works on members, not on the type a binding starts from, so this one is repointed by hand: assign a source of the new type, or switch the binding off.
A converter or modifier class rename, or a namespace or assembly move	Orphans every saved instance. They are stored by class name through `[SerializeReference]`, so there is no path to rewrite. Reported as Modifier type is missing or Read converter type is missing; pick the modifier or converter again, or restore the old class name.
A converter or modifier `Id` rename	Safe. The `Id` is a menu label and a registry key, and is never written into the saved data.
A generated standard modifier class rename	Same as any other modifier class rename: it orphans the saved instances. Do not rename that file or its classes.

## No binding counts in VS Code or Rider The extension reads `Library/BindingSystem/IdeIndex.json`, which Unity writes. Check that **Export for IDEs** is on in **Project Settings ▸ Binding System ▸ Configuration ▸ IDE Integration**, that the line under it reports a recent export, and that VS Code was reloaded or Rider restarted since the extension was installed. A binding you just made shows once its scene or prefab is saved. See [VS Code and Rider](/binding-system-3/reference/integrations/vscode-and-rider.md#troubleshooting). ## Performance

Symptom	Where to look
The game is slow	Bindings Monitor, then the tuning order.
The Inspector is slow	Performance Mode.
The bind path menu is slow	Lower the path depth, hide methods.
The Inspector repaints constantly	Turn off Realtime Debug, and check for a binding with Live Debug left on.
Import takes a long time	The dependency database is being built. It settles after the first pass.

## UI Toolkit See the [dedicated table](/binding-system-3/overview/ui-toolkit.md#troubleshooting), which covers every message the UI Builder integration produces. ## Still stuck [Support](/binding-system-3/help/support.md) has the contact details, and what to include so the answer arrives on the first reply.