The other advantage is that the tools with HIP allow easy migration from existing CUDA code to something more generic. This allows the Blender Cycles developers to write one set of rendering kernels and run them across multiple devices.
#HOW TO WORK BLENDER ON MAC PORTABLE#
HIP (Heterogeneous-computing Interface for Portability) is a C++ Runtime API and kernel language that allows developers to create portable applications for AMD and NVIDIA GPUs from a single source code. Luckily, AMD has an open-source solution for developers just for that. In short, with Cycles X, they were looking for a way to compile a single codebase that could be used on all the different devices Cycles can render on, including AMD graphics cards. However, moving forward our partners at Blender were hoping to merge the separate OpenCL code with the C++ CPU and CUDA rendering code. OpenCL is a C-based programming language that allows running programs on many GPUs which support it. Previous versions of Cycles, Blender’s physically-based path tracer, supported rendering via the OpenCL framework. To help address this, AMD has been working very closely with Blender to improve support for GPU rendering in Blender using the AMD HIP API, to ensure users of AMD graphics cards can take advantage of all the enhancements found in Cycles X.įor AMD GPUs, this will be in Blender 3.0, expected in December 2021. This removed OpenCL support for rendering on AMD GPUs for technical and performance reasons. Blender 3.0 was announced with some rewrites to the rendering engine Cycles (AKA Cycles X). We have some exciting developments to share about AMD graphics card support. With improved AMD GPU rendering support in Cycles. Blender 3.0 takes support for AMD GPUs to the next level.
0 kommentar(er)
