Hardware Ray Tracing is on the list of tasks that needs to be done for HIP in Blender: ā T91571 Cycles HIP device
As for when this feature will be added? I do not know.
Hardware Ray Tracing is on the list of tasks that needs to be done for HIP in Blender: ā T91571 Cycles HIP device
As for when this feature will be added? I do not know.
Until AMD commits to a date for hardware ray-tracing support in CyclesX I think its safe to assume its not coming. Note there is no mention of ray tracing in the ānext levelā blog.
Ray tracing appears in T91571 as it was copied over from, the failed T82557 issue which related to the no longer supported OpenCL Cycles.
Iām more excited about the performance after Deduplicate CUDA and HIP host code than hardware ray tracing
From my understanding ādeduplicating CUDA and HIP host codeā should not improve performance.
cool. Im not well read up on the technical details, but do you reckon this will get it closer to nvidia optiX performance than enabling hardware raytracing on amd cards?
do you think amd will ever fix hardware raytracing for blender on their end? or dead end?
Hardware raytracing for AMD cards is on the todo list. I cannot give you more information about who and when.
Correct, this is a code change only, avoiding code duplication.
Relying on translation will certainly have code redundancy resulting in performance loss, redundancy is a near-synonym, that word this I do not know how to say in English
Nice ā¦ What about Linux support for AMD GPUs. Thanks.
Hey guys. My time is limited being on parental leave. Sorry there hasnāt been more updates, but the above statement still stands.
Weāre also having another developer look at older card support but no guarantee there. As far as hardware ray tracing support we donāt have an optix like library ready yet for HIP and I canāt give any dates because of corporate reasons. And Iām not sure participating in the speculation on what is a developer forum is the best use of anyoneās time, to be honest.
Iāll give updates when we have them. Please understand companies like AMD donāt want to commit to things before they are ready and Iām telling you guys everything I can.
Hey Brian. Appreciate you taking the time during your leave to reply ( there has been no updates from the core dev team ).
With 3.1 Bcon3 starting on the 26th of Jan I really hope we can get AMD GPU support on Linux in by then or it stands to be left out for another blender release. Thanks.
Itās more a question of when the driver will be available and when to get it. Which you can understand the corporate overlords donāt like to pre-announce. Iāll see if I can share more info but should be in the next few weeks.
I wish AMD the best of luck in delivering a driver that supports cyclesX and satisfies those that have purchased their products.
As for ray tracing I wouldnāt blame anyone for wanting āan order of magnitude increase in intersection performanceā.
Isnāt rays4.1 an off-the-shelf ray tracing library?
Really, I have been waiting for HIP support for my Vega64 card, before moving up from 2.93.x to 3.x generation of blender. I am just unhappy looking at the gap between OpenCL removal and HIP replacement for it. The OpenCL option for rendering on GPU was still ābearableā.
I am keeping my hopes high for its inclusion in 3.2 alpha or 3.1 (stable) in next few weeks.
Hi,
Same for me with my radeon VIIā¦ waiting hard !
Looks like HIP RDNA Linux support will be pushed back to 3.2 which appears to be scheduled for June 8, 2022.
Its bad news for Linux RDNA owners. Strangely these days a delay is about as good as it gets for AMD GPUs when compared to the lack of commitment that Vega / Polaris owners are faced with. In other news Nvidia GPUs remain supported .
There is some hope that ROCm version 5.x will be fully packaged in Ubuntu Jammy 22.04 LTS releasing April 21st 2022. 4.5.2 packages are still entering Debian:new. So that would be somewhat coinciding dates.
P.S. 20220129 lol, no way
While waiting for Blender acceleration, if you wish the ROCm/HIP stack success, you are welcome helping documenting it!
@bsavery since we are on a developer forum: would you or an involved AMD developer be kind enough to walk us through the challenges and technical designs that are being dealt with? I am guessing that graphic/compute interop is a big topic since it is not supported officially yet, but any more details and/or vulgarization would be enjoyed.
Linux RDNA2 users might have a chance to try a new 5.1 ROCM version soon.
Reasons this will amount to a hill of beans:
Reasons to be excited: