Blender Running extremely slow on Intel IRIS and Windows #71287

Closed
opened 2019-11-02 12:18:27 +01:00 by Christoph Graf · 84 comments

System Information
Microsoft Surface Laptop 3 13.5"
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: Intel(R) Iris(R) Plus Graphics Intel 4.5.0 - Build 25.20.100.7101
CPU: Intel Core i7 1065G7
RAM: 16GB LPDDR4X @3733 mhz
Drivers are up to date, this is a fresh windows install without other programs apart from Chrome, Autohotkey, Slack and Whatsapp, which all have been turned off.

Blender Version
Broken: version: 2.82 (sub 1), branch: master, commit date: 2019-11-01 22:10, hash: e83a23acb2
Every other version of 2.8 I tried is also not working.
Worked: 2.79

Short description of error
Blender runs extremely slow, the viewport is laggy and has hang spikes every few frames, resizing the window is slow and every action takes half a second. I could only find references to this behavior happening on Macs (the behavior is similar to https://developer.blender.org/T56996). I'm pretty sure that this is tied to my hardware as I've tried the same build on another similarly powered device and didn't get the behavior there. I'm suspecting the Iris graphics, as that is a similarity with some of the macs that reportedly had this problem.
The Problem gets a little less worse when going into render view once, it stays that way when moving back, though still not usable. I'm not sure how to enable the --debug-gpu thing so I haven't tried that, the Debug Menu (23 if that's correct) shows this, but opening it doesn't have any noticeable effect: Capture.PNG

Exact steps for others to reproduce the error
I'm pretty sure this is not reproducible without the same hardware, As this happens directly on opening a fresh download of blender, no changes to anything with the default scene.

Video of the Problem:
Blender 2019-11-02 12-07-26.mp4

**System Information** Microsoft Surface Laptop 3 13.5" Operating system: Windows-10-10.0.18362 64 Bits Graphics card: Intel(R) Iris(R) Plus Graphics Intel 4.5.0 - Build 25.20.100.7101 CPU: Intel Core i7 1065G7 RAM: 16GB LPDDR4X @3733 mhz Drivers are up to date, this is a fresh windows install without other programs apart from Chrome, Autohotkey, Slack and Whatsapp, which all have been turned off. **Blender Version** Broken: version: 2.82 (sub 1), branch: master, commit date: 2019-11-01 22:10, hash: `e83a23acb2` Every other version of 2.8 I tried is also not working. Worked: 2.79 **Short description of error** Blender runs extremely slow, the viewport is laggy and has hang spikes every few frames, resizing the window is slow and every action takes half a second. I could only find references to this behavior happening on Macs (the behavior is similar to https://developer.blender.org/T56996). I'm pretty sure that this is tied to my hardware as I've tried the same build on another similarly powered device and didn't get the behavior there. I'm suspecting the Iris graphics, as that is a similarity with some of the macs that reportedly had this problem. The Problem gets a little less worse when going into render view once, it stays that way when moving back, though still not usable. I'm not sure how to enable the --debug-gpu thing so I haven't tried that, the Debug Menu (23 if that's correct) shows this, but opening it doesn't have any noticeable effect: ![Capture.PNG](https://archive.blender.org/developer/F7901358/Capture.PNG) **Exact steps for others to reproduce the error** I'm pretty sure this is not reproducible without the same hardware, As this happens directly on opening a fresh download of blender, no changes to anything with the default scene. Video of the Problem: [Blender 2019-11-02 12-07-26.mp4](https://archive.blender.org/developer/F7901299/Blender_2019-11-02_12-07-26.mp4)
Author

Added subscriber: @Ordenritterlein

Added subscriber: @Ordenritterlein

#73112 was marked as duplicate of this issue

#73112 was marked as duplicate of this issue
Author

I'm not sure how to get this seen, but this makes 2.8 literally unusable and it is definitely a problem with Blender and the hardware, not my specific pc setup, since it appears on a clean windows install. I presume the problem is with all 10th gen intel chips. and a few older ones. (specifically the Iris graphics line) .

I'm not sure how to get this seen, but this makes 2.8 literally unusable and it is definitely a problem with Blender and the hardware, not my specific pc setup, since it appears on a clean windows install. I presume the problem is with all 10th gen intel chips. and a few older ones. (specifically the Iris graphics line) .

Added subscriber: @BrendTheCow

Added subscriber: @BrendTheCow

I can confirm this issue on my Surface Pro 7 (also 10th Gen Intel with Iris Plus). I've tried both updating the graphics drivers to latest (had to force, as they weren't authorized for this device yet), and testing on every Blender version from 2.80 to 2.82. It makes the software completely unusable.

I can confirm this issue on my Surface Pro 7 (also 10th Gen Intel with Iris Plus). I've tried both updating the graphics drivers to latest (had to force, as they weren't authorized for this device yet), and testing on every Blender version from 2.80 to 2.82. It makes the software completely unusable.

It should be mentioned that this problem persists across both Eevee and Cycles viewport renderers, regardless of whether or not Cycles is set to CPU or GPU. I installed Maya 2019.2 to see if it also had issues with the 3D viewport stutter (which would indicate inherent driver issues instead of Blender issues), but Maya renders 3D objects in the viewport without any stutter.

It should be mentioned that this problem persists across both Eevee and Cycles viewport renderers, regardless of whether or not Cycles is set to CPU or GPU. I installed Maya 2019.2 to see if it also had issues with the 3D viewport stutter (which would indicate inherent driver issues instead of Blender issues), but Maya renders 3D objects in the viewport without any stutter.

Added subscriber: @rboxman

Added subscriber: @rboxman

Yes, lack of hardware will make this difficult to address. In the meantime please try the following:

  1. Install Intel drivers directly: https://downloadcenter.intel.com/product/197599/Graphics-for-10th-Generation-Intel-Processors
  The latest version is 26.xx.xxxx.xxxx (The 25.xx series pre-dates 10th gen really)
  Can those here confirm the problem still happens with the 26.xx series of driver.
  1. If that does not work please try launching blender with the provided blender_debug_gpu_glitchworkaround.cmd file (just double-click it) that should be right next to your blender.exe. When finished, drag and drop the 2 log files here (the location of the files will be opened in Explorer for you when closing blender)

This isn't a support system but reporting back after doing those 2 items will help the devs investigate eventually.

Yes, lack of hardware will make this difficult to address. In the meantime please try the following: 1. Install Intel drivers directly: https://downloadcenter.intel.com/product/197599/Graphics-for-10th-Generation-Intel-Processors ``` The latest version is 26.xx.xxxx.xxxx (The 25.xx series pre-dates 10th gen really) ``` ``` Can those here confirm the problem still happens with the 26.xx series of driver. ``` 2. If that does not work please try launching blender with the provided `blender_debug_gpu_glitchworkaround.cmd` file (just double-click it) that should be right next to your blender.exe. When finished, drag and drop the 2 log files here (the location of the files will be opened in Explorer for you when closing blender) This isn't a support system but reporting back after doing those 2 items will help the devs investigate eventually.

Hi Roger,

Thanks for the help! To answer your questions:

  1. Can confirm. I'm running 26.20.100.7372 currently, and previously ran 26.20.100.7xx1 (earlier version, but can't remember specific build number) - same issue on both.

  2. Done and done: blender_system_info.txt blender_debug_output.txt

While this isn't a support system, I do hope the devs take a look at this soon. Fingers crossed!

Hi Roger, Thanks for the help! To answer your questions: 1. Can confirm. I'm running 26.20.100.7372 currently, and previously ran 26.20.100.7xx1 (earlier version, but can't remember specific build number) - same issue on both. 2. Done and done: [blender_system_info.txt](https://archive.blender.org/developer/F8064382/blender_system_info.txt) [blender_debug_output.txt](https://archive.blender.org/developer/F8064381/blender_debug_output.txt) While this isn't a support system, I do hope the devs take a look at this soon. Fingers crossed!

One more thing for completeness. It looks like you're using 2.80. Can you try 2.81 (or 2.82) available for download here (just unzip locally and run): https://builder.blender.org/download/

Same procedure. Try with and without the debug script and upload logs if necessary.

One more thing for completeness. It looks like you're using 2.80. Can you try 2.81 (or 2.82) available for download here (just unzip locally and run): https://builder.blender.org/download/ Same procedure. Try with and without the debug script and upload logs if necessary.
Author

Hey Roger,

Thanks for taking the time, it's getting really frustrating having to use 2.79 again^^

blender_debug_output.txt

blender_system_info.txt

Latest Blender 2.82, latest intel driver (26.20.100.7372)
The issues appear to have not changed in any way.

Hey Roger, Thanks for taking the time, it's getting really frustrating having to use 2.79 again^^ [blender_debug_output.txt](https://archive.blender.org/developer/F8065511/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F8065512/blender_system_info.txt) Latest Blender 2.82, latest intel driver (26.20.100.7372) The issues appear to have not changed in any way.

Added subscriber: @brianf

Added subscriber: @brianf

I'm encountering the same issue on a Surface Pro 7 with Iris Plus G7 graphics as well. Digging around I see https://developer.blender.org/T70922 which looks to be the same issue. I have the latest master branch 2.82 built locally with debug symbols and Intel driver 26.20.100.7372.
blender_debug_output.txt

blender_system_info.txt

I'm encountering the same issue on a Surface Pro 7 with Iris Plus G7 graphics as well. Digging around I see https://developer.blender.org/T70922 which looks to be the same issue. I have the latest master branch 2.82 built locally with debug symbols and Intel driver 26.20.100.7372. [blender_debug_output.txt](https://archive.blender.org/developer/F8078475/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F8078476/blender_system_info.txt)

Added subscriber: @Viiince

Added subscriber: @Viiince

I have an identical issue on the Dell XPS 13 7390 2 in 1 (Intel i7-1065G7 with Intel IRIS)

Graphics drivers: 25.20.100.7102

I have an identical issue on the Dell XPS 13 7390 2 in 1 (Intel i7-1065G7 with Intel IRIS) Graphics drivers: 25.20.100.7102
Author

Hey Vincent, can you upload the logs as well? I haven't been able to see a similarity between them and logs from a working machine, but the more info we get the better.

Hey Vincent, can you upload the logs as well? I haven't been able to see a similarity between them and logs from a working machine, but the more info we get the better.

I took some performance traces and saw that most of the render time was being spent in workbench_solid_draw_background, 60% of a 1 second sample, on the 10th gen Iris Plus graphics.
While on Intel HD 630 graphics, workbench_solid_draw_background was only taking up 10% of the 1 second sample.

I took some performance traces and saw that most of the render time was being spent in workbench_solid_draw_background, 60% of a 1 second sample, on the 10th gen Iris Plus graphics. While on Intel HD 630 graphics, workbench_solid_draw_background was only taking up 10% of the 1 second sample.

Added subscriber: @VincentMaurer

Added subscriber: @VincentMaurer

Hey Christoph,

Here are the logs you requested

blender_system_info.txt

blender_debug_output.txt

Hey Christoph, Here are the logs you requested [blender_system_info.txt](https://archive.blender.org/developer/F8148516/blender_system_info.txt) [blender_debug_output.txt](https://archive.blender.org/developer/F8148517/blender_debug_output.txt)

Added subscriber: @katmanthree

Added subscriber: @katmanthree

Hi Christoph,

I've attached my logs as well, for a Dell Inspirion 3000 series laptop with an Intel i5-1035G4 running Intel's graphics driver version 26.20.100.7463. Might make sense to merge this with https:*developer.blender.org/T70922 and https:*developer.blender.org/T71555 as it seems this issue applies for all Iris Plus Graphics cards.blender_system_info.txt

blender_debug_output.txt

Hi Christoph, I've attached my logs as well, for a Dell Inspirion 3000 series laptop with an Intel i5-1035G4 running Intel's graphics driver version 26.20.100.7463. Might make sense to merge this with https:*developer.blender.org/T70922 and https:*developer.blender.org/T71555 as it seems this issue applies for all Iris Plus Graphics cards.[blender_system_info.txt](https://archive.blender.org/developer/F8150396/blender_system_info.txt) [blender_debug_output.txt](https://archive.blender.org/developer/F8150397/blender_debug_output.txt)

Added subscriber: @c19130064

Added subscriber: @c19130064

2.81 and 2.82 both share the same issus. I have to use 2.79 for now. Please give some advice?

2.81 and 2.82 both share the same issus. I have to use 2.79 for now. Please give some advice?

Added subscriber: @patrickmros

Added subscriber: @patrickmros

Added subscriber: @JosefNobach

Added subscriber: @JosefNobach

I have the same issue with my Surface Pro 7 i7. I have an entire thread here about this issue.

BLender artist Laggy viewport

I have the same issue with my Surface Pro 7 i7. I have an entire thread here about this issue. [BLender artist Laggy viewport ](https://blenderartists.org/t/blender-not-working-well-on-surface-pro-7/1187133/19)
Germano Cavalcante changed title from Blender Running extremely slow on Surface Laptop 3 to Blender Running extremely slow on Intel IRIS and Windows 2019-12-05 16:21:11 +01:00

Added subscriber: @mano-wii

Added subscriber: @mano-wii

Since many are reporting the same issue, I set the report as a high priority, but we still need a developer who can reproduce the problem :\

Since many are reporting the same issue, I set the report as a high priority, but we still need a developer who can reproduce the problem :\

Added subscriber: @michealparks

Added subscriber: @michealparks

Added subscriber: @Teralink

Added subscriber: @Teralink

I have the same issue with my Surface Pro 7 with Intel i7-1065G7 CPU, 16 GB Ram, Windows 10 and Intel Iris Plus Graphics.

blender_system_info.txt

blender_debug_output.txt

I have the same issue with my Surface Pro 7 with Intel i7-1065G7 CPU, 16 GB Ram, Windows 10 and Intel Iris Plus Graphics. [blender_system_info.txt](https://archive.blender.org/developer/F8214136/blender_system_info.txt) [blender_debug_output.txt](https://archive.blender.org/developer/F8214135/blender_debug_output.txt)

Added subscriber: @pancake-manicure

Added subscriber: @pancake-manicure

Added subscriber: @floetenmaul

Added subscriber: @floetenmaul

Added subscriber: @b.c.m.janssen

Added subscriber: @b.c.m.janssen

I'm having the same issue on my Surface Pro 7 i5-1035G4 as well.

I'm having the same issue on my Surface Pro 7 i5-1035G4 as well.

Added subscriber: @kettunenf.lassi

Added subscriber: @kettunenf.lassi

Added subscriber: @gryphus

Added subscriber: @gryphus

The issue still exists in Blender 2.83 alpha.

The issue still exists in Blender 2.83 alpha.
Member

Added subscriber: @Jeroen-Bakker

Added subscriber: @Jeroen-Bakker
Member

Looking at the video it seems like a GPU/Driver issue. As cycles viewport is reacting more smoother than the workbench I can imagine that the driver is having trouble loading/unloading data.
Can someone do the same test, but with the debug value set to 22. (f3 -> Debug menu -> 22 -> ok) and record it with via an external source (mobile phone) So we can compare in which area the GPU does not excel.

As the architecture is new, and we don't have that architecture it is hard for us to fix the issue. I would expect that the driver isn't optimized for our load, but we might need to help out the driver a bit. I will set the issue to known issue for now until a gpu dev has their hands on a similar device.

Looking at the video it seems like a GPU/Driver issue. As cycles viewport is reacting more smoother than the workbench I can imagine that the driver is having trouble loading/unloading data. Can someone do the same test, but with the debug value set to 22. (f3 -> Debug menu -> 22 -> ok) and record it with via an external source (mobile phone) So we can compare in which area the GPU does not excel. As the architecture is new, and we don't have that architecture it is hard for us to fix the issue. I would expect that the driver isn't optimized for our load, but we might need to help out the driver a bit. I will set the issue to known issue for now until a gpu dev has their hands on a similar device.
Member

Added subscriber: @FionNoir

Added subscriber: @FionNoir

Hi @Jeroen-Bakker,
When you say the same test do you mean perform the same actions as in the video attached to the opening post of this thread?

Hi @Jeroen-Bakker, When you say the same test do you mean perform the same actions as in the video attached to the opening post of this thread?
Author

same pc, 2.83 alpha, Date 2020-01-10 17:32, hash 01d9a2f71b

I've done the test with the debug menu before, as some people with the problem on mac suggested it goes away when you enable it, but I only attached a static image before.

order of operations: Load, set debug to 22, duplicate, set to rendered in eevee (which improves viewport performance slightly for camera turning and such, but not for moving objects), switch to cycles.
as you can se the difference is hugely noticeable, even through the crap smartphone recording. I hope that helps. Blender Recording.mp4

same pc, 2.83 alpha, Date 2020-01-10 17:32, hash 01d9a2f71b56 I've done the test with the debug menu before, as some people with the problem on mac suggested it goes away when you enable it, but I only attached a static image before. order of operations: Load, set debug to 22, duplicate, set to rendered in eevee (which improves viewport performance slightly for camera turning and such, but not for moving objects), switch to cycles. as you can se the difference is hugely noticeable, even through the crap smartphone recording. I hope that helps. [Blender Recording.mp4](https://archive.blender.org/developer/F8279471/Blender_Recording.mp4)

Added subscriber: @aguy73

Added subscriber: @aguy73

I just wanted to add that my new Surface Laptop 3 "15 intel with a 1065g7 based cpu doesn't work correctly with any 2.8x. I have tried 2.81a, and dev 2.82 and 2.83. I'm getting the similar problem of low viewport framerate, making Blender essentially unusable.

I just wanted to add that my new Surface Laptop 3 "15 intel with a 1065g7 based cpu doesn't work correctly with any 2.8x. I have tried 2.81a, and dev 2.82 and 2.83. I'm getting the similar problem of low viewport framerate, making Blender essentially unusable.

Added subscriber: @blu3bird

Added subscriber: @blu3bird

Added subscriber: @KlausJJ

Added subscriber: @KlausJJ

Same issue on Lenovo Yoga C940.
system-info.txt

Same issue on Lenovo Yoga C940. [system-info.txt](https://archive.blender.org/developer/F8328626/system-info.txt)

Added subscriber: @Philongo

Added subscriber: @Philongo

Hello, I just wanted to say that I have been using Blender 2.8A with my surface pro 7, i7 model for the past week with no issues with the exception of the first 6 to 10 minutes which happen to be laggy but once it clears I have no issue what so ever with it. I agree there is a problem but I'm glad I can use it with my surface.

Hello, I just wanted to say that I have been using Blender 2.8A with my surface pro 7, i7 model for the past week with no issues with the exception of the first 6 to 10 minutes which happen to be laggy but once it clears I have no issue what so ever with it. I agree there is a problem but I'm glad I can use it with my surface.

In #71287#870752, @Philongo wrote:
Hello, I just wanted to say that I have been using Blender 2.8A with my surface pro 7, i7 model for the past week with no issues with the exception of the first 6 to 10 minutes which happen to be laggy but once it clears I have no issue what so ever with it. I agree there is a problem but I'm glad I can use it with my surface.

I can not confirm this on a Surface Laptop 3 with similar i7 CPU (1065G7). Even after half an hour it is still laggy. Have you changed any settings?

> In #71287#870752, @Philongo wrote: > Hello, I just wanted to say that I have been using Blender 2.8A with my surface pro 7, i7 model for the past week with no issues with the exception of the first 6 to 10 minutes which happen to be laggy but once it clears I have no issue what so ever with it. I agree there is a problem but I'm glad I can use it with my surface. I can not confirm this on a Surface Laptop 3 with similar i7 CPU (1065G7). Even after half an hour it is still laggy. Have you changed any settings?

So I did not change any of my setting, but I did do some testing to see what would what be the quickest way I could get my laggy/choppy performance to act normal and I found out that if I open: File/New/Sculpting and start doodling my performance will fix itself within 2 to 3 mins but if I start with the normal general modelling my computer with take between 10 -20 mins to fix itself and If I just open blender in a let the computer sit idle with the application open it does nothing, I thought maybe the files took longer to load and thats the reason why it took so long to fix itself but that's clearly not the issues. If I could provide anything please let me know.

So I did not change any of my setting, but I did do some testing to see what would what be the quickest way I could get my laggy/choppy performance to act normal and I found out that if I open: File/New/Sculpting and start doodling my performance will fix itself within 2 to 3 mins but if I start with the normal general modelling my computer with take between 10 -20 mins to fix itself and If I just open blender in a let the computer sit idle with the application open it does nothing, I thought maybe the files took longer to load and thats the reason why it took so long to fix itself but that's clearly not the issues. If I could provide anything please let me know.
Author

I can confirm, at least from my side that viewport performance kind of returns to normal after noodling around a few minutes in sculpt mode (as described, new File -> sculpting).
the change happened rather abruptly after randomly applying strokes. Menus still operate laggy though, adding a separate material for example still hangs for seconds at a time.
I have not tested if much, if it's specific to a view (pane, windows subdivision, never knew what those were called) for example.

I can confirm, at least from my side that viewport performance kind of returns to normal after noodling around a few minutes in sculpt mode (as described, new File -> sculpting). the change happened rather abruptly after randomly applying strokes. Menus still operate laggy though, adding a separate material for example still hangs for seconds at a time. I have not tested if much, if it's specific to a view (pane, windows subdivision, never knew what those were called) for example.

Added subscriber: @Stavv

Added subscriber: @Stavv

Also confirming. Smooth as butter (including menus) after messing around in sculpt mode for a few minutes.

Blender Version: 2.83 (sub 4)

Specs:
XPS 13 7390 2-in-1
Windows 10, 10.0.18362 Build 18362
Intel(R) Core(TM) i7-1065G7
32 GB RAM
Intel Graphics driver version 26.20.100.7463

Haven't tested with production Blender 2.82 but it seems like the lag got worse in 2.82 compared to 2.81.

Also confirming. Smooth as butter (including menus) after messing around in sculpt mode for a few minutes. Blender Version: 2.83 (sub 4) Specs: XPS 13 7390 2-in-1 Windows 10, 10.0.18362 Build 18362 Intel(R) Core(TM) i7-1065G7 32 GB RAM Intel Graphics driver version 26.20.100.7463 Haven't tested with production Blender 2.82 but it seems like the lag got worse in 2.82 compared to 2.81.

Added subscriber: @hamC

Added subscriber: @hamC

Also confirming. Sculpt mode fixes the viewport somehow after a couple of minutes. But its' not a solution.

Specs: Surface Laptop 3 with i7-1065G7

Also confirming. Sculpt mode fixes the viewport somehow after a couple of minutes. But its' not a solution. Specs: Surface Laptop 3 with i7-1065G7

Can Confirm on a Surface Pro 7 - i7 model. The sculpt mode trick kind of works but going back to the normal object view brings the lag back, making it unusable. Gotta use 2.79 for now which luckily works perfectly :(

Can Confirm on a Surface Pro 7 - i7 model. The sculpt mode trick kind of works but going back to the normal object view brings the lag back, making it unusable. Gotta use 2.79 for now which luckily works perfectly :(

Added subscriber: @gokarter64

Added subscriber: @gokarter64

also can confirm with a surface pro 7 i7, it handles blender 2.79 perfectly however 2.8 is still not running properly the sculpt mode trick works but if i sit idle for too long it will slow right back down. actions are still delayed regardless of what i do

also can confirm with a surface pro 7 i7, it handles blender 2.79 perfectly however 2.8 is still not running properly the sculpt mode trick works but if i sit idle for too long it will slow right back down. actions are still delayed regardless of what i do

Added subscriber: @ahmess

Added subscriber: @ahmess

can confirm poor performance on my i5 surface pro 7. i've tried using version 2.8, 2.82, and 2.83 alpha but none shows any significant performance difference. sculpt mode doesn't seem to help at all in my case.

specs:
Surface Pro 7 - i5-1035G4
8GB RAM
Intel Graphics Driver version 26.20.100.7641

can confirm poor performance on my i5 surface pro 7. i've tried using version 2.8, 2.82, and 2.83 alpha but none shows any significant performance difference. sculpt mode doesn't seem to help at all in my case. specs: Surface Pro 7 - i5-1035G4 8GB RAM Intel Graphics Driver version 26.20.100.7641

Added subscriber: @teejay5

Added subscriber: @teejay5

Confirming poor performance on Surface Laptop 3 i7 16gb and Surface Pro 7 i7 16gb. Changing the render mode to Cycles, then turn viewport shading to "Rendered" makes it smoother, but switching to any other viewport shading mode brings the issue back.

Confirming poor performance on Surface Laptop 3 i7 16gb and Surface Pro 7 i7 16gb. Changing the render mode to Cycles, then turn viewport shading to "Rendered" makes it smoother, but switching to any other viewport shading mode brings the issue back.

Added subscriber: @SpencerTerry

Added subscriber: @SpencerTerry

Has there been an update in the development of this issue recently? Using brand new Surface Pro 7 i7 and experiencing the exact same issues.

Has there been an update in the development of this issue recently? Using brand new Surface Pro 7 i7 and experiencing the exact same issues.
Member

@SpencerTerry We did some indept performance checks and the viewport isn't lacking it is the rendering of the properties panel. We send this issue to Intel to come with direction.

By default the object panel is open. And gets updated when moving the active object in the 3d viewport. The 3d viewport is fast. The bottleneck is in the property panel and font drawing. This part of blender uses a wrapper to convert legacy OpenGL calls to core profile calls. It seems that the Intel driver is not performing well when creating many of these calls. You can test that yourself when you switch to the render tab in the property panel. This makes the UI more interactive.

If we want migrate the legacy OpenGL calls to core profile calls I would estimation 3 months full time work for a single developer (1 year lead time). Which might be redone when moving to vulkan. The most cost effective and quickest solution is that Intel would solve this issue in their driver. They are aware of this request and we are waiting for their response.

@SpencerTerry We did some indept performance checks and the viewport isn't lacking it is the rendering of the properties panel. We send this issue to Intel to come with direction. By default the object panel is open. And gets updated when moving the active object in the 3d viewport. The 3d viewport is fast. The bottleneck is in the property panel and font drawing. This part of blender uses a wrapper to convert legacy OpenGL calls to core profile calls. It seems that the Intel driver is not performing well when creating many of these calls. You can test that yourself when you switch to the render tab in the property panel. This makes the UI more interactive. If we want migrate the legacy OpenGL calls to core profile calls I would estimation 3 months full time work for a single developer (1 year lead time). Which might be redone when moving to vulkan. The most cost effective and quickest solution is that Intel would solve this issue in their driver. They are aware of this request and we are waiting for their response.

Added subscriber: @ghostmafaldo

Added subscriber: @ghostmafaldo

Apparently the problem is in turbo boost of the intel microprocessor, this controls the speed of the microprocessor, I understand that when the tablet is connected to the outlet, the microprocessor works at full power, otherwise it works at half speed .
This option also detects when a program requires more computing power and activates turbo mode.

Apparently the problem is in turbo boost of the intel microprocessor, this controls the speed of the microprocessor, I understand that when the tablet is connected to the outlet, the microprocessor works at full power, otherwise it works at half speed . This option also detects when a program requires more computing power and activates turbo mode.

Is that confirmed? The problem is the same for me when the device (Surface Laptop 3) is plugged in, but Turbo Boost issues would maybe explain why the viewport performs better when it's in Cycles render mode, right? Or is there another explanation?

Is that confirmed? The problem is the same for me when the device (Surface Laptop 3) is plugged in, but Turbo Boost issues would maybe explain why the viewport performs better when it's in Cycles render mode, right? Or is there another explanation?

I highly doubt it has to do with the turbo clock. If that were the case we would see a difference in performance between battery and plugged in. It acts the same way regardless. I really think its an issue with the newest version of open gl for windows when running on 10th gen intel devices.

By the way i installed ubuntu in dual boot on my surface pro 7 i7 this week and blender 2.8 runs perfectly smooth on linux.

I highly doubt it has to do with the turbo clock. If that were the case we would see a difference in performance between battery and plugged in. It acts the same way regardless. I really think its an issue with the newest version of open gl for windows when running on 10th gen intel devices. By the way i installed ubuntu in dual boot on my surface pro 7 i7 this week and blender 2.8 runs perfectly smooth on linux.

In #71287#904037, @gokarter64 wrote:
I highly doubt it has to do with the turbo clock. If that were the case we would see a difference in performance between battery and plugged in. It acts the same way regardless. I really think its an issue with the newest version of open gl for windows when running on 10th gen intel devices.

By the way i installed ubuntu in dual boot on my surface pro 7 i7 this week and blender 2.8 runs perfectly smooth on linux.

@gokarter64
I just got the Surface 7 as well, would you be able to give me some tips on how you installed Ubuntu on your laptop? Thanks.

> In #71287#904037, @gokarter64 wrote: > I highly doubt it has to do with the turbo clock. If that were the case we would see a difference in performance between battery and plugged in. It acts the same way regardless. I really think its an issue with the newest version of open gl for windows when running on 10th gen intel devices. > > By the way i installed ubuntu in dual boot on my surface pro 7 i7 this week and blender 2.8 runs perfectly smooth on linux. @gokarter64 I just got the Surface 7 as well, would you be able to give me some tips on how you installed Ubuntu on your laptop? Thanks.

In #71287#907978, @SpencerTerry wrote:

In #71287#904037, @gokarter64 wrote:
I highly doubt it has to do with the turbo clock. If that were the case we would see a difference in performance between battery and plugged in. It acts the same way regardless. I really think its an issue with the newest version of open gl for windows when running on 10th gen intel devices.

By the way i installed ubuntu in dual boot on my surface pro 7 i7 this week and blender 2.8 runs perfectly smooth on linux.

@gokarter64
I just got the Surface 7 as well, would you be able to give me some tips on how you installed Ubuntu on your laptop? Thanks.

Here is a link to the project. You can use any linux version i personally just have experience with ubuntu https://github.com/linux-surface/linux-surface/wiki/Installation-and-Setup/_history

> In #71287#907978, @SpencerTerry wrote: >> In #71287#904037, @gokarter64 wrote: >> I highly doubt it has to do with the turbo clock. If that were the case we would see a difference in performance between battery and plugged in. It acts the same way regardless. I really think its an issue with the newest version of open gl for windows when running on 10th gen intel devices. >> >> By the way i installed ubuntu in dual boot on my surface pro 7 i7 this week and blender 2.8 runs perfectly smooth on linux. > > @gokarter64 > I just got the Surface 7 as well, would you be able to give me some tips on how you installed Ubuntu on your laptop? Thanks. Here is a link to the project. You can use any linux version i personally just have experience with ubuntu https://github.com/linux-surface/linux-surface/wiki/Installation-and-Setup/_history

@gokarter64
Thank you!

@gokarter64 Thank you!

Added subscriber: @baswein

Added subscriber: @baswein

I haven't tried it but does this fix the issue?
https://developer.blender.org/D7357

I haven't tried it but does this fix the issue? https://developer.blender.org/D7357

Temporary Solution:

On Blender Artists it was discovered that an experimental April 10th build of 2.83a had resolved most of the issue. I haven't played around with it too much but its pretty smooth from the get-go. The most recent builds bring the issue back, but that was because someone reported crashing and they're still working out the kinks. Full release is scheduled for May 20th, I believe, but this is a great sign that things will be fine for Iris Plus users.

Ive attached the April 10th build below for those who are needing 2.8x asap--but it is experimental!

blender-2.83-a8d139ca2002-windows64.zip

Temporary Solution: On Blender Artists it was discovered that an experimental April 10th build of 2.83a had resolved most of the issue. I haven't played around with it too much but its pretty smooth from the get-go. The most recent builds bring the issue back, but that was because someone reported crashing and they're still working out the kinks. Full release is scheduled for May 20th, I believe, but this is a great sign that things will be fine for Iris Plus users. Ive attached the April 10th build below for those who are needing 2.8x asap--but it is experimental! [blender-2.83-a8d139ca2002-windows64.zip](https://archive.blender.org/developer/F8467384/blender-2.83-a8d139ca2002-windows64.zip)

Added subscriber: @Doomer1122

Added subscriber: @Doomer1122

Blender 2.90 Alpha has come out. I love to do work on my Surface Pro 7 as its very light weight, the surface pen, resolution, etc. Its a wonderful portable workstation for me. While its not the most powerful unit, it does exactly what I need from it. That being said, I created an account here (Been shadowing this post) to report that 2.90 Alpha has come out and upon first launch of it, the stuttering and performance issue is nearly gone immediately. There is a noticeable FPS drop in the view port than what I am use to from my main PC, and from the work around listed above (Sculpting in 2.83a), however menus work flawlessly. The FPS drop is the only performance issue left that I can feel. Hopefully, depending on the person, the performance may not be bad. For me, I do not mind it. Hopefully this will improve over time. Gives me high hopes.

Blender 2.90 Alpha has come out. I love to do work on my Surface Pro 7 as its very light weight, the surface pen, resolution, etc. Its a wonderful portable workstation for me. While its not the most powerful unit, it does exactly what I need from it. That being said, I created an account here (Been shadowing this post) to report that 2.90 Alpha has come out and upon first launch of it, the stuttering and performance issue is nearly gone immediately. There is a noticeable FPS drop in the view port than what I am use to from my main PC, and from the work around listed above (Sculpting in 2.83a), however menus work flawlessly. The FPS drop is the only performance issue left that I can feel. Hopefully, depending on the person, the performance may not be bad. For me, I do not mind it. Hopefully this will improve over time. Gives me high hopes.

Added subscriber: @brecht

Added subscriber: @brecht

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Brecht Van Lommel self-assigned this 2020-04-20 15:03:50 +02:00

The main fix for this is in both 2.83 and 2.90.

I'm closing this as a duplicate of #70922 (Intel IRS / Ice lake GPU slow viewport performance) which is still open to improve performance further, since that's where most of the information is.

The main fix for this is in both 2.83 and 2.90. I'm closing this as a duplicate of #70922 (Intel IRS / Ice lake GPU slow viewport performance) which is still open to improve performance further, since that's where most of the information is.

Added subscriber: @welcometohe1l

Added subscriber: @welcometohe1l

Hello everyone! I ran into the problem of a slow interface and I FIX IT.

My characteristics:

  • Laptop Dell Inspiron 15570
  • GPU: Nvidia Geforce 1050 and Intel HD Graphics 630
  • CPU: Intel i5-7300HQ
  • Blender: 2.82a

Two graphics cards are installed in the laptop: NVIDIA Geforce 1050 and Intel HD Graphics 630. It turned out that the video card from Intel is not detected in the system. After turning it off in the device manager, the blender began to work quickly. However, after rebooting the blender, it again worked slowly. For it to work well, you had to enable and disable the video card from Intel. Later, I decided to update the drivers for the Intel graphics card from the official website and it began to display correctly in the system. The blender began to work quickly without complaints.

Hello everyone! I ran into the problem of a slow interface and I FIX IT. My characteristics: - Laptop Dell Inspiron 15570 - GPU: Nvidia Geforce 1050 and Intel HD Graphics 630 - CPU: Intel i5-7300HQ - Blender: 2.82a Two graphics cards are installed in the laptop: NVIDIA Geforce 1050 and Intel HD Graphics 630. It turned out that the video card from Intel is not detected in the system. After turning it off in the device manager, the blender began to work quickly. However, after rebooting the blender, it again worked slowly. For it to work well, you had to enable and disable the video card from Intel. Later, I decided to update the drivers for the Intel graphics card from the official website and it began to display correctly in the system. The blender began to work quickly without complaints.
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
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
36 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#71287
No description provided.