> 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/chaotic-tag-rendering-grass-hairs-fur-trees....md).
# Chaotic tag: rendering grass, hairs, fur, trees...
[
](https://support.presenzvr.com/docs/html/_images/InsideZOV.png)**When to use the chaotic tag:**
If you’re working on a scene with complex geometry, such as vegetation or hair, you can speed up your rendering process hugely by using the PresenZ Chaotic tag. This tag reduces the number of unnecessary points rendered for complex objects, decreasing the overall render time and the size of the final .prz file
**How does it work?**
To achieve this, V-Nova PresenZ divides the space around the Zone of View into smaller volumes corresponding to 8x8 pixel patches, with a variable depth. \
As the distance from the center increases, the slices become deeper, as we don’t require as much detail further away from the ZOV.\
\
This is a top view representing the space partition:
For each patch, V-Nova PresenZ computes a maximum of 8x8 pixels (64 pixels) instead of the original complexity of your objects. Without this process, leaves or grass could generate hundreds of points for the same patch volume. This approach can significantly reduce the complexity of your scene and speed up rendering.
We provide a UI to tag as "chaotic" selected objects in your 3D scene.
---
# 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/chaotic-tag-rendering-grass-hairs-fur-trees....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.