> 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-program-overview/depence-camera-and-navigation.md).
# Camera & Navigation
The Camera in Depence is optimized to be easily navigated through bigger scenes or even rotate around a specific object.
## **Focus & Zoom**
Focus your camera at the point of interest and use your Scroll-Wheel on your mouse to zoom in or out.
## **Rotate**
To rotate your camera around your focused point hold **ALT** and your left mouse button or the middle mouse button/scroll wheel. The Camera will try to rotate around the intersection point of your scene. If no intersection is found *(e.g. when clicking on the sky)* the camera will rotate around itself.
## **Move**
To move your camera in view-space hold your right mouse button while moving the mouse.
## **Limited Picking distance**
The editor limits the distance to an intersection point, which is too far away, to prevent accidental movements by default. However, in some cases, like in terrain sculpting or Fireworks, it might be required to disable this limit. Therefore go to the View-Menu and disable "Limit Pick Distance" in the camera menu.
---
# 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-program-overview/depence-camera-and-navigation.md?ask=&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.