Dual monitor on separate graphics card driver error #62651

Closed
opened 4 years ago by u_n_ur_cat · 52 comments

System Information
Operating system: Windows 10 Pro 64 Bit
Graphics card: 2 x GTX1080
Graphics driver: 25.21.14.1891

Blender Version
Broken: 2.80, bf9904ec80

Short description of error

Blender crashes when i try to open a blend file that has any floating window open besides the main UI Window, with the following error " Blender requires a graphics driver with at list OpenGL 3.3 support "
0001.jpg

I believe this is happening because i have my monitors plunged in to two separate video card of same make and model,
002.jpg

a test blend file that produces this error test001.blend

**System Information** Operating system: Windows 10 Pro 64 Bit Graphics card: 2 x GTX1080 Graphics driver: 25.21.14.1891 **Blender Version** Broken: 2.80, bf9904ec8018 **Short description of error** Blender crashes when i try to open a blend file that has any floating window open besides the main UI Window, with the following error " Blender requires a graphics driver with at list OpenGL 3.3 support " ![0001.jpg](https://archive.blender.org/developer/F6834181/0001.jpg) I believe this is happening because i have my monitors plunged in to two separate video card of same make and model, ![002.jpg](https://archive.blender.org/developer/F6834202/002.jpg) a test blend file that produces this error [test001.blend](https://archive.blender.org/developer/F6834212/test001.blend)
Poster

Added subscriber: @u_n_ur_cat

Added subscriber: @u_n_ur_cat
Collaborator

#89796 was marked as duplicate of this issue

#89796 was marked as duplicate of this issue
Collaborator

#85628 was marked as duplicate of this issue

#85628 was marked as duplicate of this issue
Collaborator

#94462 was marked as duplicate of this issue

#94462 was marked as duplicate of this issue
Collaborator

#88918 was marked as duplicate of this issue

#88918 was marked as duplicate of this issue
Collaborator

#83320 was marked as duplicate of this issue

#83320 was marked as duplicate of this issue
Collaborator

#82410 was marked as duplicate of this issue

#82410 was marked as duplicate of this issue
Collaborator

#79065 was marked as duplicate of this issue

#79065 was marked as duplicate of this issue
Collaborator

#77089 was marked as duplicate of this issue

#77089 was marked as duplicate of this issue
Collaborator

#75386 was marked as duplicate of this issue

#75386 was marked as duplicate of this issue
Collaborator

#74479 was marked as duplicate of this issue

#74479 was marked as duplicate of this issue
Collaborator

#60019 was marked as duplicate of this issue

#60019 was marked as duplicate of this issue
Collaborator

#63013 was marked as duplicate of this issue

#63013 was marked as duplicate of this issue

Added subscriber: @GavinScott

Added subscriber: @GavinScott

I'll just throw in that if your 1080s do indeed have DVI-D output as shown in the screenshot, you can probably use a $6 DVI-D to HDMI cable to let you drive both monitors from a single card, which shouldn't be a problem for a 1080 and two HD displays.

I'll just throw in that if your 1080s do indeed have DVI-D output as shown in the screenshot, you can probably use a $6 DVI-D to HDMI cable to let you drive both monitors from a single card, which shouldn't be a problem for a 1080 and two HD displays.
ZedDB commented 4 years ago
Collaborator

Added subscriber: @ZedDB

Added subscriber: @ZedDB
ZedDB commented 4 years ago
Collaborator

Does it work if you only use one GPU to render opengl?
image.png

Probably a duplicate of: #61995

Does it work if you only use one GPU to render opengl? ![image.png](https://archive.blender.org/developer/F6815682/image.png) Probably a duplicate of: #61995
Poster

Yes, that seems to work, I no longer get the error when opening files with floating windows.

Thanks

Yes, that seems to work, I no longer get the error when opening files with floating windows. Thanks
brecht commented 4 years ago
Owner

Added subscriber: @ssh4

Added subscriber: @ssh4
brecht changed title from Duel Monitor on separate Graphics card Driver Erroe to Dual monitor on separate graphics card driver error 4 years ago
brecht commented 4 years ago
Owner

Added subscriber: @brecht

Added subscriber: @brecht
brecht commented 4 years ago
Owner

While there is a workaround, we should try to fix this.

I haven't tested this setup myself, but since it's been reported by 3 users would consider it confirmed.

While there is a workaround, we should try to fix this. I haven't tested this setup myself, but since it's been reported by 3 users would consider it confirmed.
ssh4 commented 4 years ago

Can confirm that monitors should be connected to different video cards.
And using only one GPU to render opengl fix this issue.

Can confirm that monitors should be connected to different video cards. And using only one GPU to render opengl fix this issue.
fclem was assigned by ZedDB 4 years ago
ZedDB commented 4 years ago
Collaborator

Added subscriber: @fclem

Added subscriber: @fclem
ZedDB commented 4 years ago
Collaborator

@fclem I think we talked about this previously. I don't think blender does anything special with multi GPU/monitor setups. So I suspect that this is an issue on the driver side of things?

@fclem I think we talked about this previously. I don't think blender does anything special with multi GPU/monitor setups. So I suspect that this is an issue on the driver side of things?
Poster

In #62651#650092, @ZedDB wrote:
@fclem I think we talked about this previously. I don't think blender does anything special with multi GPU/monitor setups. So I suspect that this is an issue on the driver side of things?

If it helps i didn't face this problem in blender 2.7 ... its only on 2.8 in my case.

> In #62651#650092, @ZedDB wrote: > @fclem I think we talked about this previously. I don't think blender does anything special with multi GPU/monitor setups. So I suspect that this is an issue on the driver side of things? If it helps i didn't face this problem in blender 2.7 ... its only on 2.8 in my case.
brecht commented 4 years ago
Owner
Added subscribers: @jonathanwills, @Archost, @WillFalcon, @sjoerdsein, @SubliminalArtist
fclem was unassigned by dfelinto 3 years ago
Collaborator

Added subscriber: @Jeroen-Bakker

Added subscriber: @Jeroen-Bakker
Collaborator

I will set this as a known issue. Can be how OpenGL resources are shared between the two graphic cards. Blender OpenGL assumes that there is only a single GPU to take care of.

I will set this as a known issue. Can be how OpenGL resources are shared between the two graphic cards. Blender OpenGL assumes that there is only a single GPU to take care of.
brecht commented 3 years ago
Owner

Added subscribers: @yak27, @mano-wii, @girafic

Added subscribers: @yak27, @mano-wii, @girafic
brecht commented 3 years ago
Owner

I think this definitely a bug, and almost a high priority one. This is a common setup and it shouldn't fail by default.

We may be able to only use one GPU, but then we should fix GHOST to enforce that somehow.

I think this definitely a bug, and almost a high priority one. This is a common setup and it shouldn't fail by default. We may be able to only use one GPU, but then we should fix GHOST to enforce that somehow.
brecht commented 3 years ago
Owner

Worst case, we could try to show a better error message that explains how to work around this problem.

Worst case, we could try to show a better error message that explains how to work around this problem.
iss commented 3 years ago
Collaborator

Added subscribers: @vicy.1832, @iss, @AnthonyEdlin

Added subscribers: @vicy.1832, @iss, @AnthonyEdlin
iss commented 3 years ago
Collaborator

Added subscriber: @skantron

Added subscriber: @skantron
Ykadam commented 3 years ago

Added subscriber: @Ykadam

Added subscriber: @Ykadam
Ykadam commented 3 years ago

2020-07-14 02_53_13-NVIDIA Control Panel.jpg

![2020-07-14 02_53_13-NVIDIA Control Panel.jpg](https://archive.blender.org/developer/F8691966/2020-07-14_02_53_13-NVIDIA_Control_Panel.jpg)

Removed subscriber: @sjoerdsein

Removed subscriber: @sjoerdsein
iss commented 3 years ago
Collaborator

Added subscriber: @Andrei-Feheregyhazi

Added subscriber: @Andrei-Feheregyhazi
iss commented 2 years ago
Collaborator

Added subscriber: @CuttlefishKitch

Added subscriber: @CuttlefishKitch
iss commented 2 years ago
Collaborator

Added subscriber: @cata_cg

Added subscriber: @cata_cg
iss commented 2 years ago
Collaborator

Added subscriber: @JAPfeiffer

Added subscriber: @JAPfeiffer

Added subscriber: @glenmoyes

Added subscriber: @glenmoyes

To add an update on this issue, I got this bug in Blender 2.93 LTS. Plugging all monitors into the same card made it work. However, 2.91 didn't give me this issue (plugging multiple monitors across two 1080s). Same driver version in both tests. Regression between the two Blender versions perhaps?

To add an update on this issue, I got this bug in Blender 2.93 LTS. Plugging all monitors into the same card made it work. However, 2.91 didn't give me this issue (plugging multiple monitors across two 1080s). Same driver version in both tests. Regression between the two Blender versions perhaps?
Collaborator

Added subscribers: @chengll, @Harley

Added subscribers: @chengll, @Harley

Removed subscriber: @glenmoyes

Removed subscriber: @glenmoyes
Collaborator
Added subscribers: @Prodeous, @Pierre-39, @PratikPB2123, @DuarteRamos
Collaborator

Added subscriber: @patricio.davila.ca

Added subscriber: @patricio.davila.ca
Collaborator

This issue was referenced by fd1078e105

This issue was referenced by fd1078e1055e6932fc539a1fae4c7d433b1839d9
Harley commented 1 year ago
Collaborator

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Harley closed this issue 1 year ago
Harley self-assigned this 1 year ago

Added subscriber: @akcamay

Added subscriber: @akcamay

Thank you all; this will help and I will try to hook up my three screens on the same card as I think this is what you are saying.

Thank you all; this will help and I will try to hook up my three screens on the same card as I think this is what you are saying.

Added subscriber: @LittleRobotGuys

Added subscriber: @LittleRobotGuys

I have two screens set up where each is plugged into a different Nvidia GTX 960 that are connected by SLI. When running Blender on either I can open it fine; when saving or doing many other operations (like changing add-ons) with the Blender window on the SECONDARY screen it gives this error. It's like it forgets what driver to use, checks, and the secondary screen can only reply with the old non-OpenGL 3.3 file.

I have two screens set up where each is plugged into a different Nvidia GTX 960 that are connected by SLI. When running Blender on either I can open it fine; when saving or doing many other operations (like changing add-ons) with the Blender window on the SECONDARY screen it gives this error. It's like it forgets what driver to use, checks, and the secondary screen can only reply with the old non-OpenGL 3.3 file.
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
15 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

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