
Yesterday's render and cycles meeting for Blender confirmed that on the AMD HIP side, " Hardware ray-tracing aimed for Blender 3.5."Īlso from yesterday's Blender meeting, there is a known AMD HIP performance regression around matrix inverse changes that is being investigated. We've been eager to see AMD's similar ray-tracing support for upstream Blender but it's not coming with the next release (v3.4) but now confirmed to be targeting Blender 3.5. The OptiX ray-tracing support within Blender has worked out very well and faster render times for modern NVIDIA GPUs. NVIDIA has long provided an OptiX back-end for Cycles that makes use of the RT cores on modern NVIDIA GPUs as an alternative to their CUDA back-end.

While Blender 3.2 introduced AMD HIP on Linux support for GPU acceleration and the recent Blender 3.3 extended the AMD GPU Cycles acceleration back to GFX9/Vega GPUs, for those wanting AMD ray-tracing support within Blender it's not expected to come until Blender 3.5.
