# Settings

The settings can be found in *Project Settings -> Binding System*.

<figure><img src="https://3780647524-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnpeBTRzgLGSQUWVhwqoi%2Fuploads%2FKBXsSPE36USfWVIbvAzH%2Fimage.png?alt=media&#x26;token=e3b97f0d-71ea-4ff9-a770-2455d800620f" alt="" width="563"><figcaption><p>Settings Page</p></figcaption></figure>

Here is a short description of each settting:

* **Show Target Group Replacement**: whether to show or not the bind source replacement controls, that is, Group Rebinding.<br>

  <figure><img src="https://content.gitbook.com/content/npeBTRzgLGSQUWVhwqoi/blobs/4negtM2NJ3ZlLv4v2NfB/Settings_ShowTargetReplacement.png" alt="" width="375"><figcaption><p>Target Replacement</p></figcaption></figure>
* **Realtime Debug:** if true, the Live Debug will update with at least 60Hz, otherwise it will update only when Inspector refreshes.
* **Show Last Used Sources**: if true, the last 4 used objects will be shown in binding menu. This is a quality of life option, although it may contribute to menu clutter.
* **Show Last Used Pins**: if true, last assigned pins will be visible directly in binding menu.
* **Max Bind Path Depth**: when selecting members to bind, how deep the dropdown allows to navigate. A higher depth means gives more flexibility at the cost of performance during dropdown popup.
* **Auto Conversion**: enables an automatic logic which detects field type change and reserializes its value to keep the data consistent. For more info refer to Bind Types Reserialization section.\ <mark style="color:orange;">This options is hidden behind a compilation flag:</mark> <mark style="color:orange;"></mark><mark style="color:orange;">`BS_LEGACY_SUPPORT`</mark>
* **Phased Bindings:** enables phased bindings updates. It improves performance by up to 30% for complex bindings setups. For simple setups, it will have around 5% - 10% improvements over the classic logic, but this improvements can increase significantly for pipelines that include multiple modifiers and/or converters. Since this changes quite a lot the underlying logic, for now it is marked as Experimental, even if all tests have passed successfully.
* **Proxy Binding System:** here are stored all settings for Proxy Bindings objects
  * **Show Proxy Bindings**: if true, the proxy bindings objects will be shown in the inspector: ProxyBinding Component and/or Asset will be visibile and some adjustments can be made when something goes wrong with bindings.
  * **Default Bind Data**: this serves as the template for new bindings.

    <figure><img src="https://3780647524-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnpeBTRzgLGSQUWVhwqoi%2Fuploads%2FFUPfPBgKbQbwFI947kVV%2Fimage.png?alt=media&#x26;token=cb896710-8266-4a6c-ae63-33e02e125dba" alt="" width="563"><figcaption></figcaption></figure>
* **Pinned Manager:** here all pinned fields and objects are categorized and shown. From here these pins can be removed as well. Check the [**page dedicated to pinning**](https://postica.gitbook.io/binding-system-2/product/pinning-fields).
* **Fields Routes**: here all re-routed fields will be visible. Check [**this page**](https://postica.gitbook.io/binding-system-2/product/extending-the-system/bind-rerouting) for more details.
* **Refactor Manager**: options related to [**refactoring**](https://postica.gitbook.io/binding-system-2/product/troubleshooting/refactoring) may be changed here.
* **Dependencies Window**: options related to [**dependencies window**](https://postica.gitbook.io/binding-system-2/product/troubleshooting/bindings-dependencies) can be changed here.