> 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/the-clipping-sphere.md). # The clipping sphere **The clipping sphere** The clipping sphere feature in V-Nova PresenZ allows you to render only a specific part of a 3D scene. This can be useful if you’ve made changes to a particular object and want to see how those changes have affected it without having to render the entire scene. Instead, you can place a clipping sphere around the object and render only that part. This is similar to doing a cropped render in 2D. In the rendered image, everything outside of the clipping sphere is not visible, giving the impression that the object is isolated in space. In some cases, you might want to do the opposite and render everything outside of the sphere, creating a hole in the final render. This technique can also be used for animations where a large part of the scene is static and unaffected by the animation (such as shadows and reflections). By rendering this static part of the scene once using the clipping sphere feature, usually outside the sphere, you can save time and resources during the animation rendering process, by just rendering inside the sphere for the animation. ![](https://2927645607-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1djoRwqtVhAs0LOpvzC9%2Fuploads%2F3OOAWordhgNfQaUzas13%2F14.jpeg?alt=media) --- # 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/the-clipping-sphere.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.