> 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/3d-configurator/interactions/actions/cameras.md).

# Cameras

The **Cameras** action enables the creation and configuration of camera switching within a project, allowing seamless transitions between different camera views. This serves as an alternative to camera movement animation, providing a more direct way to change perspectives.

<figure><img src="https://2973737105-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAXNLyKVZ2tvtyDr8sVES%2Fuploads%2FCsbZvM2NrH7i6PcSeRBV%2Fimage.png?alt=media&amp;token=4d0c66eb-65f8-4985-9598-f219ba0f17d5" alt="" width="563"><figcaption></figcaption></figure>

**Settings**

* **Switch to** — Select the target camera to switch to.
* **Ease type** — Defines the interpolation method, controlling the smoothness of the transition between the current and new view:
  * **Constant** — Instantly switches the view while considering duration and delay.
  * **Linear** — Maintains a uniform speed with no acceleration or deceleration.
  * **Ease auto** — Ensures the smoothest possible motion.
  * **Ease in & out** — Accelerates at the beginning and decelerates at the end.
  * **Ease in** — Starts slowly and stops instantly.
  * **Ease out** — Starts immediately and slows down toward the end.


---

# 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/3d-configurator/interactions/actions/cameras.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.