Intel IRS / Ice lake GPU slow viewport performance #70922
Labels
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
39 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#70922
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
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.7011
Blender Version
Broken: version: 2.81 (sub 15), branch: master, commit date: 2019-10-17 15:40, hash:
382e7ce9ecWorked: (optional)
Short description of error
Viewport perfomance is 5-10fps with just a cube in scene. Runs smooth in 2.79 but extremely sluggish in 2.8-2.81
Exact steps for others to reproduce the error
Start default Blender 2.8 or 2.81 startup file. Navigate or move cube.
blender
--debug-gpu-force-workaroundsdoes not help.blender 2.81 slow.mkv
/Nikolaj
Added subscriber: @nikand
Added subscriber: @mano-wii
Have you tested with the latest graphics drivers on the intel website?
https://downloadcenter.intel.com/product/80939/Graphics-Drivers
I'm using the latest xxx.7323 driver from october. Stock driver from Lenovo gave same results.
Blender 2.79 runs smooth as does Houdini. But 2.8-81 is extremely slow. Moving a cube trails after the mouse.
Let me know if there is anything I can do.
Hello here's a screencapture of Blender 2.81 performance.
Unfortunately I'm not able to use Blender 2.8 on my new laptop.
Laptop model is Lenvo Yoga C940 14" 16gb ram, I7-1065-G7 cpu, fhd model, windows 10 64bit.blender 2.81 slow.mkv
Added subscriber: @DrDirk
Same thing on my brand new Surface 7 Pro. Newest Intel Drivers 26.20.100.7463.
Intel® Core™ i7-1065G7 CPU
Blender 2.82Alpha has the same problem. 2.79 is smooth.
Moving the whole window is laggy, too.
Added subscriber: @c19130064
Same icelake blender 2.8 lag on Surface Pro 7 i7 ice lake Cpu.
Blender 2.8, 2.8.1, 2.8.2 all laggy
Added subscriber: @VincentMaurer
I've got the same Problems on Surface Laptop 3 i5 Icelake CPU.
From Blender 2.8 to 2.82.
Added subscriber: @fclem
This seems to be becoming a frequent problem.
A major refactor has been made in blender 2.81's Draw Manager, but as far as I know, this shouldn't affect Intel GPUs.
To fix this problem, we may need to have this setup available.
For anyone experiencing this problem, could you provide
system-info.txt? (generated inHelp -> Save System Info).There is a complete information about the Blender version and graphics cards.
@fclem, any idea what it might be?
2019-11-26 laggy system-info.txt
191126_vma_system-info.txt
Added subscriber: @katmanthree
system-info.txt
Added subscriber: @Bolos
15 FPS in viewport with 4/5 GP objects (especially one with 30 layers made of textured strokes that get 15 FPS too viewed alone).
system-info.txt
Added subscriber: @Viiince
Any solution please?
Added subscriber: @EngineArtist
Same deal for me. Surface Pro 7 with Ice Lake under the hood. Blender 2.80-2.82 all have extremely laggy viewports.
CPU: Intel(R) Core(TM) i7-1065G7
GPU: Intel(R) Iris(R) Plus Graphics
system-info.txt
Added subscriber: @michealparks
Added subscriber: @barhoom
Added subscriber: @Teralink
Added subscriber: @MaciejJutrzenka
any chance of any of you instal linux on this device.. and try blender? to see is this maybe W10 related issiue?
also does the problem goes away if u switch to cycles?
Interesting:
For those observations the "viewport shading" is always left untouched.
@Viiince yeah it is known issiue at least for me.. for some strange reason intel GPU's have problem with eevee speciallly window of material preview.
Added subscriber: @victorg
This comment was removed by @victorg
Added subscriber: @floetenmaul
Added subscriber: @alfredbaudisch
How long does it usually take to address such problem/bug? sorry if its off topic.
After modeling with the software for more than 10 min, it acted totally normal and was very smooth.
video below, even with Eevee render engine.
[name ](Blender_ [C__Users_Ibrahim_Documents_Blender_BasketBall.blend] 2020-01-05 13-22-19.mp4)
Added subscriber: @b.c.m.janssen
Solution here:Another observation, if you changed computer BIOS Setting (Computer performance mode) it will solve the problem:
how did i change: (i got Lenovo S740, so i am assuming all Lenovo can have same solution), now it run smooth right from the start.
turn on computer
open start menu and click restart (while holding down left shift on your keyboard)
Select:
Troubleshoot,Advance Options,UEFI Setting(Might also be called BIOS, depends on your machine)then change the configuration of Preference mode from Quite/ Intelligent to:
Performance:Thanks for the update Ibrahim. Hopefully there will be a real fix soon. Unfortunately this doesn't work for my Surface Pro as is has an extremely limited UEFI
Added subscriber: @strobelo
Wanted to chip in here that I am seeing the same issue on 13" Surface Laptop 3 i5-1035G7, with latest Intel drivers on updated windows with all versions of Blender available above 2.8 (smooth on 2.79).
HOWEVER, today I installed Ubuntu linux (18.04) on the same device using the Surface Linux Kernel and tested out Blender 2.81a. And lo - it's buttery smooth! Let me know if there is any helpful debugging information I can provide. Perhaps this suggests an issue in the OpenGL implementation on Windows?
Added subscriber: @Belanko
Removed subscriber: @Belanko
Added subscriber: @Belanko
Added subscriber: @tihkal-4
Seems I am suffering from the same or a very similar issue.
UI behaves fine initially, then gets laggy, seemingly only after a few minutes.
I have not noticed anything other than time be the cause.
I run Arch Linux, and compile Blender from git source.
Noticed the issue since 2.81 if I'm not mistaken. Though I also seem to remember early 2.81 being fine. Not certain.
If I can provide any useful info, pease ask. I'm not sure where to begin debugging this kind of issue - sorry.
system-info.txt
@tihkal-4 Since you build from git source you could try to git bisect to find the commit that introduced the regression.
Removed subscriber: @Bolos
@fclem thanks - I'll look into it.
Just ran quick test. Opened blender from scratch and left it open with default cube.
After some time, came back and the lag was there.
I generally run Blender with
optirun blenderto use nvidia gpu.Currently doing the same without optirun. As yet, no lag, so looking like a GPU driver issue perhaps.
Currently compiling 2.79 to check if that now has the issue (assuming GPU driver) - it never suffered before.
And will also do the bisect as you suggested to see if I can glean more info.
@fclem so - I guess there's not much point in doing the
git bisectprocedure.Re-compiled 2.79 which never gave me trouble, ran it with
optirun, left it alone and again, experienced the lag.Looks like this (at least for me) is an nvidia driver issue.
Where the hell do I start dealing with them?
Or is there another possibility I haven't considered?
Note, if not clear already, I'm using the closed source nvidia drivers, not mesa.
@tihkal-4, you shouldn't be testing with the dedicated card, but with the integrated one (as reported in other users' system-info.txt)
Problems with your
GeForce GTX 960M/PCIe/SSE2are most likely unrelated.This comment was removed by @b.c.m.janssen
@mano-wii sorry I didn't realise.
But if I don't use the dedicated card, I can't use CUDA with GPU, only CPU (I assume CPU in this case is using the integrated card?)
Having said that, it seems if I don't use
optirunI can still use the dedicated card (though I don't remember this behaviour in the past).It would appear then, that I only have the problem when using
optirunand as it now seems I don't have to, I guess I can stop making noise here.Thanks for the help and sorry for the trouble.
@b.c.m.janssen you should not have removed your comment - I think it was valid. In trying to find a similar issue rather than post a new one, I kind of hijacked this.
Apologies.
edit: I now also realise mano-wii was pointing also at my issue being unrelated to this one.
I'm gonna get some sleep and say a final sorry for posting this here.
Mods can feel free to remove my posts.
If my issue continues, I'll open a separate report.
Added subscriber: @KlausJJ
Same problem on Lenovo C940 with startup scene. Moving the cube is extremely sluggish. Looks like its using the CPU.
system-info.txt
Added subscriber: @numarul7
Hi all!
Please all try to turn off Anti-Aliasing in Preferences , "half solve" this solves this problem on my tablet Cube Mix Plus with Intel 610
Lag happens even on my Nvidia Geforce GTX 750 Ti.
Wonder why default settings are with AA at near full ?! Or maybe AA implementation has some bugs to iron out cause happens on two manufacturers on Win10
@numarul7 Old AA implementation was really buggy and not optimal. In 2.82 it has been rewritten and is way more lightweight.
Added subscriber: @brecht
Assuming that the issue found by @tihkal-4 is a different one, the reports here are from before the overlay refactor on December 2 and other following changes.
Can anyone confirm that the issue still happens in the latest 2.82 builds?
https://builder.blender.org/download/
Added subscriber: @aguy73
Hi,
Yes I can confirm, the choppy viewport performance on icelake (tested on i7-1065G7) CPU's still is an issue on 2.81a, and 2.82 that I downloaded 2 days ago. I tried todays 2.83 as well.
Added subscriber: @Stinaus
I tested it on my Surface Pro 7, and the issue remains in the latest 2.82 beta, and 2.83 alpha builds as of 14.02.20!
system-info.txt
Added subscriber: @kloop
Can confirm, Linux 18.04, GeForce 970, Blender 2.82, nvidia-driver 390.116.
Super sluggish viewport, pretty unusable at this point with both cycles and eevee. :(
system-info.txt
Edit:
I can't believe it, it runs buttersmooth... under root account!
Added subscriber: @alzea
Hi,
Is this issue still persist? I have a plan to buy SP7 in the near future...
I hope this issue is already fixed...
Yes, this issue still persists on my SP7, tested the latest alpha. It's a shame, as I would have hoped to do some light modeling on it. It's a fantastic machine otherwise. I hope this gets fixed soon!
edit: on this tread people found a workaround to make it stop lagging
https://developer.blender.org/T71287
Entering sculpt mode and wait some minutes, then it will work smoothly. This worked for my SP7 It's a bit unreliable though, I tried a second time and it hasn't worked yet
Hi Stig,
Really appreciate the update, thanks!
It's so sad this issue still persists even after these months... I guess I will just wait then.
Thank you!
Added subscriber: @hamC
Added subscriber: @Roj
Hi all, if nothing worked try this:
To solve lagging issue, simply go to blender folder and delete "opengl132.dll" file. And open your blender as usual. This worked for me very well.
Video tutorial: https://youtu.be/7M-t4H_LfO8
Hope this works.
There is no "opengl132.dll" file in my Blender. The tutorial you linked is for an older version, 2.79. Do you know an equivalent for 2.80+?
That opengl32.dll shouldn't have been there in the first place.
So it's not a fix.
Somehow it appeared there.
I'm using old type of laptop that doesn't even have such Nvidia graphic. And I use blender 2.81
I tried different ways to solve this issue and deleting that file was solution for me and I thought this solution could help some others.
Added subscriber: @Jeroen-Bakker
We received a laptop that allows us to replicate the issue. I will do some performance measurements to see what part of the drawing is causing this issue. Using the Debug value 22 the draw manager measures extreme performance issues in the
Backgroundpart.I detect that even when there isn't any 3d viewport it is extreme slow. So I expect that the draw manager isn't the issue and we need to dive much deeper.
When opening a single area and changed the area types at first it seemed that the property area was really slow. But later it recovered. Even when using the 3d viewport as a single area is working better. But it seems that inside the driver it is lacking.
Note: Not related to this issue: viewport is always redrawn when the transform operator is active. Which could be improved to only schedule a redraw when a value has changed.
I have been profiling and have identified 2 areas that are really slow.
Nonein theColor Managementtab. When done the Image editor and 3D Viewport performance is within acceptable bandwidth. We need to check where in OCIO this is an issue and if other applications have the similar issues.on mouse overcolor is slowly behind. Or looking at the performance difference when the Object property tab is active or not.The issues could also be related to the use of OpenGL intermediate mode wrapper. If it is the case that the driver doesn't like temporary VBO/IBO's it would be a huge undertaking to get this issue fixed.
Side note: On the provided machine I wasn't able to start Blender 2.79b at all.
My Device with this issue (Surface Pro 7, 10th gen Intel® Core™ i7-1065G7 + Intel Iris Plus Graphics (GT2 @ 1.1GHz)) Runs 2.79b perfectly so that seems really strange if your provided machine is having the same issue.
Added subscriber: @sntg_p
I'm having the same problem with my Lenovo S340 with an i7-1065G7. It also runs 2.79b perfectly.
Added subscriber: @teejay5
Just wanted to add that the issue persists on the Surface Laptop 3 i7-1065G7 @ 1.30GHz 16GB RAM. I asked my friend and he says the same happens on his Surface Pro 7 with the same configuration.
What's even stranger is, if I set the render mode to Cycles and switch my viewport shading to "Rendered", it runs smoother than in any other view mode, even though it is literally rendering.
I really hope we can find at least a temporary workaround for this, I pretty much got this computer for Blender.
Added subscriber: @StanislavOvcharov
Added subscriber: @YoranMarchione
Exactly the same issues for me on my Surface Pro 7 i7 - 1065G7 16GB RAM / Windows 10 Pro 1909 and up-to-date. I'm using Blender 2.82a.
Same performance issues and also works well when switching to Cycles and rendered viewport. Any other mode is unusable.
DESKTOP-P02E5NG.04-06-2020.11-19-41.etl
After each run other stuff become the bottleneck. During this try I see 2 parts that are causing the slowness
the drawing of the drag handles can be improved on our side by implementing it as a glsl shader.
the color management is still unclear where this bottleneck lies. as it is just drawing a single triangle with a fragment shader. It could be that the fragment shader from OCIO is not optimized for this platform.
I will start with the drag handles and measure after this what we could improve.
This issue was referenced by
60d873bd22D7345: GPU: Panel Drag Widget Drawing Performance improved the performance. Current bottleneck seems to be in the way how OCIO shaders are used and how we could move it to a
GPUBatch.Added subscriber: @EliSpizzichino
On Lenovo C940 (ice lake with iris graphics) with Linux Manjaro and latest kernel, performance is still very bad i.e. a simple cube animation gives 5 fps, CPU at 100% also on performance mode set on BIOS, and antialias disabled. Switching to Cycles doesn't help neither switching at different drawing modes.
I'm going to sell this brand new pc since this bug is still unsolved and like this, blender 2.82a is unusable
@Jeroen-Bakker We appreciate your work on this, thank you! 😊
After D7357: GPUViewport: Use GPUBatch for viewport drawing the bottleneck shifts to icon rendering. It is responsive, but still not on par with previous generations.
Added subscriber: @Gilberto.R
@Jeroen-Bakker Good work! Keep Going!
I don't know what it is in the immediate mode code that causes performance issues. But some random ideas that might help:
strict_vertex_lenon/off, maybe switching flags is problematic.glBufferDatato copy data from own allocated memory instead of usingglMapBufferRange.This issue was referenced by
862ec82942862ec82942has been reverted for now, until crashes are fixed.FYI, the April 10 build did fix viewport performance massively from 6-12 FPS to a very nice 30 -70FPS for a primitive sphere on my Icelake i7 Surface laptop with integrated GPU.
I know the fix has been reverted but this gives me hope that I will be able to use Blender again.
Thanks.
Removed subscriber: @floetenmaul
Removed subscriber: @tihkal-4
This issue was referenced by
502b8e0f08This issue was referenced by
5d9d246851Tried out the 2.83 experimental from April 16th and so far it feels good! The improved framerate seems on par with what I'd expect for integrated graphics. Any further optimization is a bonus at this point.
Thanks so much for addressing these issues and all the work. Also kind of cool to see THE brecht working on our issue :)
The blender 2.90 alpha also works much much better than what Blender 2.8x used to with a Surface Pro 7! Thank you so much for the amazing work! Resizing the 3D viewport and moving the window still cause some lag at times, but other than that it's massively improved! Super exciting!
Lowering the priority as it is in a workable state. I still want to improve as it is not on par with other platforms.
Intel 10th gen Ice lake cpu extremely slow viewport performance(blender 2.8-2.81)to Intel IRS / Ice lake GPU slow viewport performanceChanged status from 'Confirmed' to: 'Resolved'
Latest test done against previous generation Intel Integrated graphics are that they are similar or just above. At this point we can close this issue as there is no specific work to be done.
While we do continue to work on improving performance in general, potential performance improvements are not handled as bug reports.
Added subscriber: @welcometohe1l
Hello everyone! I ran into the problem of a slow interface and I FIX IT.
My characteristics:
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.