Dual monitor on separate graphics card driver error #62651

Closed
opened 2019-03-16 13:00:17 +01:00 by Alex Atiq · 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)
Author

Added subscriber: @u_n_ur_cat

Added subscriber: @u_n_ur_cat

#89796 was marked as duplicate of this issue

#89796 was marked as duplicate of this issue

#85628 was marked as duplicate of this issue

#85628 was marked as duplicate of this issue

#94462 was marked as duplicate of this issue

#94462 was marked as duplicate of this issue

#88918 was marked as duplicate of this issue

#88918 was marked as duplicate of this issue

#83320 was marked as duplicate of this issue

#83320 was marked as duplicate of this issue

#82410 was marked as duplicate of this issue

#82410 was marked as duplicate of this issue

#79065 was marked as duplicate of this issue

#79065 was marked as duplicate of this issue

#77089 was marked as duplicate of this issue

#77089 was marked as duplicate of this issue

#75386 was marked as duplicate of this issue

#75386 was marked as duplicate of this issue

#74479 was marked as duplicate of this issue

#74479 was marked as duplicate of this issue

#60019 was marked as duplicate of this issue

#60019 was marked as duplicate of this issue

#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.

Added subscriber: @ZedDB

Added subscriber: @ZedDB

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
Author

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

Added subscriber: @ssh4

Added subscriber: @ssh4
Brecht Van Lommel changed title from Duel Monitor on separate Graphics card Driver Erroe to Dual monitor on separate graphics card driver error 2019-03-27 15:49:40 +01:00

Added subscriber: @brecht

Added subscriber: @brecht

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.

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.
Clément Foucault was assigned by Sebastian Parborg 2019-03-28 11:01:38 +01:00

Added subscriber: @fclem

Added subscriber: @fclem

@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?
Author

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.
Added subscribers: @jonathanwills, @Archost, @WillFalcon, @sjoerdsein, @SubliminalArtist
Clément Foucault was unassigned by Dalai Felinto 2019-12-23 16:34:53 +01:00
Member

Added subscriber: @Jeroen-Bakker

Added subscriber: @Jeroen-Bakker
Member

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.

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

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

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.

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.

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

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

Added subscriber: @skantron

Added subscriber: @skantron

Added subscriber: @Ykadam

Added subscriber: @Ykadam

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

Added subscriber: @Andrei-Feheregyhazi

Added subscriber: @Andrei-Feheregyhazi

Added subscriber: @CuttlefishKitch

Added subscriber: @CuttlefishKitch

Added subscriber: @cata_cg

Added subscriber: @cata_cg

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?
Member

Added subscribers: @chengll, @Harley

Added subscribers: @chengll, @Harley

Removed subscriber: @glenmoyes

Removed subscriber: @glenmoyes
Member

Added subscribers: @Prodeous, @Pierre-39, @PratikPB2123, @DuarteRamos

Added subscribers: @Prodeous, @Pierre-39, @PratikPB2123, @DuarteRamos
Member

Added subscriber: @patricio.davila.ca

Added subscriber: @patricio.davila.ca

This issue was referenced by fd1078e105

This issue was referenced by fd1078e1055e6932fc539a1fae4c7d433b1839d9
Member

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Harley Acheson self-assigned this 2022-01-29 00:20:25 +01:00

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
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
15 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#62651
No description provided.