> For the complete documentation index, see [llms.txt](https://docs.v-nova.com/technologies/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.v-nova.com/technologies/v-nova.presenz/v-nova-presenz-documentation/draft-mode.md).

# Draft mode

**Draft mode**

<figure><img src="https://2927645607-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1djoRwqtVhAs0LOpvzC9%2Fuploads%2Fm6vrf6VhU8KSHd0W3ZGF%2Fimage.png?alt=media&amp;token=1462df13-791a-48cc-9f4f-ef9368b949b3" alt=""><figcaption></figcaption></figure>

Draft mode is a special debug/test mode of PresenZ that can be super useful for quick tests:

* It does a volumetric rendering, so depth information is stored for every point
* But only from the center of the Zone Of View

So, of course, any occluded object not visible from the center of the ZOV won't be captured but:

* It renders very quickly, normally almost like a 2d image,
* The result still allows to test in VR the scene composition, scale, animation, and placement of the Zone of View.

{% hint style="info" %}
[*Note: We recommend when working on a new scene to start in draft mode low resolution to iterate quickly.*](#user-content-fn-1)[^1]
{% endhint %}

[^1]:


---

# 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://docs.v-nova.com/technologies/v-nova.presenz/v-nova-presenz-documentation/draft-mode.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.
