Can't force the detection of OpenCL devices #73734

Closed
opened 2020-02-11 17:31:09 +01:00 by Kévin B · 15 comments

Blender Version
Broken: maybe since 2.80?

Short description of error
At some point it was possible to force an OpenCL device to be picked up with CYCLES_OPENCL_SPLIT_KERNEL_TEST=1 in the environnement but it's apprently gone. I can see in opencl_util.cpp:861 that a flag exists for that very reason but it seems it was never implemented, could it be possible to set that flag to true with an option/env variable?

**Blender Version** Broken: maybe since 2.80? **Short description of error** At some point it was possible to force an OpenCL device to be picked up with `CYCLES_OPENCL_SPLIT_KERNEL_TEST=1` in the environnement but it's apprently gone. I can see in [opencl_util.cpp:861 ](https://developer.blender.org/diffusion/B/browse/master/intern/cycles/device/opencl/opencl_util.cpp$861) that a flag exists for that very reason but it seems it was never implemented, could it be possible to set that flag to true with an option/env variable?
Author

Added subscriber: @Tzig

Added subscriber: @Tzig
Member

Added subscribers: @Jeroen-Bakker, @brecht, @LazyDodo

Added subscribers: @Jeroen-Bakker, @brecht, @LazyDodo
Member

I have to admit, this has annoyed me for the longest time as well, previously it was still possible to test opencl on nvidia using the cycles debug menu, but that has broken somewhere as well during one of @Jeroen-Bakker 's refactors somewhere during 2.80.

which makes testing kernel changes more annoying than it should be , can we restore the functionality of the debug menu to either it's former glory or decide we don't care and remove the dead options from it

cc: @brecht

I have to admit, this has annoyed me for the longest time as well, previously it was still possible to test opencl on nvidia using the cycles debug menu, but that has broken somewhere as well during one of @Jeroen-Bakker 's refactors somewhere during 2.80. which makes testing kernel changes more annoying than it should be , can we restore the functionality of the debug menu to either it's former glory or decide we don't care and remove the dead options from it cc: @brecht

Added subscriber: @mano-wii

Added subscriber: @mano-wii

We no longer have the opencl mega kernel 949ab753bb
The kernel is splitted by default.

I don't understand the difference that this option would make. (We can't just bring the mega kernel back).

We no longer have the opencl mega kernel 949ab753bb The kernel is splitted by default. I don't understand the difference that this option would make. (We can't just bring the mega kernel back).
Member

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'

Added subscriber: @TomG

Added subscriber: @TomG

Could you re-enable AMD 7870HD series for Cycles/OpenCL which were deprecated in Blender 2.78?

yuiotzghdf.JPG

Could you re-enable AMD 7870HD series for Cycles/OpenCL which were deprecated in Blender 2.78? ![yuiotzghdf.JPG](https://archive.blender.org/developer/F8385637/yuiotzghdf.JPG)

We are unlikely to bring back support for cards that were deprecated. I don't think the reason behind that decision has changed as the graphics card has not received driver updates for quite a while.

We are unlikely to bring back support for cards that were deprecated. I don't think the reason behind that decision has changed as the graphics card has not received driver updates for quite a while.

In #73734#884530, @brecht wrote:
We are unlikely to bring back support for cards that were deprecated. I don't think the reason behind that decision has changed as the graphics card has not received driver updates for quite a while.

There was a glitch when rendering hair and microdisplacement with OpenCl on that card. Everything else worked.

> In #73734#884530, @brecht wrote: > We are unlikely to bring back support for cards that were deprecated. I don't think the reason behind that decision has changed as the graphics card has not received driver updates for quite a while. There was a glitch when rendering hair and microdisplacement with OpenCl on that card. Everything else worked.

This issue was referenced by blender/cycles@6b063eb75f

This issue was referenced by blender/cycles@6b063eb75f6895cd4592bd739adffe90ecaa5de9
Member

I brought back the environment variable in D7202 to enable testing on unsupported hardware, leaving this ticket open though since the debug menu should still be either fixed or removed.

I brought back the environment variable in [D7202](https://archive.blender.org/developer/D7202) to enable testing on unsupported hardware, leaving this ticket open though since the debug menu should still be either fixed or removed.

Added subscriber: @ThomasDinges

Added subscriber: @ThomasDinges

Changed status from 'Confirmed' to: 'Archived'

Changed status from 'Confirmed' to: 'Archived'

OpenCL rendering support was removed in Blender 3.0.
The combination of the limited Cycles kernel implementation, driver bugs, and stalled OpenCL standard
has made maintenance too difficult. Thanks for all your reports, but it's unlikely that there will be further fixes for OpenCL.

For AMD GPUs, there is a new backend based on the HIP platform.
In Blender 3.0, this is supported on Windows with RDNA and RDNA2 generation discrete graphics cards.
It includes Radeon RX 5000 and RX 6000 series GPUs. Driver version Radeon Pro 21.Q4 or newer is required.

https://wiki.blender.org/wiki/Reference/Release_Notes/3.0/Cycles
https://code.blender.org/2021/11/next-level-support-for-amd-gpus/

OpenCL rendering support was removed in Blender 3.0. The combination of the limited Cycles kernel implementation, driver bugs, and stalled OpenCL standard has made maintenance too difficult. Thanks for all your reports, but it's unlikely that there will be further fixes for OpenCL. For AMD GPUs, there is a new backend based on the HIP platform. In Blender 3.0, this is supported on Windows with RDNA and RDNA2 generation discrete graphics cards. It includes Radeon RX 5000 and RX 6000 series GPUs. Driver version Radeon Pro 21.Q4 or newer is required. https://wiki.blender.org/wiki/Reference/Release_Notes/3.0/Cycles https://code.blender.org/2021/11/next-level-support-for-amd-gpus/
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
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
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
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
EEVEE & Viewport
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
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
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
8 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#73734
No description provided.