GPU Compute option for cycles incorrectly disabled. #73676
Labels
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#73676
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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 10 Professional
Graphics card:
Nvidia GTX 1080
Blender Version
Broken: 2.82 Beta (all versions going back at least a month)
Worked: 2.81a
Short description of error
GPU Compute is greyed out in the cycles render properties and rendering is done by the CPU. If I go into Preferences -> System, add my CPU as a CUDA target then the GPU compute option is no longer greyed out. I then untick the CPU and rendering is then done on the GPU instead of the CPU. I need to do this process every time I restart Blender in order to use GPU rendering.
Exact steps for others to reproduce the error
This happens in every system file and on every version of 2.82. Reproduction steps are to start with the default scene, select Cycles as renderer. GPU compute is disabled.
Added subscriber: @huttbutter
Added subscriber: @rjg
Changed status from 'Needs Triage' to: 'Needs User Info'
You shouldn't have to enable / disable the CPU in the CUDA tab if your goal it to render on the GPU.
GPU is being correctly identified as a CUDA device in preferences, but not in Render Properties.
And it definitely is running renders on the GPU, obviously there's a huge speed difference and I can see the compute core on the GPU going to 100% in windows task manager. :)
What I meant was that the CUDA tab is still selected (highlighted in blue) and that you're not switching to a different tab (None, OpenCL, Optix).
Does this issue only affect your selection for GPU rendering or are other preferences also not saved/applied correctly?
Oh, right, yes then I'm still on the CUDA tab. I've not seen any other problems with preferences. As far as I can tell the preference IS being set (and, in fact, automatically detected correctly), but perhaps it's not got the right value when read by Render Properties initially. Hmm.
Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'
Added subscriber: @MistahX99
Same card same problem although I'm on 2.80
Added subscriber: @S.Fairfoot
This issue is present on my system as well using a GTx 1070.
Did a driver update on the GPU and still need to disable the CPU in preferences before the GPU option in cycles is no longer greyed out.
Before most recent updates of GPU and other system updates together with a new SSD installation, this issue was not present.
Everyone affected by this issue, please try if it is still present in Blender 2.83 starting with the factory default settings.
Added subscriber: @Jeroen-Bakker
Changed status from 'Needs Developer To Reproduce' to: 'Needs User Info'
There is no mentioning of any driver versions in this report. Can anyone go to Blender's Help menu and Press Save System Info... This will generate a file with the drivers versions and other related info what could perhaps find the cause. Please upload that file here.
Changed status from 'Needs User Info' to: 'Archived'
No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.
Thanks again for the report. If the problem persists please open a new report with the required information.