> 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/introduction.md). # Introduction Welcome, this is a top level description of V-Nova PresenZ. #### W**hat is V-Nova PresenZ** V-Nova PresenZ is a unique immersive movie and image format, allowing for 6 degrees of freedom into pre-computed images. It uses a revolutionary approach to 3D creation and rendering, enabling truly movie-quality immersive worlds with higher detail, better immersion, and more fluid, natural movement. By leveraging V-Nova’s advanced data compression technology, V-Nova PresenZ makes these rich, high-quality experiences practical to deliver, without compromising visual fidelity. \ This allows content creators to craft immersive experiences like never before, while also enabling already rendered media to be re-imagined for VR. For studios and rights holders, this opens up an additional revenue stream, creating immersive experiences with minimal overhead. #### Legacy documentation We are currently updating all V-Nova PresenZ documentation. Some materials may not yet be live, so we have provided a link to the legacy documentation below. If you cannot find what you are looking for in the current resources, please refer to the legacy documentation, which may contain the information you need. Legacy documentation: [here](https://support.presenzvr.com/docs/html/index.html#) #### Error reporting If you encounter any technical issues, our technical artists are available to assist. Please use the link below to contact support. We also welcome feedback and suggestions, which we review as part of our ongoing development. Email us:
--- # 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/introduction.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.