defining cycles render device in edit>preferences does not change the device used by cycles in the properties(workspace)>render tab #114563

New Issue

Daniel L. Travieso · 2023-11-07T05:10:10+01:00

2023-11-07 05:10:10 +01:00

System Information
Operating system: win 10, latest update
Graphics card: nvidia rtx 2060

Blender Version
Broken: blender 3.6.5 LTS
Worked: unknown (did it ever?)

SHORT VIDEO DEMONSTRATION OF THE BUG:
https://youtu.be/OrMVXZRdWFY

defining Cycles Render Devices in System settings has no effect on the 'Device' dropdown default selection of the Properties workspace (Shift F7). It should be linked but it is not adjusting to the user defined System preference by default. Make user System preference choice the default in the Properties workspace, other Render choices OPTIONAL, instead of using the default (CPU) and user cofiguration being OPTIONAL?
[Alternatively set/modify the most powerful checkboxed one as default, not the weakest one]

launch blender 3.6.5 LTS
go to edit -> Preferences
in burger menu select System
in the first line on the right under Cycles Render Devices pick either CUDA or OptiX and checkbox both your GPU and CPU
save settings
on the right go to the "Properties" workspace (the "Shift+F7" one, confusing name btw, just call it the dashboard because what's under the dashboard of every car? a ton of knobs and sliders, either digital or physical) and select the Render tab (2nd from top)
select Cycles

notice how CPU is still the default even though you checkboxed a superior device in the Preferences before

IMO something is redundant here. EITHER the System section is inadequately labeled [or redundant altogether] (should probably be called "Hardware render technology preference and permitted devices - check all for coop-effort render" or somesuch if I understand it right) OR it isn't switching to the most powerful checked device in the Properties workspace->Render tab automatically after being defined in the System preferences, which it should when a GPU is checked.
There's no reason to remain on "CPU"-default in the Render properties when a GPU has been 'permitted' to work. Why, why, why are these configuration options not linked to each other, at least one-directional (from Preferences to Properties only, if GPU is checked it should be automatically set-to in the dropdown of the Properties workspace/Render tab/Cycles engine settings)?

The bug is that the device is not being set to the user's-'System preferece'-choice in the properties workspace/render tab/cycles render engine/Device-dropdown.

**System Information** Operating system: win 10, latest update Graphics card: nvidia rtx 2060 **Blender Version** Broken: blender 3.6.5 LTS Worked: unknown (did it ever?) SHORT VIDEO DEMONSTRATION OF THE BUG: https://youtu.be/OrMVXZRdWFY defining Cycles Render Devices in System settings has no effect on the 'Device' dropdown default selection of the Properties workspace (Shift F7). It should be linked but it is not adjusting to the user defined System preference by default. Make user System preference choice the default in the Properties workspace, other Render choices OPTIONAL, instead of using the default (CPU) and user cofiguration being OPTIONAL? [Alternatively set/modify the most powerful checkboxed one as default, not the weakest one] - launch blender 3.6.5 LTS - go to edit -> Preferences - in burger menu select System - in the first line on the right under Cycles Render Devices pick either CUDA or OptiX and checkbox both your GPU and CPU - save settings - on the right go to the "Properties" workspace (the "Shift+F7" one, confusing name btw, just call it the dashboard because what's under the dashboard of every car? a ton of knobs and sliders, either digital or physical) and select the Render tab (2nd from top) - select Cycles notice how CPU is still the default even though you checkboxed a superior device in the Preferences before IMO something is redundant here. EITHER the System section is inadequately labeled [or redundant altogether] (should probably be called "Hardware render technology preference and permitted devices - check all for coop-effort render" or somesuch if I understand it right) OR it isn't switching to the most powerful checked device in the Properties workspace->Render tab automatically after being defined in the System preferences, which it should when a GPU is checked. There's no reason to remain on "CPU"-default in the Render properties when a GPU has been 'permitted' to work. Why, why, why are these configuration options not linked to each other, at least one-directional (from Preferences to Properties only, if GPU is checked it should be automatically set-to in the dropdown of the Properties workspace/Render tab/Cycles engine settings)? The bug is that the device is not being set to the user's-'System preferece'-choice in the properties workspace/render tab/cycles render engine/Device-dropdown.

Daniel L. Travieso added the

labels 2023-11-07 05:10:10 +01:00

Pratik Borhade commented

2023-11-07 10:31:53 +01:00

Hi, thanks for the report. Not a bug, this is mentioned in the manual too. You'll have to choose between CPU and GPU in properties tab.
The issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors.
For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Hi, thanks for the report. Not a bug, this is mentioned in the [manual too](https://docs.blender.org/manual/en/latest/render/cycles/gpu_rendering.html#:~:text=To%20enable%20GPU%20rendering%2C%20go%20into%20the%20Preferences%20%E2%80%A3%20System%20%E2%80%A3%20Cycles%20Render%20Devices%2C%20and%20select%20either%20CUDA%2C%20OptiX%2C%20HIP%2C%20oneAPI%2C%20or%20Metal.%20Next%2C%20you%20must%20configure%20each%20scene%20to%20use%20GPU%20rendering%20in%20Properties%20%E2%80%A3%20Render%20%E2%80%A3%20Device). You'll have to choose between CPU and GPU in properties tab. The issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors. For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Pratik Borhade closed this issue

2023-11-07 10:31:56 +01:00

Blender Bot added

and removed

labels 2023-11-07 10:31:57 +01:00

Daniel L. Travieso commented

2023-11-07 17:28:20 +01:00

not a bug? your software behaving in an unexpected way, having a mind of its own basically and that is not a bug? I pick GPU and the software says "no, you have to pick it over here as well". WHY?

As the user I expect the GPU (because more powerful in most cases, CPU weaker in most cases) to be selected WHEN CHOSEN in the Preferences. Expectation is not met by the software, instead you make us double and tripple select what we want to get an expected result. How is that not a bug?

not a bug? your software behaving in an unexpected way, having a mind of its own basically and that is not a bug? I pick GPU and the software says "no, you have to pick it over here as well". WHY? As the user I expect the GPU (because more powerful in **most** cases, CPU weaker in most cases) to be selected **WHEN CHOSEN** in the Preferences. Expectation is not met by the software, instead you make us double and tripple select what we want to get an expected result. How is that not a bug?

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

defining cycles render device in edit>preferences does not change the device used by cycles in the properties(workspace)>render tab #114563