--cycles-device command line option does nothing #104634
Labels
No Label
Meta
Good First Issue
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 & Devices
Module
Python API
Module
Rendering & Cycles
Module
Sculpt, Paint & Texture
Module
User Interface
Module
VFX & Video
Priority
High
Priority
Low
Priority
Normal
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Information 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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-manual#104634
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?
Page Information
File:
N/A
Blender Version:
4.0
Short description of error
The
--cycles-device
command line option does nothing.When attempting to setup Blender on the render farm, I pass the command line option as follows:
blender .\scene.blend -o out.exr --background -E CYCLES -f 1 -- --cycles-device OPTIX --cycles-print-stats
The scene renders using the CPU only and no GPU.
I am guessing that the
--cycles-device
option is supposed to act the same as going to Preferences > System > cycles Render Devices and selectingOptiX
? If not, what is this option for?I am aware that if I do set the preferences manually on a machine, then that particular machine will rendering using the GPUs, however because I am looking to integrate this into our farm, (and everything on our farm is run via Rez), I do not want to have to manually go to every machine, open up Blender and set this via the UI.
If the option indeed does nothing, it would be better to report that in the Blender project instead. We won't be able to help you much here in the manual project, I'm afraid - the documentation comes straight from
blender -h
, so in that regard, there's nothing wrong with it.