> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/learn/workflows/v-ray-workflow.md).

# V-Ray Workflow

The ThreeKit platform provides extensive support for the use of Vray assets, in order to generate beautiful 2D renders of each configuration.

<figure><img src="https://2029237644-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8N1IA5a0lqRClKT5eQQ7%2Fuploads%2FmaGQMIJy7uli4uv9ueWL%2FEngagementRing_3.jpg?alt=media&amp;token=ba3b2dee-afb6-47b7-8b4d-25b42f35b1bb" alt=""><figcaption></figcaption></figure>

The use of VRay allows us to produce more photorealistic results than what we could achieve currently in WebGl. This is due primarily to the fact that Vray uses a ray-traced approach to lighting and shaders, which means that it tries to simulate more closely how light behaves in the real world. This leads to better reflections, refractions, shadows, and aliasing.

The following set of documents describe the process required for the generation of 2D renders on ThreeKit, using the Vray set of features.

To find more information about Vray, please visit the [official documentation](https://docs.chaos.com/category/vray).

1. [Vray Requirements](https://community.threekit.com/learn/workflows/v-ray-workflow/1.-vray-requirements.md)
2. [Vray Asset Preparation](https://community.threekit.com/learn/workflows/v-ray-workflow/2.-vray-asset-preparation.md)
3. [Vray Asset Export](https://community.threekit.com/learn/workflows/v-ray-workflow/3.-vray-asset-export.md)
4. [Vray Scenes](https://community.threekit.com/learn/workflows/v-ray-workflow/4.-vray-scenes.md)
5. [Vray Models](https://community.threekit.com/learn/workflows/v-ray-workflow/5.-vray-models.md)
6. [Vray Materials](https://community.threekit.com/learn/workflows/v-ray-workflow/6.-vray-materials.md)
7. [Vray VFB Presets](https://community.threekit.com/learn/workflows/v-ray-workflow/7.-vray-vfb-presets.md)
8. [Vray Operators](https://community.threekit.com/learn/workflows/v-ray-workflow/8.-vray-operators.md)
9. [Vray Light Linking](https://community.threekit.com/learn/workflows/v-ray-workflow/9.-vray-light-linking.md)
10. [Vray Compositing](https://community.threekit.com/learn/workflows/v-ray-workflow/10.-vray-compositing.md)
11. Vray Render Workflow (coming soon)
12. Vray Troubleshooting (coming soon)


---

# 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://community.threekit.com/learn/workflows/v-ray-workflow.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.
