HIP integration Work continues on AMD HIP integration. Currently to use this as yet unreleased drivers are needed on both Windows and Linux. Looking into what cards are supported. (Brian)
Plan to submit MNEE manifold next event estimation code for 3.1 (Christophe)
Working on the Metal Backend first fix kernel side then host side. Hopes to have this ready for 3.1 (Michael)
Optix denoising issue caused by driver bug, hopefully fixed for 3.0 (Patrick)
This is a weekly video chat meeting for planning and discussion of Blender rendering development. Any contributor (developer, UI/UX designer, writer, …) working on rendering in Blender is welcome to join and add proposed items to the agenda.
For users and other interested parties, we ask to read the meeting notes instead so that the meeting can remain focused.
Will metal be implemented in the whole software or just cycles? Will the metal version have hybrid rendering or other optimisation that you could share? Thanks in advamce
In equal sample situation, the paper says it’s 3 times slower, but equal noise (which is the case now in 3.0 with Adaptive Sampling) should be much faster
Hey Brecht, It’s amazing to see the Depth Denoising pass restored and No AA on the position pass! We have already started using the non-AA position pass right away.
However, I’m not sure if it’s a bug or if something has changed, but I can’t seem to get the denoising depth pass to appear in the compositor in any of the latest daily builds.
At the moment code for AMD GPU support for Cycles via HIP exists in Blender 3.0. But it is disabled by default and will probably remain that way for the official release of Blender 3.0.
You can compile Blender 3.0 for yourself with HIP enabled. However the tools for doing so on Windows are not currently avaliable (Expected to be released some time in November). The tools for compiling Blender with HIP on Linux are avaliable, but every person I’ve seen attempt it has come accross some issue of some kind that stopped them from getting a render to work. It’s possble the cause for the issues people faced are caused by HIP on Linux, or the GPU drivers on Linux, needing to be updated to support the code in Cycles or the code in Cycles still isn’t finished yet.
The other limitation is that by default Cycles only generates binaries for RDNA2 GPUs and newer. Investigations are underway to see if older GPUs can be supported.
So this is going to magically work without users testing and reporting bugs directly at release ? Very strange development protocol. Don’t really care about propriety OSs ( That is the price you pay for using Closed Source )
From my understanding HIP won’t be avaliable with Blender 3.0. HIP will PROBABLY be enabled in Blender 3.1 before BCON 2 and will under go testing and bug fixing throughout the rest of 3.1’s development.
Thanks Alaska.
I had problems with newest AMDGPU-PRO drivers on Debian due to some bug in LLVM11. Recently LLVM was upgraded to 12. So that might be useful for testing newer drivers and compute stack in this distro.
If I’ll be able to install recent drivers, I’ll definitely give HIP a shot on Vega II.
I can’t find the gpu under ubuntu, 2.93 can’t find the ray tracing graphics card of opencl, 3.0 has hip but the same can’t find the rdna2 graphics card, 2.93 can’t find opencl I’m very confused to install the driver code are amd light copy (. /amdgpu-pro-install -y --opencl=rocr,legacy)
So far it seems things aren’t working as expected, especially on “older” GPUs, but that’s based on the results of others. So I’m not sure how right this assumption is. I would recommend you wait until official instructions on how to use and setup HIP in Blender are made publicly available.
As for the HIP implementation, it is disabled by default and is thus not accessible to the end user. However you can compile Blender with HIP if you want to test it, I’m just not sure if it works with the publicly available GPU drivers and HIP compiler. You should wait until official build instructions are released by AMD/Blender developers.
