3D View split when using cycles render and two graphics cards (Texture problem) #30140

Closed
opened 2012-02-10 21:55:48 +01:00 by Tobias Jeglorz · 4 comments

%%%The 3D View is exactly split in two areas, when using cycles with my two cards. If I use only one card, there is no problem.
For further details, please have a look at the attached pdf file.

Blender 2.61.4 (r43946) Release Candidates
(blender-2.62rc1-linux-glibc27-x86_64.tar.bz2 2012-Feb-07 15:18:07 44.1M application/x-bzip)

Configuration and System:

Prozessor (CPU): AMD Phenom(tm) II X4 965 Processor
RAM 8GB

GPU1: NVIDIA 275 GTX, 896 MB
GPU2: NVIDIA 560 GTX, 2048 MB

Kernel:Linux 2.6.37.6-0.11-desktop x86_64
Distribution:openSUSE 11.4 (x86_64)
KDE:4.6.00 (4.6.0) "release 6"

NVIDIA Driver 290.10

%%%

%%%The 3D View is exactly split in two areas, when using cycles with my two cards. If I use only one card, there is no problem. For further details, please have a look at the attached pdf file. Blender 2.61.4 (r43946) Release Candidates (blender-2.62rc1-linux-glibc27-x86_64.tar.bz2 2012-Feb-07 15:18:07 44.1M application/x-bzip) Configuration and System: Prozessor (CPU): AMD Phenom(tm) II X4 965 Processor RAM 8GB GPU1: NVIDIA 275 GTX, 896 MB GPU2: NVIDIA 560 GTX, 2048 MB Kernel:Linux 2.6.37.6-0.11-desktop x86_64 Distribution:openSUSE 11.4 (x86_64) KDE:4.6.00 (4.6.0) "release 6" NVIDIA Driver 290.10 %%%
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

%%%I think the cause of the error is the "mix-shading-node". Using the mix-shader node with two GPU's show this error. If I use only one GPU there is no problem.
Using the CPU there is also no problem.
%%%

%%%I think the cause of the error is the "mix-shading-node". Using the mix-shader node with two GPU's show this error. If I use only one GPU there is no problem. Using the CPU there is also no problem. %%%

%%%Thanks for investigating, it is indeed because of the mix shading node. The problem is that the 275 GTX and 560 GTX have somewhat different compute capabilities, and handling of mix nodes is different. This is difficult to solve, and there's various other things like transparent shadows or render passes that won't work on the 275 GTX. I've committed a change now in svn so that it's no longer possible to do multi device rendering in this case.%%%

%%%Thanks for investigating, it is indeed because of the mix shading node. The problem is that the 275 GTX and 560 GTX have somewhat different compute capabilities, and handling of mix nodes is different. This is difficult to solve, and there's various other things like transparent shadows or render passes that won't work on the 275 GTX. I've committed a change now in svn so that it's no longer possible to do multi device rendering in this case.%%%

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
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
2 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#30140
No description provided.