blender/blender
163
517
Fork 786
Code Issues 6.8k Pull Requests 946 Projects 19 Wiki Activity

Failed to create HIPRT context despite HIPRT not being enabled or even possible on the specific card #108115

New Issue
Closed
opened 2023-05-21 02:49:08 +02:00 by Astra Kaim · 14 comments
Astra Kaim commented 2023-05-21 02:49:08 +02:00
Copy Link

System Information
Operating system: Windows 10 Home version 22H2 OS build 19045.2965
Graphics card: AMD Radeon RX 5700XT, AMD Software: Adrenalin Edition Version 23.4.3

Blender Version
Broken: 4.0.0 Alpha, 2023-05-19 21:45, 33c13ae6e3, main
Worked: Don't know? Have not seen the feature that causes issues before, perhaps because I only update every couple of weeks to months.

Short description of error
When I try to use HIP for rendering of a scene in Cycles, any scene I'm pretty sure, I cannot. Any attempt to do so returns the "failed to create HIPRT context" error, even though, since my card is incapable of accelerated ray tracing, I have the check box that's supposed to enable the experimental feature not checked (it doesn't matter anyway, same error regardless).

Exact steps for others to reproduce the error
I... am not sure? As far as I can tell, there's just no way for me to use HIP in any Blender version with the HIPRT feature implemented, in spite of the supposed toggle being in place, and the assurances of shader fallback. Similarly, I'm pretty sure I can't update my driver, since... my card isn't capable of RT, and so is not even listed as compatible under the beta release driver I found in a thread on here. Which leaves me simply unable to do anything to make HIP work at all. I'm not sure what steps would be needed to reproduce it, whether it is a fluke, or what. My GPU drivers are as up to date as compatibility will allow, and I'm literally trying to just use normal HIP without RT.

**System Information** Operating system: Windows 10 Home version 22H2 OS build 19045.2965 Graphics card: AMD Radeon RX 5700XT, AMD Software: Adrenalin Edition Version 23.4.3 **Blender Version** Broken: 4.0.0 Alpha, 2023-05-19 21:45, 33c13ae6e38f, main Worked: Don't know? Have not seen the feature that causes issues before, perhaps because I only update every couple of weeks to months. **Short description of error** When I try to use HIP for rendering of a scene in Cycles, any scene I'm pretty sure, I cannot. Any attempt to do so returns the "failed to create HIPRT context" error, even though, since my card is incapable of accelerated ray tracing, I have the check box that's supposed to enable the experimental feature not checked (it doesn't matter anyway, same error regardless). **Exact steps for others to reproduce the error** I... am not sure? As far as I can tell, there's just no way for me to use HIP in any Blender version with the HIPRT feature implemented, in spite of the supposed toggle being in place, and the assurances of shader fallback. Similarly, I'm pretty sure I can't update my driver, since... my card isn't capable of RT, and so is not even listed as compatible under the beta release driver I found in a thread on here. Which leaves me simply unable to do anything to make HIP work at all. I'm not sure what steps would be needed to reproduce it, whether it is a fluke, or what. My GPU drivers are as up to date as compatibility will allow, and I'm literally trying to just use normal HIP without RT.
Astra Kaim added the
Severity
Normal
Type
Report
Status
Needs Triage
 labels 2023-05-21 02:49:09 +02:00
Astra Kaim commented 2023-05-21 22:31:19 +02:00
Author
Copy Link

Tested this on an old install of 3.6.0 Alpha, and it still didn't work, although this time it said "HIP binary kernel for this graphics card compute capability (10.1) not found." instead. Rolling back to my even older install of 3.5.0 Alpha enables me to render, although I'm not sure to what degree GPU utilisation is achieved there. I'm gonna go test the current 3.6.0 Beta version, now, see if it was fixed and re-broken or just has been broken since 3.6.0 in general.

Tested this on an old install of 3.6.0 Alpha, and it still didn't work, although this time it said "HIP binary kernel for this graphics card compute capability (10.1) not found." instead. Rolling back to my even older install of 3.5.0 Alpha enables me to render, although I'm not sure to what degree GPU utilisation is achieved there. I'm gonna go test the current 3.6.0 Beta version, now, see if it was fixed and re-broken or just has been broken since 3.6.0 in general.
Astra Kaim commented 2023-05-21 22:36:00 +02:00
Author
Copy Link

Okay, the current 3.6.0 Beta build also returns the same error as the 4.0.0 Alpha build ("Failed to create HIPRT context.").

Okay, the current 3.6.0 Beta build also returns the same error as the 4.0.0 Alpha build ("Failed to create HIPRT context.").
Richard Antalik commented 2023-05-25 05:27:55 +02:00
Member
Copy Link

Just to clarify this report - Blender gives error whe you render with HIP? And you say this worked in 3.5 version?

Just to clarify this report - Blender gives error whe you render with HIP? And you say this worked in 3.5 version?
Richard Antalik added
Status
Needs Information from User
 and removed
Status
Needs Triage
 labels 2023-05-25 05:28:09 +02:00
Astra Kaim commented 2023-05-25 17:31:48 +02:00
Author
Copy Link

Yes. It differs what error I get depending on the version, and doesn't work in any version after the current stable release, which last time I checked was 3.5.1, I think? There it works fine and speeds up rendering a fair chunk compared to CPU only, so I reckon it does truly work. But in later versions, in the ones predating the HIP RT implementation I get a missing binary kernel message, and in the ones that have implementations of HIP RT, I get the error that it fails to create HIPRT context.

As far as I can tell my OS and drivers are as upto date as possible, and I tested 4.0.0A, 3.6.0B, and 3.5.1S on the latest releases at the time of writing, and found the problems on all versions later than 3.5.1S, and moreover I also found the same issue in a rather old historical build of 3.6.0 back from when it was in Alpha, which to me suggests that something was broken in the move from 3.5.x to 3.6.0, and has been broken for a while. It's possible it's an issue with my specific configuration, and to that end I am very willing to help examine the specifics by providing extra info, but whatever the case may be, yes. Blender errors when I try to render with HIP and include the GPU in it by checking the box in the system tab of preferences, and it works in 3.5.x versions on my end.

Yes. It differs what error I get depending on the version, and doesn't work in any version after the current stable release, which last time I checked was 3.5.1, I think? There it works fine and speeds up rendering a fair chunk compared to CPU only, so I reckon it does truly work. But in later versions, in the ones predating the HIP RT implementation I get a missing binary kernel message, and in the ones that have implementations of HIP RT, I get the error that it fails to create HIPRT context. As far as I can tell my OS and drivers are as upto date as possible, and I tested 4.0.0A, 3.6.0B, and 3.5.1S on the latest releases at the time of writing, and found the problems on all versions later than 3.5.1S, and moreover I also found the same issue in a rather old historical build of 3.6.0 back from when it was in Alpha, which to me suggests that something was broken in the move from 3.5.x to 3.6.0, and has been broken for a while. It's possible it's an issue with my specific configuration, and to that end I am very willing to help examine the specifics by providing extra info, but whatever the case may be, yes. Blender errors when I try to render with HIP and include the GPU in it by checking the box in the system tab of preferences, and it works in 3.5.x versions on my end.
Astra Kaim commented 2023-05-25 21:49:10 +02:00
Author
Copy Link

Let me know if I should edit the original report and thread title to reflect my most recent findings, for ease of access.

Let me know if I should edit the original report and thread title to reflect my most recent findings, for ease of access.
Richard Antalik commented 2023-05-26 06:25:49 +02:00
Member
Copy Link

I do have RX 5700XT, but on Mac machine, so I can't check. @JacquesLucke I see you have similar GPU and Windows, can you check?

@Astra-Kaim I assume this happens with all files, is that correct? if this is happens with only specific siles, please upload sample for testing.

I do have RX 5700XT, but on Mac machine, so I can't check. @JacquesLucke I see you have similar GPU and Windows, can you check? @Astra-Kaim I assume this happens with all files, is that correct? if this is happens with only specific siles, please upload sample for testing.
Jacques Lucke commented 2023-05-26 10:04:22 +02:00
Member
Copy Link

I actually don't have windows currently unfortunately. Updated my entry in https://wiki.blender.org/wiki/Process/Hardware_List

I actually don't have windows currently unfortunately. Updated my entry in https://wiki.blender.org/wiki/Process/Hardware_List
Astra Kaim commented 2023-05-26 11:32:30 +02:00
Author
Copy Link

@iss As far as I've been able to tell, yes, as it happens even when I remove the appropriate version's folder under C:\Users\<username>\AppData\Roaming\Blender Foundation\Blender and run with factory settings loaded from the download, only altering the settings necessary to enable HIP with the GPU active, and to switch from the Eevee default to Cycles GPU Compute. That in itself reproduces the error.

@iss As far as I've been able to tell, yes, as it happens even when I remove the appropriate version's folder under `C:\Users\<username>\AppData\Roaming\Blender Foundation\Blender` and run with factory settings loaded from the download, only altering the settings necessary to enable HIP with the GPU active, and to switch from the Eevee default to Cycles GPU Compute. That in itself reproduces the error.
Richard Antalik commented 2023-05-28 14:58:33 +02:00
Member
Copy Link

@Jeroen-Bakker do you have hardware/OS to check?

@Jeroen-Bakker do you have hardware/OS to check?
Richard Antalik added
Status
Needs Triage
 and removed
Status
Needs Information from User
 labels 2023-05-28 14:58:42 +02:00
Jeroen Bakker commented 2023-05-29 10:03:50 +02:00
Member
Copy Link

To my knowledge the AMD 5000 series doesn't have hardware raytracing support. It might be that some logic isn't correct as HIPRT shouldn't be used at all, but continue with HIP (without RT).

@BrianSavery can you have a check on this issue?

To my knowledge the AMD 5000 series doesn't have hardware raytracing support. It might be that some logic isn't correct as HIPRT shouldn't be used at all, but continue with HIP (without RT). @BrianSavery can you have a check on this issue?
Astra Kaim commented 2023-05-29 15:51:18 +02:00
Author
Copy Link

@Jeroen-Bakker You're correct about RX 5000 series GPUs not having RT support. However, the concerning thing is that my testing showed that HIP is broken in any version higher than the current build of 3.5.1 Stable, even though only the most recent ones of those even support HIP RT. The error is different, saying the binary kernel is missing, but the result is the same, that is, no rendering happens. Rolling back to 3.5.1, I'm pretty sure it works fine, though... which makes me pretty sure that it's not a driver or OS problem, since if that was the case, older versions wouldn't work either. ...unless of course 3.5.1's implementation is broken in such a way that it only says it utilizes the GPU, while not actually doing that, but based on my limited testing that seems unlikely since there is a performance boost for CPU+GPU compared to CPU only, with HIP.

@Jeroen-Bakker You're correct about RX 5000 series GPUs not having RT support. However, the concerning thing is that my testing showed that HIP is broken in any version higher than the current build of 3.5.1 Stable, even though only the most recent ones of those even support HIP RT. The error is different, saying the binary kernel is missing, but the result is the same, that is, no rendering happens. Rolling back to 3.5.1, I'm pretty sure it works fine, though... which makes me pretty sure that it's not a driver or OS problem, since if that was the case, older versions wouldn't work either. ...unless of course 3.5.1's implementation is broken in such a way that it only says it utilizes the GPU, while not actually doing that, but based on my limited testing that seems unlikely since there is a performance boost for CPU+GPU compared to CPU only, with HIP.
Pratik Borhade commented 2023-07-04 12:17:33 +02:00
Member
Copy Link

@Astra-Kaim hi, does cycles render work without HIPRT in recent builds?: https://builder.blender.org/download/daily/
HIPRT is only supported for RDNA 2 architecture GPUs: 557a245dd5

@Astra-Kaim hi, does cycles render work without HIPRT in recent builds?: https://builder.blender.org/download/daily/ HIPRT is only supported for RDNA 2 architecture GPUs: 557a245dd5ce30f9e802e5b11a986f8378e3ed33
Pratik Borhade added
Status
Needs Information from User
 and removed
Status
Needs Triage
 labels 2023-07-04 12:17:48 +02:00
Astra Kaim commented 2023-07-04 23:38:12 +02:00
Author
Copy Link

Uh, it would seem so, thanks for the reminder! The problem is actually gone it seems; that is, with HIP RT unchecked (as it should be on 5000 series), with both CPU and GPU boxes checked, with Cycles rendering selected, with GPU compute selected, it now renders out fine, both on a brand new stock default cube file, and on my old projects opened upon loading 3.6 settings.

That is to say, I think you can close the ticket, now, as the issue appears to have been resolved! I can go back to using recent Blender versions for my projects. :)

Uh, it would seem so, thanks for the reminder! The problem is actually gone it seems; that is, with HIP RT unchecked (as it should be on 5000 series), with both CPU and GPU boxes checked, with Cycles rendering selected, with GPU compute selected, it now renders out fine, both on a brand new stock default cube file, and on my old projects opened upon loading 3.6 settings. That is to say, I think you can close the ticket, now, as the issue appears to have been resolved! I can go back to using recent Blender versions for my projects. :)
Pratik Borhade commented 2023-07-05 04:36:12 +02:00
Member
Copy Link

Thanks, will close then.

Thanks, will close then.
Blender Bot added
Status
Archived
 and removed
Status
Needs Information from User
 labels 2023-07-05 04:36:17 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
Interest
Alembic

  
Interest
Animation & Rigging

  
Interest
Asset System
Asset datablocks, libraries, browser and shelf

  
Interest
Audio

  
Interest
Automated Testing

  
Interest
Blender Asset Bundle

  
Interest
BlendFile

  
Interest
Code Documentation
Code comments, Python/RNA API descriptions

  
Interest
Collada

  
Interest
Compatibility
Backward and forward compatibility

  
Interest
Compositing

  
Interest
Core

  
Interest
Cycles

  
Interest
Dependency Graph

  
Interest
Development Management

  
Interest
EEVEE

  
Interest
Freestyle

  
Interest
Geometry Nodes

  
Interest
Grease Pencil

  
Interest
ID Management

  
Interest
Images & Movies

  
Interest
Import Export

  
Interest
Line Art

  
Interest
Masking

  
Interest
Metal

  
Interest
Modeling

  
Interest
Modifiers

  
Interest
Motion Tracking

  
Interest
Nodes & Physics

  
Interest
OpenGL

  
Interest
Overlay

  
Interest
Overrides

  
Interest
Performance

  
Interest
Physics

  
Interest
Pipeline, Assets & IO

  
Interest
Platforms, Builds & Tests

  
Interest
Python API

  
Interest
Render & Cycles

  
Interest
Render Pipeline

  
Interest
Sculpt, Paint & Texture

  
Interest
Text Editor

  
Interest
Translations

  
Interest
Triaging

  
Interest
Undo

  
Interest
USD

  
Interest
User Interface

  
Interest
UV Editing

  
Interest
VFX & Video

  
Interest
Video Sequencer

  
Interest
Viewport & EEVEE

  
Interest
Virtual Reality

  
Interest
Vulkan

  
Interest
Wayland
Wayland windowing on Unix

  
Interest
Workbench

  
Interest: X11

Xorg/X11 windowing

  
Legacy
Asset Browser Project

Archived

  
Legacy
Blender 2.8 Project

Archived

  
Legacy
Milestone 1: Basic, Local Asset Browser

Archived

  
Legacy
OpenGL Error

Archived

  
Meta
Good First Issue

  
Meta
Papercut

  
Meta
Retrospective

  
Meta
Security
Related to security, see policy: https://developer.blender.org/docs/handbook/bug_reports/vulnerability_reports/

  
Module
Animation & Rigging

  
Module
Core

  
Module
Development Management

  
Module
Grease Pencil

  
Module
Modeling

  
Module
Nodes & Physics

  
Module
Pipeline, Assets & IO

  
Module
Platforms, Builds & Tests

  
Module
Python API

  
Module
Render & Cycles

  
Module
Sculpt, Paint & Texture

  
Module
Triaging

  
Module
User Interface

  
Module
VFX & Video

  
Module
Viewport & EEVEE

  
Platform
FreeBSD

  
Platform
Linux

  
Platform
macOS

  
Platform
Windows

  
Severity
High

  
Severity
Low

  
Severity
Normal

  
Severity
Unbreak Now!

  
Status
Archived

  
Status
Confirmed

  
Status
Duplicate

  
Status
Needs Info from Developers

  
Status
Needs Information from User

  
Status
Needs Triage

  
Status
Resolved

  
Type
Bug

  
Type
Design

  
Type
Known Issue

  
Type
Patch

Archived

  
Type
Report

Archived

  
Type
To Do

No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#108115
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?