---
title: "Supported Rendering Features"
canonical: "https://documentation.chaos.com/space/VRHINO/116130416/Supported%20Rendering%20Features"
format: markdown
---
This page provides tables of features supported in CPU and GPU rendering with V-Ray in Rhino. > Macro (anchor)




## **Overview**

---

These features are supported by V-Ray in Rhino for Interactive and Non-Interactive rendering modes.

Both RTX and CUDA cards share the same V-Ray GPU engine supported features.

For more information on V-Ray GPU, see the [GPU Rendering](https://docs-chaos.atlassian.net/wiki/spaces/VRHINO/pages/116130742). 


## **Supported Features**

---





## **Footnotes**

---

**1** – Displacement results between CPU and GPU rendering may differ slightly because of Pre-tessellation and Cache Normal settings.

**2** – Only some procedural textures are supported by V-Ray GPU renderer when used for Bump mapping (f.e. noise and mix maps are supported).

**3** – These plug-ins are only partially supported on GPU.

**4** – RPC are not supported in Interactive rendering mode. Changes done to the RPC model will not be visible in Interactive mode. Please note, that loading RPC models may take substantial time.

**5** – The playback options are currently not supported.

**6** – V-Ray GPU supports Photon map caustics except the Calculation Mode/Disk Caching and Max Density options.

**7** – Currently, Water Surface texture is supported only when used as Displacement and Bump maps. If the texture is added to other slots, it may not work or render as expected.

**8** – In V-Ray 7, the Simple Mix, Mix (Value), Mix (Operator) and Mix (Map) textures are no longer available. They are replaced by the Layered texture.

- GPU engine supports map channels from 0 to 15.
- GPU engine only supports normal maps in tangent space.
- Difference between V-Ray and V-Ray GPU are expected when rendering objects with opacity/translucency modifications.
- When a material is not directly applied to an object or layer but instead only referenced by another asset, e.g. a Proxy Mesh material, and it is introduced through a worksession import, it will not be imported if a naming conflict occurs with a pre-existing material. This is due to a Rhino SDK limitation.

**9** – This texture behaves as baked (instead of procedural) in GPU.