> For the complete documentation index, see [llms.txt](https://seasidestudios.gitbook.io/seaside-studios/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://seasidestudios.gitbook.io/seaside-studios/springs-toolkit/asset-window.md).

# Asset Window

You can access this Window in **Tools → AllIn1 → SpringsWindow**, in the top bar of the Unity editor.

Once opened you'll see something like this. You have 3 tabs. The first one is the [Spring Debugger](/seaside-studios/springs-toolkit/spring-debugger.md), explained in a later section.

<figure><img src="/files/dGNtMiSkDdfU09fdDcP1" alt=""><figcaption></figcaption></figure>

#### Spring Settings Tab

In the Spring Settings tab you'll find the **Fixed Update** rate. When enabled, the springs, similarly to how Unity physics work, will update a fixed amount of times per second. Meaning that some frames, if the framerate isn't stable, it may update more than once and that some others it may not even update at all.

<figure><img src="/files/L20t6aIbjCZNPNBOMKvx" alt=""><figcaption></figcaption></figure>

This feature makes sure that the springs are always stable, even in very low frame rate situations. And it also ensures that the springs animations always look and feel exactly the same in all frame rates.

**Fixed Time Step** can be changed according to your project needs, you can even dynamically change it if you really want to. But for most projects the default value will work great.

The feature can be disabled if you wish to, but if the game dips below 10-15 frames you may get some strange behaviors.<br>

**Force Threshold for Integration Method Selection**

Another important configurable variable included in the asset window is the **Force Threshold**. Springs use a fast semi-implicit integration method for normal force values. Above this threshold, an analytical solution is used for stability.

* **Semi-Implicit Method (≤ threshold)** - Fast, efficient, and suitable for most use cases
* **Analytical Solution (> threshold)** - Mathematically exact, handles extreme forces, but computationally more expensive
* **Recommended** - Leave at default value (7500)

<figure><img src="/files/kBQi2NdktKYJWxEk44EO" alt=""><figcaption></figcaption></figure>

This value determines when springs switch from the fast semi-implicit method (default) to the more stable analytical solution. Springs with force values below this threshold use the efficient method, while those exceeding it automatically use the mathematically exact solution for stability. Most projects work well with the default value (7500), but you can lower it if you experience stability issues or raise it for better performance with high-force springs. Setting it to -1 will always use the less performant analytical solution (physical-based simulation), which offers maximum stability at the cost of performance.

You can also enable/disable this in a per spring component basis:

<figure><img src="/files/NpofSg2NTKQEciIzlG3m" alt=""><figcaption></figcaption></figure>

Fix Spring Size Warning

At the bottom of this tab we can also find a button to solve the following issue: [Fix Spring Size Warning](/seaside-studios/springs-toolkit/fix-spring-size-warning.md).

#### Other Tab

In the Other tab (only in Unity version 2021.2 onward) you'll see 2 buttons to automate the addition and removal of the asset custom icon to the Spring Components found in the project.

<figure><img src="/files/QVD5uIOYfwnYTh7faafr" alt=""><figcaption></figcaption></figure>

**You’ll notice that all SpringComponents have a custom icon:**

<figure><img src="/files/BF3BtZuZxYVHUBitWLgp" alt=""><figcaption></figcaption></figure>

This purple icon will also show in the Scene view when Gizmos are enabled. If you want to remove all purple icons or you want to add them to the new SpringComponents you created you can use these shortcut buttons.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://seasidestudios.gitbook.io/seaside-studios/springs-toolkit/asset-window.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.