Blender does not recognize and use my Nvidia GPU. It only uses the integrated intel graphics card #72841

Closed
opened 2020-01-01 22:36:18 +01:00 by Matej Junk · 24 comments

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: Intel(R) HD Graphics 530 Intel 4.4.0 - Build 21.20.16.4550

Blender Version
Broken: version: 2.82 (sub 6), branch: master, commit date: 2019-12-30 18:20, hash: 56ef761381
Worked: blender-2.82-b03066f7ee07-windows64

Short description of error
Blender does not recognize and use my Nvidia GPU. It only uses the integrated intel graphics card EDIT: for viewport open-gl rendering.

Exact steps for others to reproduce the error
On my system this can be observed in the Task Manager, by panning or orbiting around with the default scene.
The Task Manager shows 0% activity for the n-vidia gpu, for every blender version upwards form the working one mentioned above.

The following are the specs of my N-vidia GPU acquired from the working version if I were to report the bug via Help>Report a Bug link in Blender:
Graphics card: GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66

I also made sure I have the latest n-vidia drivers.

Regards,
Matej

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: Intel(R) HD Graphics 530 Intel 4.4.0 - Build 21.20.16.4550 **Blender Version** Broken: version: 2.82 (sub 6), branch: master, commit date: 2019-12-30 18:20, hash: `56ef761381` Worked: blender-2.82-b03066f7ee07-windows64 **Short description of error** Blender does not recognize and use my Nvidia GPU. It only uses the integrated intel graphics card EDIT: **for viewport open-gl rendering**. **Exact steps for others to reproduce the error** On my system this can be observed in the Task Manager, by panning or orbiting around with the default scene. The Task Manager shows 0% activity for the n-vidia gpu, for every blender version upwards form the working one mentioned above. The following are the specs of my N-vidia GPU acquired from the working version if I were to report the bug via Help>Report a Bug link in Blender: Graphics card: GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66 I also made sure I have the latest n-vidia drivers. Regards, Matej
Author

Added subscriber: @mjunk

Added subscriber: @mjunk

Added subscriber: @StephenSwaney

Added subscriber: @StephenSwaney

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'

I don't see a 960M in the list of supported NVidia cards (corrections welcome)

Did you select your card in User Prefs -> System ?

I don't see a 960M in the list of supported NVidia cards (corrections welcome) Did you select your card in User Prefs -> System ?

Added subscriber: @Stan_Pancakes

Added subscriber: @Stan_Pancakes

The Task Manager may not be representative of the situation, nor is simple panning around. Since the Help -> Report a Bug button does paste the NVIDIA GPU info, it stands to reason Blender does use that GPU. A better way to verify this is to use the Help -> Save System Info function and read the resulting text file (look for the OpenGL section).

The Task Manager may not be representative of the situation, nor is simple panning around. Since the Help -> Report a Bug button does paste the NVIDIA GPU info, it stands to reason Blender does use that GPU. A better way to verify this is to use the Help -> Save System Info function and read the resulting text file (look for the OpenGL section).
Author

In #72841#840878, @StephenSwaney wrote:
I don't see a 960M in the list of supported NVidia cards (corrections welcome)

Did you select your card in User Prefs -> System ?

Yes I have the card selected in User Prefs. It worked flawlessly till a few weeks ago till I noticed considerable lag in the viewport with heavier scenes and I started investigating.
I found the last working version from 12.12.2019, which is noted above. I doubt that the card wouldn't be supported - it is from a 3 years old Asus gaming notebook.

> In #72841#840878, @StephenSwaney wrote: > I don't see a 960M in the list of supported NVidia cards (corrections welcome) > > Did you select your card in User Prefs -> System ? Yes I have the card selected in User Prefs. It worked flawlessly till a few weeks ago till I noticed considerable lag in the viewport with heavier scenes and I started investigating. I found the last working version from 12.12.2019, which is noted above. I doubt that the card wouldn't be supported - it is from a 3 years old Asus gaming notebook.
Author

In #72841#841000, @Stan_Pancakes wrote:
The Task Manager may not be representative of the situation, nor is simple panning around. Since the Help -> Report a Bug button does paste the NVIDIA GPU info, it stands to reason Blender does use that GPU. A better way to verify this is to use the Help -> Save System Info function and read the resulting text file (look for the OpenGL section).

I probably wasn't clear enough, the N-vidia GPU pasted info is from the version of blender that worked from 12.12.2019. The latest versions of blender display only the info from my integrated intel GPU as it can be seen from the report above. I also found the last version that worked and pasted it in the worked section of the report.

> In #72841#841000, @Stan_Pancakes wrote: > The Task Manager may not be representative of the situation, nor is simple panning around. Since the Help -> Report a Bug button does paste the NVIDIA GPU info, it stands to reason Blender does use that GPU. A better way to verify this is to use the Help -> Save System Info function and read the resulting text file (look for the OpenGL section). I probably wasn't clear enough, the N-vidia GPU pasted info is from the version of blender that worked from 12.12.2019. The latest versions of blender display only the info from my integrated intel GPU as it can be seen from the report above. I also found the last version that worked and pasted it in the worked section of the report.

Added subscriber: @rjg

Added subscriber: @rjg

@StephenSwaney The 900 series is supported. Any Nvidia GPUs from the GeForce 400 series and later are supported, if they're capable of OpenGL 3.3.

@StephenSwaney The 900 series is supported. Any Nvidia GPUs from the GeForce 400 series and later are supported, if they're capable of OpenGL 3.3.

Added subscriber: @Sergey

Added subscriber: @Sergey

Just to clarify:

  • Do you do have GPU enabled in User Preferences -> System -> CUDA?
  • Do you have Device set to GPU Compute in render panel?
Just to clarify: - Do you do have GPU enabled in User Preferences -> System -> CUDA? - Do you have Device set to GPU Compute in render panel?
Author

In #72841#841210, @Sergey wrote:
Just to clarify:

  • Do you do have GPU enabled in User Preferences -> System -> CUDA?
  • Do you have Device set to GPU Compute in render panel?

Yes, I have both enabled, but I am afraid that I wasn't clear enough that I am talking about the viewport performance, not Final rendering performance. Recent blender versions don't seem to be using my Nvidia gpu for viewport and UI.

> In #72841#841210, @Sergey wrote: > Just to clarify: > > - Do you do have GPU enabled in User Preferences -> System -> CUDA? > - Do you have Device set to GPU Compute in render panel? Yes, I have both enabled, but I am afraid that I wasn't clear enough that I am talking about the **viewport** performance, not Final rendering performance. Recent blender versions don't seem to be using my Nvidia gpu for viewport and UI.

but I am afraid that I wasn't clear enough that I am talking about the viewport performance, not Final rendering performance.

Yeah, well. That is somewhat crucial, isn't it ;) There is "Exact steps for others to reproduce the error" section in the bug report form which is to be taken seriously, otherwise we will not be able to help.

Some more questions:

  • What is the render engine you're using?
  • Does the issue happen with any .blend file? Does it need some specific one? (Attaching simple .blend file where you can easily see the issue is a very good idea, as there might be some setting specific to your setup which will affect on the issue)
  • How do you verify GPU is not used? (If you use Cycles and use System Monitor's GPU utilisation - that wouldn't give you definitive answer because it does not include CUDA cores).

Also, please attach (as a file) system-info.txt generated by Help -> Save System Info.

> but I am afraid that I wasn't clear enough that I am talking about the viewport performance, not Final rendering performance. Yeah, well. That is somewhat crucial, isn't it ;) There is "Exact steps for others to reproduce the error" section in the bug report form which is to be taken seriously, otherwise we will not be able to help. Some more questions: - What is the render engine you're using? - Does the issue happen with any .blend file? Does it need some specific one? (Attaching simple .blend file where you can easily see the issue is a very good idea, as there might be some setting specific to your setup which will affect on the issue) - How do you verify GPU is not used? (If you use Cycles and use System Monitor's GPU utilisation - that wouldn't give you definitive answer because it does not include CUDA cores). Also, please attach (as a file) system-info.txt generated by Help -> Save System Info.
Member

Added subscriber: @EAW

Added subscriber: @EAW
Member

Have you set your NVIDIA graphics card to be used while using Blender in the NVIDIA control panel?

Blender is reporting only the Intel(R) HD Graphics 530 Intel 4.4.0 - Build 21.20.16.4550 card being used for openGL aka EEVEE rendering in 56ef761381

As stated in the manual under troubleshooting,

Laptops
Laptops often have two GPUs for power saving purposes. One slower onboard GPU (typically Intel) and one faster dedicated GPU for a better performance (AMD or NVIDIA).
For the best performance the dedicated GPU should be used for Blender. Which GPU to use for which application can be configured in your graphics driver settings.


See my comment here and the following one about how to change this in Win 10.

Let us know if that works for you.


Triager Note: This appears to be simular to #72447 Did something happen between b03066f7ee and c6ba941339 that could be causing Blender to use integrated graphics instead of NVIDIA on windows laptops?

Have you set your NVIDIA graphics card to be used while using Blender in the NVIDIA control panel? Blender is reporting only the Intel(R) HD Graphics 530 Intel 4.4.0 - Build 21.20.16.4550 card being used for openGL aka EEVEE rendering in 56ef761381 As stated [in the manual under troubleshooting, ](https://docs.blender.org/manual/en/2.81/troubleshooting/gpu/windows/nvidia.html#laptops) > **Laptops** > Laptops often have two GPUs for power saving purposes. One slower onboard GPU (typically Intel) and one faster dedicated GPU for a better performance (AMD or NVIDIA). > For the best performance the dedicated GPU should be used for Blender. Which GPU to use for which application can be configured in your graphics driver settings. ``` ``` See my comment [here and the following one ](https://developer.blender.org/T72447#828971) about how to change this in Win 10. Let us know if that works for you. --- Triager Note: This appears to be simular to #72447 Did something happen between b03066f7ee and c6ba941339 that could be causing Blender to use integrated graphics instead of NVIDIA on windows laptops?
Author

Thanks Evan Wilson, manually setting the N-vidia GPU in N-vodia Control Panel for Blender helped. The open-gl performance is back again and my N-vidia GPU is used again for open-gl viewport rendering . What bugs me I never had to do this before the blender version: blender-2.82-b03066f7ee07-windows64 from 12.12.2019.

The key point in my report that was missing was that the open-gl engines weren't using the N-vidia GPU, so I edited my report to make that clear and I learned my lesson - to Sergey Scharby.

Thanks for your time and effort.

Thanks Evan Wilson, manually setting the N-vidia GPU in N-vodia Control Panel for Blender helped. The open-gl performance is back again and my N-vidia GPU is used again for open-gl viewport rendering . What bugs me I never had to do this before the blender version: blender-2.82-b03066f7ee07-windows64 from 12.12.2019. The key point in my report that was missing was that the open-gl engines weren't using the N-vidia GPU, so I edited my report to make that clear and I learned my lesson - to Sergey Scharby. Thanks for your time and effort.

Changed status from 'Needs User Info' to: 'Needs Triage'

Changed status from 'Needs User Info' to: 'Needs Triage'

Added subscriber: @mano-wii

Added subscriber: @mano-wii

Changed status from 'Needs Triage' to: 'Archived'

Changed status from 'Needs Triage' to: 'Archived'
Germano Cavalcante self-assigned this 2020-01-16 15:43:35 +01:00

The gpu chosen for OpenGL is a non-blender configuration.
This is configured in different ways depending on the GPU and operating system.
It is often set by the computer's power settings.

It would be interesting if we could pick the GPU from Blender preferences, but that's not a simple task given the compatibility of blender across multiple platforms.
Anyway, this is not a bug.

The gpu chosen for OpenGL is a non-blender configuration. This is configured in different ways depending on the GPU and operating system. It is often set by the computer's power settings. It would be interesting if we could pick the GPU from Blender preferences, but that's not a simple task given the compatibility of blender across multiple platforms. Anyway, this is not a bug.
Member

Changed status from 'Archived' to: 'Resolved'

Changed status from 'Archived' to: 'Resolved'
Member

Good news @mjunk! Your supplied working version in combination with another user's report allowed us to narrow down when this issue started occurring to a 48 hour period.

This issue has now been resolved by D6563

See https://developer.blender.org/T73296#857222 for more details if you are curious.

Good news @mjunk! Your supplied working version in combination with another user's report allowed us to narrow down when this issue started occurring to a 48 hour period. This issue has now been resolved by [D6563](https://archive.blender.org/developer/D6563) See https://developer.blender.org/T73296#857222 for more details if you are curious.
Author

In #72841#857694, @EAW wrote:
Good news @mjunk! Your supplied working version in combination with another user's report allowed us to narrow down when this issue started occurring to a 48 hour period.

This issue has now been resolved by D6563

See https://developer.blender.org/T73296#857222 for more details if you are curious.

Great, thanks.

> In #72841#857694, @EAW wrote: > Good news @mjunk! Your supplied working version in combination with another user's report allowed us to narrow down when this issue started occurring to a 48 hour period. > > This issue has now been resolved by [D6563](https://archive.blender.org/developer/D6563) > > See https://developer.blender.org/T73296#857222 for more details if you are curious. Great, thanks.
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
8 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#72841
No description provided.