> For the complete documentation index, see [llms.txt](https://know.rendernetwork.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://know.rendernetwork.com/getting-started/how-to-get-started/working-with-particles-attributes-and-dynamics.md).

# Working with Particles, Attributes and Dynamics

Avoiding common errors when setting up your scene

In programs like Cinema4D and Houdini - when users often work with plugins for particle effects - some additional baking may be needed to use the Render Network. This tutorial created by artist [Andrey Lebrov](https://www.youtube.com/channel/UCZsHHoDLK0s6r44ifx0DnXQ), walks you through the process of working with particles and attributes in Cinema4D for use on the Render Network.

{% embed url="<https://youtu.be/Ee4X8Slzi6o>" %}
Baking Tutorial by Andrey Lebrov
{% endembed %}

For more information about exporting ORBX Scenes from Cinema4D, please see the guide below:

{% embed url="<https://youtu.be/zzlPI68RRW0>" %}
Exporting ORBX from C4D guide
{% endembed %}

You can also find documentation for exporting ORBX Scenes from Cinema4D in the 'Octane Cloud Rendering' section of the [OctaneRender for Cinema4D](http://www.aoktar.com/octane/OCTANE%20HELP%20MANUAL.html?index.html) manual&#x20;

{% embed url="<http://www.aoktar.com/octane/OCTANE%20HELP%20MANUAL.html?index.html>" %}
Copyright Ahmet Oktar
{% endembed %}


---

# 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://know.rendernetwork.com/getting-started/how-to-get-started/working-with-particles-attributes-and-dynamics.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.