Rendering error #109841
Labels
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
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#109841
Loading…
Reference in New Issue
Block a user
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?
System Information
Operating system: Windows 11
Graphics card: AMD Ryzen 9 7950X
Blender Version
Broken: (Newest Version)
Worked: (never)
Short description of error
I got a new PC last week and when I try rendering with GPU Compute it gives me an error message
"HIP binary kernel for this graphics card compute capability (10.3) not found"
I bought this computer for faster render speeds and will not achieve it with CPU alone. Do I need a different graphics card?
Exact steps for others to reproduce the error
On Scene tab on right hand side
-Render Engine: Cycles
-Feature set: Supported
-Device: GPU compute
Click edit drop down menu and select preferences.
Click System tab, then select HIP and check boxes for
-AMD Radeon RX 7900 XTX
-AMD Radeon Graphics
-AMD Ryzen 9 7950X 16-Core Processor
Render the scene and the error appears.
Try going into the
HIP
tab and ONLY enabling theRX 7900XTX
. I think the error message means it tries to load the HIP kernels for the integrated GPU on your Ryzen 9 7950X and can't find one.That seemed to fix the render issue. Is there any reason when I try to add an HDRI to a scene, blender will freeze on me.
Blender freezing when you add an HDRi is probably be a bug. Please make a new bug report about that issue.
Note: The reason I'm asking you to create a new bug report is because we like to keep reports to one bug per report so they're easier to manage.
I will leave this report open for a bit and wait for a comment from a developer on whether or not the integrated GPU kernels are expected to not be compiled.
@salipour or @BrianSavery can you comment on this?
Yes this is known. #109841 (comment)
This issue will be fixed by #110907 once it is merged with main.
This issue has been fixed with
c6f5915bc8