Cycles Compute Device, 2x GPU option is gone when having 3x GPU cards. #37717

Closed
opened 9 years ago by MartinLindelof · 13 comments

System Information
Win8.1 , nVidia GTX 580 (3 cards)

Blender Version
Broken: Blender 2.69 from buildbot 2013-12-05
Worked: Blender 2.XX rXXXXXX

Short description of error
Under User Preferences > System > Compute Device: I have only the options of using all 3 cards,
or selecting individual cards.

There used to be an option to use 2x GPUs and spare the main GPU0 that drivers OS and Displays.

This is system critical for me, using all 3 cards rendering full HD and my GPU0 reaches 80deg C and the displays go white and I have to reboot.

Exact steps for others to reproduce the error
Based on a (as simple as possible) attached .blend file with minimum amount of steps
Just check Compute Device on a machine with more than 2 cards, if x2 GPU shows up.

**System Information** Win8.1 , nVidia GTX 580 (3 cards) **Blender Version** Broken: Blender 2.69 from buildbot 2013-12-05 Worked: Blender 2.XX rXXXXXX **Short description of error** Under User Preferences > System > Compute Device: I have only the options of using all 3 cards, or selecting individual cards. There used to be an option to use 2x GPUs and spare the main GPU0 that drivers OS and Displays. This is system critical for me, using all 3 cards rendering full HD and my GPU0 reaches 80deg C and the displays go white and I have to reboot. **Exact steps for others to reproduce the error** Based on a (as simple as possible) attached .blend file with minimum amount of steps Just check Compute Device on a machine with more than 2 cards, if x2 GPU shows up.
Poster

Changed status to: 'Open'

Changed status to: 'Open'
Poster

Added subscriber: @MartinLindelof

Added subscriber: @MartinLindelof
brecht commented 9 years ago
Owner

Added subscriber: @brecht

Added subscriber: @brecht
brecht commented 9 years ago
Owner

Was this a change in Blender or in your operating system or graphics driver? Please test with older Blender versions to verify.

The way this works is that cycles tries to detect if one of your graphics card is used for display, and then it offers a configuration with that card excluded. Maybe on Windows 8.1 that doesn't work.

Was this a change in Blender or in your operating system or graphics driver? Please test with older Blender versions to verify. The way this works is that cycles tries to detect if one of your graphics card is used for display, and then it offers a configuration with that card excluded. Maybe on Windows 8.1 that doesn't work.
Poster

Okay, there is no way this could be a setting? Exclude GPU0 use rest.

I have to try and use older versions to see if it has ever worked on Win8.1 I was running Ubuntu before and there for sure it worked.

Okay, there is no way this could be a setting? Exclude GPU0 use rest. I have to try and use older versions to see if it has ever worked on Win8.1 I was running Ubuntu before and there for sure it worked.
Poster

N/A in 2.68 on Win8.1
Ok,probably was so it was only available in Ubuntu.

Can I give a suggestion to have an option to spare the GPU0 device for OS/Display ?
If more than 1 GPUs are available.

N/A in 2.68 on Win8.1 Ok,probably was so it was only available in Ubuntu. Can I give a suggestion to have an option to spare the GPU0 device for OS/Display ? If more than 1 GPUs are available.
cheleb commented 9 years ago

Added subscriber: @cheleb

Added subscriber: @cheleb
cheleb commented 9 years ago

I can confirm this on Win7 64bit NVIDIA driver 331.xx. The last working driver was 327.23. We have several machines with multiple cards in our studio and all of them show this behavior with the newest driver.

I also agree with @MartinLindelof here that it would be much more comfortable to just exclude cards from rendering via checkbox in the blender preferences panel - if at all possible.
The NVIDIA driver somehow doesn't remember which cards were excluded from CUDA processing after driver updates and now is finally completely bogus after the latest update - which is kind of annoying when you have to reconfigure each machine at every driver update.

I can confirm this on Win7 64bit NVIDIA driver 331.xx. The last working driver was 327.23. We have several machines with multiple cards in our studio and all of them show this behavior with the newest driver. I also agree with @MartinLindelof here that it would be much more comfortable to just exclude cards from rendering via checkbox in the blender preferences panel - if at all possible. The NVIDIA driver somehow doesn't remember which cards were excluded from CUDA processing after driver updates and now is finally completely bogus after the latest update - which is kind of annoying when you have to reconfigure each machine at every driver update.
brecht commented 9 years ago
Owner

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
brecht closed this issue 9 years ago
brecht self-assigned this 9 years ago
brecht commented 9 years ago
Owner

It's on my todo list to improve graphics card configuration for 2.70, to allow you to select individual cards and enable/disable them. This is not considered a bug at the moment however.

It's on my todo list to improve graphics card configuration for 2.70, to allow you to select individual cards and enable/disable them. This is not considered a bug at the moment however.

Added subscriber: @STEP-ANI-MOTION

Added subscriber: @STEP-ANI-MOTION

Added subscriber: @kojiroakasama

Added subscriber: @kojiroakasama

Hi, I was just wondering if this feature has been added yet, or has there been a workaround

Hi, I was just wondering if this feature has been added yet, or has there been a workaround
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/Collada
Interest/Compositing
Interest/Core
Interest/Cycles
Interest/Dependency Graph
Interest/Development Management
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/Modeling
Interest/Modifiers
Interest/Motion Tracking
Interest/Nodes & Physics
Interest/Overrides
Interest/Performance
Interest/Performance
Interest/Physics
Interest/Pipeline, Assets & I/O
Interest/Platforms, Builds, Tests & Devices
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
legacy module/Animation & Rigging
legacy module/Core
legacy module/Development Management
legacy module/Eevee & Viewport
legacy module/Grease Pencil
legacy module/Modeling
legacy module/Nodes & Physics
legacy module/Pipeline, Assets & IO
legacy module/Platforms, Builds, Tests & Devices
legacy module/Python API
legacy module/Rendering & Cycles
legacy module/Sculpt, Paint & Texture
legacy module/Triaging
legacy module/User Interface
legacy module/VFX & Video
legacy project/1.0.0-beta.2
legacy project/Asset Browser (Archived)
legacy project/BF Blender: 2.8
legacy project/BF Blender: After Release
legacy project/BF Blender: Next
legacy project/BF Blender: Regressions
legacy project/BF Blender: Unconfirmed
legacy project/Blender 2.70
legacy project/Code Quest
legacy project/Datablocks and Libraries
legacy project/Eevee
legacy project/Game Animation
legacy project/Game Audio
legacy project/Game Data Conversion
legacy project/Game Engine
legacy project/Game Logic
legacy project/Game Physics
legacy project/Game Python
legacy project/Game Rendering
legacy project/Game UI
legacy project/GPU / Viewport
legacy project/GSoC
legacy project/Infrastructure: Websites
legacy project/LibOverrides - Usability and UX
legacy project/Milestone 1: Basic, Local Asset Browser
legacy project/Nodes
legacy project/OpenGL Error
legacy project/Papercut
legacy project/Pose Library Basics
legacy project/Retrospective
legacy project/Tracker Curfew
legacy project/Wintab High Frequency
Meta/Good First Issue
Meta/Papercut
migration/requires-manual-verification
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 › 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 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
5 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#37717
Loading…
There is no content yet.