Cycles OptiX multi‑GPU device limit configuration

Answer to the Core Question

Blender Cycles with the OptiX backend does not impose a hard‑coded maximum number of RTX GPUs. In practice, the number of devices that can be actively used is limited only by system‑level factors such as PCIe topology, power delivery, and the amount of VRAM available on each card. Enabling more than two GPUs does not trigger an intentional fallback to single‑GPU mode, but it can cause the render to fall back silently or produce allocation errors if the driver or Blender build cannot initialise a multi‑GPU OptiX context.

Likely Explanation for Observed Limitations

• Older NVIDIA drivers or mismatched driver/Blender versions can fail to create a valid OptiX context when more than two devices are enumerated.
• Mixed power states or PCIe bandwidth contention (e.g., GPUs sharing a single x16 lane) can lead to unstable memory allocation during rendering.
• Scene‑specific factors such as very large textures or high sample counts may exhaust the VRAM of a single device even when several GPUs are enabled, causing Blender to drop back to the first available device.

Confirmed Facts

• No Blender documentation states a device count cap for OptiX.
• Official release notes for recent Blender builds (2.93 LTS onward) and NVIDIA driver releases (470 + series) report full multi‑GPU support on RTX‑class GPUs.
• Users who updated both Blender and the driver to the latest releases and enabled all GPUs in Preferences → System → Cycles Render Devices observed all devices contributing to tile rendering.

Practical Verification Steps

1. Open Window → Toggle System Console (Windows) or run Blender from a terminal (Linux/macOS) to capture startup logs.
2. Check the console for lines such as OptiX: device 0 – NVIDIA RTX 3080 and ensure one line appears per GPU.
3. In the Render Properties panel, look at the Render Statistics while rendering a test scene. The number of tiles per GPU should be greater than one if multiple devices are active.
4. If the console shows only a single device or errors like OptiX context creation failed, try updating to the latest stable Blender build and the latest NVIDIA driver for your GPU series.
5. Confirm that all GPUs are listed under Preferences → System → Cycles Render Devices and that each is set to OptiX.

What to Do If You Still See Fallbacks or Errors

• Verify that all GPUs are identical RTX models and that they are physically connected to separate PCIe lanes.
• Check the driver version: NVIDIA recommends the 470 + series for Blender 2.93 LTS and later.
• Ensure Blender is built with OptiX support (the default Windows and macOS installers include it; Linux users should use the official binaries).
• If the problem persists, consider resetting the GPU selection to Auto and then re‑enabling each GPU manually.

Missing Diagnostic Detail Needed for Precise Guidance

To give a definitive recommendation for your setup, please provide:

• Blender version (e.g., 3.5.0‑stable)
• NVIDIA driver version (e.g., 525.60.13)
• Exact GPU model and PCIe slot configuration (e.g., three RTX 3080s on separate x16 lanes)

Conclusion

In short, Cycles OptiX can use any number of RTX GPUs as long as the driver and Blender build support multi‑GPU contexts and the hardware topology is adequate. The observed fallback or memory errors with three or more GPUs are not a documented restriction but rather a symptom of driver or system configuration issues that can be resolved by updating software and verifying hardware layout.