In brief
- In 3ds Max, V-Ray GPU is selected as the production renderer from the Render Setup window.
- CUDA can use the CPU and NVIDIA GPUs together; HIP support is also noted in V-Ray 7.3.
- If the interface slows down on a single GPU, try lowering Rays per pixel and Rays bundle size; this may also reduce render speed.
- Some materials, textures, and features are only partially supported or unsupported in V-Ray GPU.
According to the official documentation Chaos publishes for 3ds Max, V-Ray GPU is a separate renderer that uses GPU hardware acceleration. It can be selected from 3ds Max’s Render Setup window; in CUDA setups, it is also possible to use the CPU and NVIDIA GPU together. Chaos’s setup and configuration documentation was updated on 21 May 2026. This guide brings together the steps for enabling the renderer, selecting devices, and checking compatibility in architectural visualization scenes.
1. Select V-Ray GPU as the production renderer
Open the Render Setup window in 3ds Max.
At the top of the window, set Target to Production Rendering Mode.
Select V-Ray GPU from the Renderer list.
Chaos’s documentation recommends switching scenes previously saved with the ActiveShade renderer to V-Ray GPU as the production renderer. Because V-Ray GPU is a separate renderer from standard V-Ray, the available settings change when you select it. The V-Ray GPU options in Render Setup are spread across the V-Ray, GPU Performance, Settings, and Render Elements tabs. The GPU Performance tab includes device selection, Distributed Rendering, texture processing, and usage settings; the Settings tab includes options such as Image Sampler.
V-Ray 6 Hotfix 1 is noted to preserve render settings when switching between V-Ray and V-Ray GPU. However, when using the Bucket Image Sampler, Samples limit may change depending on the Max subdivs value. For this reason, it’s a good idea to review the settings before rendering rather than assume they are all correct after switching renderers.
2. Identify your hardware and render devices
V-Ray GPU runs ray-tracing calculations on supported GPU devices. The documentation states that NVIDIA CUDA support applies to Maxwell and newer cards in 64-bit versions of V-Ray, with a minimum compute capability of 5.2. RTX mode works with RTX cards. HIP support was also added in V-Ray 7.3. For HIP, Chaos specifies RDNA2 as the minimum, recommends RDNA3 and above, and lists driver version 26.2.2.
To select devices, use the V-Ray GPU Render Devices Select control in Render Setup. It lets you choose which GPUs will render and manage available resources. For example, on a system with multiple GPUs, you can leave one card free for interface use. An asterisk next to a device’s name indicates that a monitor is connected to that GPU.
For hybrid rendering with CUDA, enable the C++/CPU device in the device list. This lets V-Ray GPU include the CPU and NVIDIA GPU in the same render job. According to Chaos’s documentation, no special driver is required for this setup; the CPU device can also be used on computers without a CPU, NVIDIA GPU, or NVIDIA drivers. However, adding the CPU does not mean every scene will render faster; results should be tested for the hardware and workload.
3. Check performance and confirm the active device
If the interface becomes slow or unresponsive while rendering with a single GPU, Chaos recommends lowering the Rays per pixel and Rays bundle size / IPR ray bundle size values in the Performance tab. The documentation gives 64/1 and 32/1 as values to try. Sending smaller data batches to the GPU can help it respond more quickly to interface requests, but may reduce render speed. Enable the statistics display to measure the difference and find the right balance for your system.
| Setting | Recommended value | Effect |
|---|---|---|
| Rays per pixel / Rays bundle size or IPR ray bundle size | Try 64/1 or 32/1 | May improve interface responsiveness; may reduce render speed. |
The documentation also emphasizes that V-Ray GPU may silently fall back to CPU code when no supported CUDA device is found. So the fact that a render has started does not prove that the GPU is being used. Check the V-Ray console output and log messages to see which device is active and review any warnings about driver compatibility. If a separate GUI tool was used to select render devices, 3ds Max may need to be restarted for the changes to take effect. Device selection in Render Setup does not require a restart.
4. Check compatibility in architectural visualization scenes
Before switching to GPU rendering, check the support status of the materials, textures, and render features in your scene. Chaos’s support list marks some features as partially supported or limited. For example, VRayMtl does not support Diffuse Roughness; VRayMtl/OpenPBR mode is partially supported. The Composite texture has a six-layer limit with the GPU renderer. Some procedural textures are baked for GPU rendering, which can increase memory use compared with fully supported procedural textures.
In architectural interior and exterior scenes, test particularly heavy material use, hair and fur plugins, scattering systems, and animated camera moves. Materials and textures that are not supported are treated as incompatible in the Material/Map Browser in 3ds Max’s Material Editor; they may not appear unless Show Incompatible is enabled. Motion blur in GPU rendering is supported only on whole-number frames; for example, the documentation notes that a render starting at frame 1.25 may not produce the correct result. Area shadows are also unsupported.
A safe workflow for an office is to render a representative frame on the GPU first, compare it with the CPU result, and inspect critical materials in that test. Driver compatibility, scene plugins, and memory requirements matter just as much as having hardware capable of GPU rendering. The CPU-GPU hybrid option allows you to use the existing processor as well, but the same results should not be assumed across all scenes in terms of quality, performance, or compatibility.
Common mistakes
Assuming the GPU is definitely being used because rendering has started; an unsupported CUDA device may trigger a silent fallback to the CPU.
Moving on to production rendering without testing materials and textures marked as partially supported or limited.
Lowering the Rays values to speed up the interface without accounting for the possibility of longer render times.
Overlooking the need to restart 3ds Max after using a separate device selection tool.
Sources
3 sourcesSource texts are not republished; short quotes are marked, everything else is our own summary and commentary.
For architecture and visualization offices in Turkey, V-Ray GPU’s main advantage is that, with suitable hardware, it can move render calculations to the GPU and also bring the CPU into the process through CUDA. Still, that does not mean a hardware upgrade will automatically save time on every project; it’s important to run a short test with the scene, drivers, and materials you use.
Especially when production deadlines are tight, issues such as a silent fallback to the CPU, partial material support, and GPU memory should not be overlooked. Teams should first compare results using representative scenes and frames, and account for the possibility that render times may increase when performance settings are lowered to improve interface responsiveness.
Frequently asked questions
How do you enable V-Ray GPU in 3ds Max?
In the Render Setup window, set Target to Production Rendering Mode and select V-Ray GPU from the Renderer list.
Can V-Ray GPU use the CPU and GPU at the same time?
Yes. Enable C++/CPU among the CUDA devices to render with the CPU and NVIDIA GPU together.
How can you tell whether a V-Ray GPU render is actually running on the GPU?
Check the V-Ray console output and log messages. If no supported CUDA device is found, the renderer may silently fall back to CPU code.
