> For the complete documentation index, see [llms.txt](https://help.depence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.depence.com/depence-getting-started/depence-graphics-hardware.md).

# Graphics Hardware

Since Depence is a graphically intense software, it requires a powerful graphic card. In case your computer has more than one graphic adapter installed (which is often the case on laptops), you need to make sure that Depence will run on the most powerful card installed.

On NVIDIA-based systems, you can select the "default" graphics hardware within the NVIDIA system configuration.

{% hint style="danger" %}
Please keep your graphic card drivers always up-to-date.
{% endhint %}

## Monitor Refresh rate

The Depence render window always tries to render at the same framerate (fps) as your monitor refresh rate. This synchronization is called V-Sync. Usual monitors are working with a 60Hz refresh rate but modern gaming monitors and even gaming laptop screens are more and more shipped with high-frequency monitors with 120, 140, or even 200 Hz. 

That means on a 140Hz Screen, the V-Sync tries to match Depence's frame rate to 140fps. 

While this improves the subjective smoothness of animations, it drastically stresses your hardware.  This results in GPU overheating/throttling and low battery life on laptops. 

Therefore Depence has a feature called Frame-Limiter, which can limit the fps to a specific value. You can apply a frame limiter in the Application Settings or by a click on the framerate in the window's status bar:\
![](https://content.gitbook.com/content/SJPsyh5CBOise9BtVNGO/blobs/ke4fZt1m2rB3AGfRXdrI/image.png)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.depence.com/depence-getting-started/depence-graphics-hardware.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.