> For the complete documentation index, see [llms.txt](https://help.vectary.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.vectary.com/documentation/design-process/effects/reflections.md).

# Reflections

The **Reflections** effect enables surface reflections in the scene, ensuring realistic light behavior.

{% hint style="danger" %}
This effect has a **high** impact on performance. It is recommended to enable it only when necessary or when the scene is highly optimized.
{% endhint %}

{% embed url="<https://www.youtube.com/watch?v=y2Vsu6HkRb0>" %}

#### Settings:

<figure><img src="https://2973737105-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAXNLyKVZ2tvtyDr8sVES%2Fuploads%2F4GJL1cSYObyaVUZDISh1%2Fimage.png?alt=media&amp;token=cf9671a1-1a33-4d76-93db-340cbf2cc1f9" alt="" width="563"><figcaption></figcaption></figure>

* **Realtime Samples** – controls the quality of reflections in real-time mode. Higher values improve reflection accuracy but may impact performance.
* **Steady Samples** – adjusts the reflection quality for static renders, producing sharper and more refined reflections.
* **Selection only** – this option allows enabling reflections only for specific objects, groups, or selections, optimizing performance by applying reflections selectively instead of globally -[Selections](/documentation/other/selections.md)

{% hint style="info" %}
Screen Space Reflections (SSR) are calculated dynamically based on material properties. If roughness and metallic values exceed certain thresholds, SSR is automatically adjusted or disabled to optimize performance for materials where reflections are not essential.
{% endhint %}


---

# 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.vectary.com/documentation/design-process/effects/reflections.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.