> 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/smoke-fire-and-atmospheric-rendering.md).
# Smoke, fire and atmospheric rendering
How to render Atmospheric volumes
#### Smoke, fire and atmospheric rendering
V-Nova PresenZ does support Smoke, Fire, atmospheric and more broadly "volumetric" rendering from Maya Arnold. But it is important to remember that a volume that takes up a large space will greatly increase the number of points and the amount of data in the scene. So this will take up more blocks in the render. As such, you should limit the amount of space used for atmospheric volumes by using the aiAtmosphereVolume shader on a geometry. As seen below
You should avoid the atmosphere attribute inside Arnold, as this will create points throughout the scene and will affect your renders, as mentioned. It will also create issues where you will need to render inside the Zone Of View.
When rendering any volume, it is important to limit the number of effective Lights and improve the samples of the render inside of Arnold
* Here is a simple look at render settings that will work for testing
---
# 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/smoke-fire-and-atmospheric-rendering.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.
