Viewport Slowdown on 11th gen Intel Xe graphics #86778

New Issue

Tom Oliver · 2021-03-21T01:31:10+01:00

Tom Oliver commented

2021-03-21 01:31:10 +01:00

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits

Graphics card:	Intel(R) Iris(R) Xe Graphics Intel 4.5.0 - Build 27.20.100.8935	@tommyoliversays, @CuriousHobbyist (#93114), @Jonathan-Monsonego (#93039), @Pyer (#93505), @Charlie3521 (#93257), @ImaRealBoi (#87147)
	Quadro RTX 3000 with Max-Q - 4.5.0 NVIDIA 472.39	@Stay_Here

Blender Version
Broken: version: 2.92.0, 2.93
Worked: 2.83 LTS (better but not perfect, just takes longer for it to start occuring, maybe an hour as opposed to around 20 minutes in 2.92).

Short description of error
Working on a model slowly brings viewport down to single digit framerates.
It seems to be a twofold issue. Whenever you hit spacebar to playback animation, Blender starts using up more RAM. After working for about 15 minutes, 2.92 RAM usage increased from ~500MB at launch to over 3GB in the same scene while idle. Rotating the viewport also spikes GPU usage to over 50%, which immediately drops back to single percent digits when idling.


Memory at launch	15 mins after	Spikes rotating viewport

Exact steps for others to reproduce the error

moving verts around over time or
hit spacebar to playback animation or

In #93114#1254781, @Stay_Here wrote:
The most likely scenario in my case is when two or more Blender(s) are launched. For example, open Blender.exe twice, then load two different characters in the two Blender windows. Let's say, character A and character B are loaded in the Blender window A and window B, respectively. After that, I spend some time on sculpting character A, and use the character B as a reference character. In this setup, Blender window B is seldom touched or manipulated, since it is just for reference.

After about 10 mins to 2 hours on sculpting character A on the window A and open YouTube to listen some music, I jump to the Blender window B to navigate and change the view to the reference character B. At this moment, the lag in the solid viewport in the window B can be quite likely to happen. However, at the same moment, navigating in the window A is still smooth and unaffected.

imp2.blend

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits | Graphics card: | Intel(R) Iris(R) Xe Graphics Intel 4.5.0 - Build 27.20.100.8935 | @tommyoliversays, @CuriousHobbyist (#93114), @Jonathan-Monsonego (#93039), @Pyer (#93505), @Charlie3521 (#93257), @ImaRealBoi (#87147) | -- | -- | -- | | | Quadro RTX 3000 with Max-Q - 4.5.0 NVIDIA 472.39 | @Stay_Here **Blender Version** Broken: version: 2.92.0, 2.93 Worked: 2.83 LTS (better but not perfect, just takes longer for it to start occuring, maybe an hour as opposed to around 20 minutes in 2.92). **Short description of error** Working on a model slowly brings viewport down to single digit framerates. It seems to be a twofold issue. Whenever you hit spacebar to playback animation, Blender starts using up more RAM. After working for about 15 minutes, 2.92 RAM usage increased from ~500MB at launch to over 3GB in the same scene while idle. Rotating the viewport also spikes GPU usage to over 50%, which immediately drops back to single percent digits when idling. | ![ram_startup.png](https://archive.blender.org/developer/F9908521/ram_startup.png) | ![ram_usage.png](https://archive.blender.org/developer/F9908523/ram_usage.png) | ![ram_uptick.gif](https://archive.blender.org/developer/F9908522/ram_uptick.gif) | -- | -- | -- | | Memory at launch | 15 mins after | Spikes rotating viewport **Exact steps for others to reproduce the error** - moving verts around over time or - hit spacebar to playback animation or > In #93114#1254781, @Stay_Here wrote: > The most likely scenario in my case is when two or more Blender(s) are launched. For example, open Blender.exe twice, then load two different characters in the two Blender windows. Let's say, character A and character B are loaded in the Blender window A and window B, respectively. After that, I spend some time on sculpting character A, and use the character B as a reference character. In this setup, Blender window B is seldom touched or manipulated, since it is just for reference. > > After about 10 mins to 2 hours on sculpting character A on the window A and open YouTube to listen some music, I jump to the Blender window B to navigate and change the view to the reference character B. At this moment, the lag in the solid viewport in the window B can be quite likely to happen. However, at the same moment, navigating in the window A is still smooth and unaffected. [imp2.blend](https://archive.blender.org/developer/F9901664/imp2.blend)

Tom Oliver commented

2021-03-21 01:31:10 +01:00

Added subscriber: @tommyoliversays

blender-admin commented

2021-03-21 01:31:10 +01:00

#98332 was marked as duplicate of this issue

blender-admin commented

2021-03-21 01:31:10 +01:00

#97972 was marked as duplicate of this issue

blender-admin commented

2021-03-21 01:31:10 +01:00

#97781 was marked as duplicate of this issue

blender-admin commented

2021-03-21 01:31:10 +01:00

#97668 was marked as duplicate of this issue

blender-admin commented

2021-03-21 01:31:10 +01:00

#94020 was marked as duplicate of this issue

blender-admin commented

2021-03-21 01:31:10 +01:00

#96043 was marked as duplicate of this issue

blender-admin commented

2021-03-21 01:31:10 +01:00

#96566 was marked as duplicate of this issue

blender-admin commented

2021-03-21 01:31:10 +01:00

#96086 was marked as duplicate of this issue

blender-admin commented

2021-03-21 01:31:10 +01:00

#86342 was marked as duplicate of this issue

blender-admin commented

2021-03-21 01:31:10 +01:00

#91082 was marked as duplicate of this issue

blender-admin commented

2021-03-21 01:31:10 +01:00

#95559 was marked as duplicate of this issue

blender-admin commented

2021-03-21 01:31:10 +01:00

#94864 was marked as duplicate of this issue

blender-admin commented

2021-03-21 01:31:10 +01:00

#87147 was marked as duplicate of this issue

blender-admin commented

2021-03-21 01:31:10 +01:00

#93257 was marked as duplicate of this issue

blender-admin commented

2021-03-21 01:31:10 +01:00

#93505 was marked as duplicate of this issue

blender-admin commented

2021-03-21 01:31:10 +01:00

#93039 was marked as duplicate of this issue

blender-admin commented

2021-03-21 01:31:10 +01:00

#93114 was marked as duplicate of this issue

Tom Oliver commented

2021-03-25 01:08:59 +01:00

Okay, figured out some more info.

It seems to be a twofold issue. Whenever you hit spacebar to playback animation, Blender starts using up more RAM. After working for about 15 minutes, 2.92 RAM usage increased from ~500MB at launch to over 3GB in the same scene while idle. Rotating the viewport also spikes GPU usage to over 50%, which immediately drops back to single percent digits when idling.

Okay, figured out some more info. It seems to be a twofold issue. Whenever you hit spacebar to playback animation, Blender starts using up more RAM. After working for about 15 minutes, 2.92 RAM usage increased from ~500MB at launch to over 3GB in the same scene while idle. Rotating the viewport also spikes GPU usage to over 50%, which immediately drops back to single percent digits when idling. ![ram_startup.png](https://archive.blender.org/developer/F9908521/ram_startup.png) ![ram_uptick.gif](https://archive.blender.org/developer/F9908522/ram_uptick.gif) ![ram_usage.png](https://archive.blender.org/developer/F9908523/ram_usage.png)

Germano Cavalcante commented

2021-11-17 13:37:05 +01:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2021-11-17 13:37:05 +01:00

It seems related to #93114 (Blender 3.0b becomes laggy after being open for some time) and #93039 (Memory leak while rotating the viewport (default cube))
Interesting that this one also involves the Intel Iris Xe GPU.
I'll merge all these reports into one as soon as I have more details.

It seems related to #93114 (Blender 3.0b becomes laggy after being open for some time) and #93039 (Memory leak while rotating the viewport (default cube)) Interesting that this one also involves the `Intel Iris Xe` GPU. I'll merge all these reports into one as soon as I have more details.

Germano Cavalcante commented

2021-11-18 13:42:19 +01:00

Added subscribers: @Stay_Here, @Jonathan-Monsonego, @CuriousHobbyist

Germano Cavalcante commented

2021-11-18 13:42:49 +01:00

Added subscribers: @Germano, @Raimund58

Germano Cavalcante commented

2021-11-18 13:47:13 +01:00

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

Germano Cavalcante commented

2021-11-18 13:47:13 +01:00

I edited the description using the information from each report (hope I understood the images correctly).
I'm setting it with high priority, though I'm not sure it can be fixed before 3.0 release

I edited the description using the information from each report (hope I understood the images correctly). I'm setting it with high priority, though I'm not sure it can be fixed before 3.0 release

Raimund Klink commented

2021-11-18 14:38:14 +01:00

@mano-wii The user @Stay_Here also has a Intel Iris. See: https://developer.blender.org/T93114#1255452
Makes me wonder if this bug could be the fault of the Intel CPU/firmware.

@mano-wii The user @Stay_Here also has a Intel Iris. See: https://developer.blender.org/T93114#1255452 Makes me wonder if this bug could be the fault of the Intel CPU/firmware.

Stay_Here commented

2021-11-18 20:59:50 +01:00

Then based on the method of the observation from previous comments, could I also wonder if this bug could be the fault of Windows 10 please? Because all 4 users are using Windows 10.

I guess that this is just too hard to fix it anytime soon, largely because it is hard to reproduce the problem.

If I was a Blender developer, I would just wait and see if anymore users (date points) have the same issue. It may be too early to conclude that the bug is the fault of the Intel CPU or Intel GPU, because Intel has a dominant market share in the today PC market. Thousands of Blender users have Intel CPUs, but only a handful users actually report the issue. If there is really a fault, then I expect way more Intel users to report.

If we have 10 or 20 more users who have the same issue, then we may know if the fault is actually due to the Intel CPU or Intel GPU. That is why collecting data points is very important to finally solve the problem, if the problem is hard to reproduce.

I appreciate the hard effort from developers~

Then based on the method of the observation from previous comments, could I also wonder if this bug could be the fault of Windows 10 please? Because all 4 users are using Windows 10. I guess that this is just too hard to fix it anytime soon, largely because it is hard to reproduce the problem. If I was a Blender developer, I would just wait and see if anymore users (date points) have the same issue. It may be too early to conclude that the bug is the fault of the Intel CPU or Intel GPU, because Intel has a dominant market share in the today PC market. Thousands of Blender users have Intel CPUs, but only a handful users actually report the issue. If there is really a fault, then I expect way more Intel users to report. If we have 10 or 20 more users who have the same issue, then we may know if the fault is actually due to the Intel CPU or Intel GPU. That is why collecting data points is very important to finally solve the problem, if the problem is hard to reproduce. I appreciate the hard effort from developers~

Jonathan Monsonego commented

2021-11-18 23:02:18 +01:00

In my merged report I’ve noted that the problem is less felt in earlier Blender version. For that I think the bug is in Blender.

Regarding reproducibility - is it hard? Do we know anyone with Intel Iris that does not experience the issue?

I might try to take a look at this again myself but windbg is my worst enemy. The allocated memory is native and I couldn’t understand at a first glance what objects were allocated there.
Since it’s reproducible in the most basic setup, someone with knowledge of how the view port renders can quickly find the relevant native calls and see how it differs between version 2.8 and 2.9.

Regarding severity - the fact that intel GPUs are so common rightfully justifies the current severity of High.

Indeed a big thanks to the developers 💪🏼

In my merged report I’ve noted that the problem is less felt in earlier Blender version. For that I think the bug is in Blender. Regarding reproducibility - is it hard? Do we know anyone with Intel Iris that does not experience the issue? I might try to take a look at this again myself but windbg is my worst enemy. The allocated memory is native and I couldn’t understand at a first glance what objects were allocated there. Since it’s reproducible in the most basic setup, someone with knowledge of how the view port renders can quickly find the relevant native calls and see how it differs between version 2.8 and 2.9. Regarding severity - the fact that intel GPUs are so common rightfully justifies the current severity of High. Indeed a big thanks to the developers 💪🏼

Sergey Sharybin commented

2021-11-19 18:02:18 +01:00

Added subscriber: @Sergey

Sergey Sharybin commented

2021-11-19 18:02:18 +01:00

Seems to be related to the GPU driver. We've reproduced the issue on a number of Intel cards available at the studio, and we are in contact with Intel to get the issue resolved.

We did not see memory leak on any other GPU on neither Windows nor Linux. The report from @Stay_Here might be coming from other root cause.

Seems to be related to the GPU driver. We've reproduced the issue on a number of Intel cards available at the studio, and we are in contact with Intel to get the issue resolved. We did not see memory leak on any other GPU on neither Windows nor Linux. The report from @Stay_Here might be coming from other root cause.

Stay_Here commented

2021-11-20 01:06:55 +01:00

Congratulations for reproducing the problem! Bug detection and fixing are complicated and challenging tasks.

The report from @Stay_Here might be coming from other root cause.

@Sergey , maybe you're right. Today has a good news, since I have found another method to fix the lag, in addition to exit and reboot the program. It turns out that switching from mouse to my drawing tablet stylus can fix the lag.

I am using HUION Wireless Drawing Tablet Dial Q620M to sculpt in Blender. Today, the lag happened twice when I switched from the stylus to mouse - here, the "switch" means the change from using stylus to move the cursor, to using mouse to move the cursor.

Of course, there were more than one hundred times of switches today, but the lag only happened twice. Based on my observation, these two lags happened during the period of clicking the File menu. In this period, I switched from using stylus to mouse, and then used mouse to click "File" -> "Save as" -> change file name -> "Save". After that, it took about 5 seconds for Blender to actually save the file. One lag happened right at the moment of the switch, and the other lag happened during the period of waiting for the 5 seconds.

I was expecting that the lag would have continued forever until I had restarted the program. However, coincidentally, I found that switching back from my mouse to my stylus fixed the lag, and everything became normal - whether I used mouse or used stylus, both became smooth again. This may also echo the video: https://developer.blender.org/T93114#1255452
where shows that it is not really the lag of the system, because the lag disappears when I click the gizmo axis to navigate instead. (although clicking the gizmo axis does not fix the lag.)

Although I am not saying that the lag is with 100% certainty caused by my drawing tablet, the next and future step for me is that maybe I will try to update the driver for my drawing tablet. But even without updating the driver, switching back from mouse to stylus fixing the lag is an enough solution to me, and I can live with that.

My suggest:
Maybe Blender Bug report template needs improvement, because the standard report template omits two important questions:

Do you use any drawing tablet?
If yes, what is the name and model number of the drawing tablet?

It is possible that an incompatible drawing tablet can cause unexpected issues and consequently increase the difficulty for bug detection and fixing.

Congratulations for reproducing the problem! Bug detection and fixing are complicated and challenging tasks. > The report from @Stay_Here might be coming from other root cause. @Sergey , maybe you're right. Today has a good news, since I have found another method to fix the lag, in addition to exit and reboot the program. It turns out that **switching from mouse to my drawing tablet stylus can fix the lag**. I am using HUION Wireless Drawing Tablet Dial Q620M to sculpt in Blender. Today, the lag happened twice when I switched from the stylus to mouse - here, the "switch" means the change from using stylus to move the cursor, to using mouse to move the cursor. Of course, there were more than one hundred times of switches today, but the lag only happened twice. Based on my observation, these two lags happened during the period of clicking the File menu. In this period, I switched from using stylus to mouse, and then used mouse to click "File" -> "Save as" -> change file name -> "Save". After that, it took about 5 seconds for Blender to actually save the file. One lag happened right at the moment of the switch, and the other lag happened during the period of waiting for the 5 seconds. I was expecting that the lag would have continued forever until I had restarted the program. However, coincidentally, I found that switching back from my mouse to my stylus fixed the lag, and everything became normal - whether I used mouse or used stylus, both became smooth again. This may also echo the video: https://developer.blender.org/T93114#1255452 where shows that it is not really the lag of the system, because the lag disappears when I click the gizmo axis to navigate instead. (although clicking the gizmo axis does not fix the lag.) Although I am not saying that the lag is with 100% certainty caused by my drawing tablet, the next and future step for me is that maybe I will try to update the driver for my drawing tablet. But even without updating the driver, switching back from mouse to stylus fixing the lag is an enough solution to me, and I can live with that. My suggest: **Maybe Blender Bug report template needs improvement, because the standard report template omits two important questions**: 1) **Do you use any drawing tablet?** 2) **If yes, what is the name and model number of the drawing tablet?** It is possible that an incompatible drawing tablet can cause unexpected issues and consequently increase the difficulty for bug detection and fixing.

Gabriel commented

2021-11-21 06:48:01 +01:00

@Stay_Here That's interesting. So it seems like it might be a mouse-related issue that's somehow causing something to build up. Also it's interesting that it only happens with Iris Xe.

Jonathan Monsonego commented

2021-11-21 09:02:10 +01:00

I don’t think it’s the mouse because I’ve also reproduced it using only numpad something to rotate the view, not touching the mouse.

Stay_Here commented

2021-11-23 04:19:39 +01:00

2257-4890.mp4

My solution may only work to my specific case. I believe that the lag is the fault of my drawing tablet, though not 100% sure.

[2257-4890.mp4](https://archive.blender.org/developer/F11868661/2257-4890.mp4) My solution may only work to my specific case. I believe that the lag is the fault of my drawing tablet, though not 100% sure.

Gulfie X commented

2021-11-28 00:14:42 +01:00

Added subscriber: @gulfie

Gulfie X commented

2021-11-28 00:14:42 +01:00

Wanted to pop in and add "me too". Things start off running very well and then start to get choppy after 10 minutes or so, eventually becoming super difficult to use. The issue is very apparent while doing grease pencil animation on Windows 10, and I just confirmed it happens with or without the tablet.

I will note that I'm not maxing out my RAM and I'm still having issues, I still have about 20% left according to Task Manager and things are running very, very slowly.


Blender:
=====================================

version: 2.93.5, branch: master, commit date: 2021-10-05 12:04, hash: a791bdabd0b2, type: release
build date: 2021-10-06, 06:44:49
platform: Windows
binary path: 'C:\\Program Files\\Blender Foundation\\Blender 2.93\\blender.exe'
build cflags: /W3 /w34062 /w34115 /w34189 /wd4018 /wd4146 /wd4065 /wd4127 /wd4181 /wd4200 /wd4244 /wd4267 /wd4305 /wd4800 /wd4828 /wd4996 /wd4661 /we4013 /we4133 /we4431 /w35038 /DWIN32 /D_WINDOWS /W3 /nologo /J /Gd /MP /bigobj -openmp   
build cxxflags: /W3 /w34062 /w34115 /w34189 /wd4018 /wd4146 /wd4065 /wd4127 /wd4181 /wd4200 /wd4244 /wd4267 /wd4305 /wd4800 /wd4828 /wd4996 /wd4661 /we4013 /we4133 /we4431 /w35038 /DWIN32 /D_WINDOWS /W3  /EHsc /nologo /J /Gd /MP /EHsc /bigobj /permissive- /Zc:twoPhase- -openmp /std:c++17 /Zc:__cplusplus   
build linkflags: /MACHINE:X64  /SUBSYSTEM:CONSOLE /STACK:2097152 /ignore:4049 /ignore:4217 /ignore:4221
build system: CMake


OpenGL:
=====================================

renderer:	'Intel(R) Iris(R) Xe Graphics'
vendor:		'Intel'
version:	'4.5.0 - Build 30.0.101.1069'

Wanted to pop in and add "me too". Things start off running very well and then start to get choppy after 10 minutes or so, eventually becoming super difficult to use. The issue is very apparent while doing grease pencil animation on Windows 10, and I just confirmed it happens with or without the tablet. I will note that I'm not maxing out my RAM and I'm still having issues, I still have about 20% left according to Task Manager and things are running very, very slowly. --- ``` Blender: ===================================== version: 2.93.5, branch: master, commit date: 2021-10-05 12:04, hash: a791bdabd0b2, type: release build date: 2021-10-06, 06:44:49 platform: Windows binary path: 'C:\\Program Files\\Blender Foundation\\Blender 2.93\\blender.exe' build cflags: /W3 /w34062 /w34115 /w34189 /wd4018 /wd4146 /wd4065 /wd4127 /wd4181 /wd4200 /wd4244 /wd4267 /wd4305 /wd4800 /wd4828 /wd4996 /wd4661 /we4013 /we4133 /we4431 /w35038 /DWIN32 /D_WINDOWS /W3 /nologo /J /Gd /MP /bigobj -openmp build cxxflags: /W3 /w34062 /w34115 /w34189 /wd4018 /wd4146 /wd4065 /wd4127 /wd4181 /wd4200 /wd4244 /wd4267 /wd4305 /wd4800 /wd4828 /wd4996 /wd4661 /we4013 /we4133 /we4431 /w35038 /DWIN32 /D_WINDOWS /W3 /EHsc /nologo /J /Gd /MP /EHsc /bigobj /permissive- /Zc:twoPhase- -openmp /std:c++17 /Zc:__cplusplus build linkflags: /MACHINE:X64 /SUBSYSTEM:CONSOLE /STACK:2097152 /ignore:4049 /ignore:4217 /ignore:4221 build system: CMake ``` ``` OpenGL: ===================================== renderer: 'Intel(R) Iris(R) Xe Graphics' vendor: 'Intel' version: '4.5.0 - Build 30.0.101.1069' ``` ![Screenshot 2021-11-27 181212.png](https://archive.blender.org/developer/F12496713/Screenshot_2021-11-27_181212.png)

Germano Cavalcante commented

2021-12-02 17:23:00 +01:00

Added subscriber: @Pyer

Germano Cavalcante commented

2021-12-02 17:30:38 +01:00

Added subscriber: @Charlie3521

Chito Misaki commented

2021-12-04 02:54:27 +01:00

In my opinion, the problem is that Intel Iris grafics allocates half of the physical memory to the graphics memory.
If you have 8GB of physical memory, the software has only 4GB of physical memory left.
This memory size will be less than the minimum amount of memory that BLENDER can operate.
My laptop had 8GB of physical memory, so I added 8GB of memory to 16GB, but since Intel Iris Graphics uses half of the physical memory,
the amount of physical memory that the software can use is 8GB. Only increased.
According to Intel's official homepage, user cannot set the amount of graphic memory arbitrarily.

In my opinion, the problem is that Intel Iris grafics allocates half of the physical memory to the graphics memory. If you have 8GB of physical memory, the software has only 4GB of physical memory left. This memory size will be less than the minimum amount of memory that BLENDER can operate. My laptop had 8GB of physical memory, so I added 8GB of memory to 16GB, but since Intel Iris Graphics uses half of the physical memory, the amount of physical memory that the software can use is 8GB. Only increased. According to Intel's official homepage, user cannot set the amount of graphic memory arbitrarily.

Félix Gutiérrez commented

2021-12-07 05:25:19 +01:00

Added subscriber: @SnarkBucham

Félix Gutiérrez commented

2021-12-07 05:25:19 +01:00

Hello, I do not know if it is related, but the case is very similar, I will leave it here in case it were so (I hope so because blender is practically unusable for me currently). https://developer.blender.org/T87147 . In my case the error occurs using the mouse or the pencil. I can not contribute more for the same reason as in that post, it is a difficult error to reproduce (although it always happens) and I have no knowledge to track the bug. Greetings and thank you very much for your work and effort.

Piotr Nikov commented

2021-12-12 11:47:44 +01:00

Hello!
Here is a video illustrating the issue in realtime. I left the TaskManager in frame in case it reveals something.
The steps:
. I load a simple scene (GreasePencil in my case).
. I go back and forth in the Timeline. It's smooth.
. I switch to Render Viewport..
. Just before fiddling around in the Timeline again I opened the Preference Window and moved it around. Just to show that the whole Blender interface is still smooth.
. I then went back and forth in the Timeline. Slowdown appears. The playhead no longer sticks to the mouse/pen movement.
. Opening the Preference Window and moving it around shows stutter and no longer is smooth.
Could this be a memory leak of sorts? A driver issue? Or is it because these Intel cards don't have any VRAM and start using er, something else (I have 16G of Ram and a lot of disk space)?
Either way it'd be great to find a solution for this. Being able to work on the go (with the Surface Pro in my case) is pretty awesome...
Thanks for any helpful hints or insights!

Piotr

My Movie 1-720p30.mp4

PS I'm on a SP8 WIN11 latest Intel Drivers.

Hello! Here is a video illustrating the issue in realtime. I left the TaskManager in frame in case it reveals something. The steps: . I load a simple scene (GreasePencil in my case). . I go back and forth in the Timeline. It's smooth. . I switch to Render Viewport.. . Just before fiddling around in the Timeline again I opened the Preference Window and moved it around. Just to show that the whole Blender interface is still smooth. . I then went back and forth in the Timeline. Slowdown appears. The playhead no longer sticks to the mouse/pen movement. . Opening the Preference Window and moving it around shows stutter and no longer is smooth. Could this be a memory leak of sorts? A driver issue? Or is it because these Intel cards don't have any VRAM and start using er, something else (I have 16G of Ram and a lot of disk space)? Either way it'd be great to find a solution for this. Being able to work on the go (with the Surface Pro in my case) is pretty awesome... Thanks for any helpful hints or insights! Piotr [My Movie 1-720p30.mp4](https://archive.blender.org/developer/F12733544/My_Movie_1-720p30.mp4) PS I'm on a SP8 WIN11 latest Intel Drivers.

Germano Cavalcante commented

2021-12-21 14:41:30 +01:00

Added subscribers: @ImaRealBoi, @afeso, @Jako, @carl.e.henderson, @iss, @antoniov, @AquilaTheEagle, @Harley, @filedescriptor

Germano Cavalcante commented

2021-12-21 14:44:53 +01:00

Removed subscribers: @antoniov, @Germano

Franklyn Afeso commented

2021-12-22 12:40:27 +01:00

I'm experiencing similar issue too with a 10th Gen intel Core i5. Issue occurs in the VSE and the 3D View when sculpting. I also use a graphics tablet (Wacom intuous 5 Touch). My issue seems to have been merged with this.

In regards to the tablet though, on earlier beta build I had to change my input type from automatic to WInTab because there was a noticeable lag when working, which I also reported.

I'm experiencing similar issue too with a 10th Gen intel Core i5. Issue occurs in the VSE and the 3D View when sculpting. I also use a graphics tablet (Wacom intuous 5 Touch). My issue seems to have been merged with this. In regards to the tablet though, on earlier beta build I had to change my input type from automatic to WInTab because there was a noticeable lag when working, which I also reported.

Franklyn Afeso commented

2021-12-23 10:10:51 +01:00

This issue is also present with 3.1 Alpha.

Something I've noticed is, while this is happening in the viewport, shortcuts and keyboard actions are not affected.

for example I can do Shift + A, and use my keyboard to navigate the the options, and it responds fine, but the moment I try to select or do anything in the viewport, the Lag happens.

Also, from the looks of seems to be an Intel issue, as I'm experiencing the same on a very light scene in blender. 2.93.6. My guess is there's something wrong with the Drivers.

It took a bit longer to notice, but now, I can definitely see it. Going to re-install the drivers, and see what happens. Might option for an older build.

This issue is also present with 3.1 Alpha. Something I've noticed is, while this is happening in the viewport, shortcuts and keyboard actions are not affected. for example I can do Shift + A, and use my keyboard to navigate the the options, and it responds fine, but the moment I try to select or do anything in the viewport, the Lag happens. Also, from the looks of seems to be an Intel issue, as I'm experiencing the same on a very light scene in blender. 2.93.6. My guess is there's something wrong with the Drivers. It took a bit longer to notice, but now, I can definitely see it. Going to re-install the drivers, and see what happens. Might option for an older build.

Thomas Lynch commented

2022-01-03 00:09:35 +01:00

Added subscriber: @super248

Thomas Lynch commented

2022-01-03 00:09:35 +01:00

I just wanted to chime in to say that I am experiencing the same problem. I'm running a Surface Laptop 3 with integrated Intel Iris Plus GPU (Gen 11), an i7-1065G7 CPU, and 32GB of RAM. I have a touch screen but no drawing pad. I'm using Blender 3.0.0.

Blender starts out running smoothly, but after a while (especially if I'm running animations) it becomes very laggy to perform any operation. Task manager indicates that the memory usage is around 4GB, which is much higher than when Blender first opened.

I will post a video next time I am on Blender. I'm not sure when that will be though, because I have a deadline to hit in 2 weeks. If it helps, I also tried out Cinema 4D today and this issue didn't occur.

Thanks for helping develop this otherwise awesome software.

I just wanted to chime in to say that I am experiencing the same problem. I'm running a Surface Laptop 3 with integrated Intel Iris Plus GPU (Gen 11), an i7-1065G7 CPU, and 32GB of RAM. I have a touch screen but no drawing pad. I'm using Blender 3.0.0. Blender starts out running smoothly, but after a while (especially if I'm running animations) it becomes very laggy to perform any operation. Task manager indicates that the memory usage is around 4GB, which is much higher than when Blender first opened. I will post a video next time I am on Blender. I'm not sure when that will be though, because I have a deadline to hit in 2 weeks. If it helps, I also tried out Cinema 4D today and this issue didn't occur. Thanks for helping develop this otherwise awesome software.

Franklyn Afeso commented

2022-01-10 15:31:40 +01:00

Anyone got a working update regarding this issue. Nothing I've tried works. 2.83.16 LTS seems to take a while before the Lag kicks in (or maybe I'm just not noticing it).

It has made blender really unusable for the past weeks now, and I'm having to use another program if I want to do any sculpting for more than 10 minutes.

Anyone got a working update regarding this issue. Nothing I've tried works. 2.83.16 LTS seems to take a while before the Lag kicks in (or maybe I'm just not noticing it). It has made blender really unusable for the past weeks now, and I'm having to use another program if I want to do any sculpting for more than 10 minutes.

William B commented

2022-01-10 16:51:53 +01:00

I still haven't found anything that works, and agree that it becomes unusable. I just have to restart the program every 10-15 minutes (which takes about 30 seconds). I actually start a second instance so that I don't have to wait on the startup and switch to that one. I also keep checking the Intel drivers and new Blenders to hope one of the two companies fix it!

Franklyn Afeso commented

2022-01-11 13:23:30 +01:00

Yeah. The startup time helps. Its just that steady decline in performance over a short period of time, can get frustrating.

emil commented

2022-01-24 15:26:49 +01:00

Added subscriber: @emilgars

Germano Cavalcante commented

2022-01-24 22:14:56 +01:00

Added subscribers: @trentity-lowery, @HDMaster84

Franklyn Afeso commented

2022-01-25 16:01:22 +01:00

Not sure how much this helps, but this is something that happens in the viewport, whenever this issue comes up.

![Screenshot (257).png](https://archive.blender.org/developer/F12823264/Screenshot__257_.png) Not sure how much this helps, but this is something that happens in the viewport, whenever this issue comes up.

Lucas commented

2022-02-04 04:02:37 +01:00

Added subscriber: @CartolaBRA

Lucas commented

2022-02-04 04:02:37 +01:00

Bug Report Final.mp4
Small animation running under the same conditions, just changing the intel gpu driver version. (Blender 2.93.7) (i5 8265u, UHD Graphics 620)

[Bug Report Final.mp4](https://archive.blender.org/developer/F12844825/Bug_Report_Final.mp4) Small animation running under the same conditions, just changing the intel gpu driver version. (Blender 2.93.7) (i5 8265u, UHD Graphics 620)

Franklyn Afeso commented

2022-02-04 08:51:37 +01:00

Hey @CartolaBRA what version of windows are you running? and where did you get the previous driver?

I have a Dell Latitude and can only get the latest driver (27.20.100.9664) from their site. I tried downloading the older driver from intel, but the install failed, saying my OS isn't compatible (windows 10 21H1 [19043.1503]).

This issue has really made blender frustrating to use.

Hey @CartolaBRA what version of windows are you running? and where did you get the previous driver? I have a Dell Latitude and can only get the latest driver (27.20.100.9664) from their site. I tried downloading the older driver from intel, but the install failed, saying my OS isn't compatible (windows 10 21H1 [19043.1503]). This issue has really made blender frustrating to use.

Franklyn Afeso commented

2022-02-04 10:54:06 +01:00

okay, so I've finally been able to get version 26.20.100.8184 back on my system.

Downloaded it from intel's site here: https://www.intel.com/content/www/us/en/download/19344/29530/intel-graphics-windows-dch-drivers.html
and followed the instruction on how to remove previous version completely. (took 2 trials before it was successful)

also, I downloaded the zipped version, so I could update manually by pointing it to the folder I extracted to in device manager. would begin testing now and see if there's improvement, and I hope windows update does not download the latest driver for now.

okay, so I've finally been able to get version 26.20.100.8184 back on my system. Downloaded it from intel's site here: https://www.intel.com/content/www/us/en/download/19344/29530/intel-graphics-windows-dch-drivers.html and followed the instruction on how to remove previous version completely. (took 2 trials before it was successful) also, I downloaded the zipped version, so I could update manually by pointing it to the folder I extracted to in device manager. would begin testing now and see if there's improvement, and I hope windows update does not download the latest driver for now.

Lucas commented

2022-02-04 12:19:25 +01:00

@afeso My Windows version is 21H2, 19044.1466 and I downloaded the driver from the same website you mentioned above. I also use Blender on a Dell, an Inspiron 3583, with an 8th generation i5 (i5 8265u), and installing the driver 26.20.100.8141 is solving the problem. I used Blender in my spare time, but with this problem, I stopped using it. After installing this older driver, I'm going back to using Blender. [Sorry for any English errors (Google Translate)]

Franklyn Afeso commented

2022-02-04 13:31:52 +01:00

@CartolaBRA No problems. I've been testing the older driver for some hours now, and everything has been stable. Many thanks for your video that showed a working version of the driver.

husnu commented

2022-02-05 01:38:03 +01:00

Added subscriber: @husnubey

husnu commented

2022-02-05 01:57:28 +01:00

When I resize viewport panels memory usage is increasing exponentially.
New Project.mp4

When I resize viewport panels memory usage is increasing exponentially. [New Project.mp4](https://archive.blender.org/developer/F12847255/New_Project.mp4)

Daniel Beyer commented

2022-02-07 11:36:14 +01:00

Added subscriber: @obox

Daniel Beyer commented

2022-02-07 11:36:14 +01:00

i5 11600k
intel UHD750 graphics.
win 10
blender 2.82, 2.91, 2.93, 3.0
Every aspect of blender is affected, cycles, eevee, viewport maneuvering, phisics simulations, evrything. Rendering and simulations increase the slowing down rate. Maybe a GPU memory flush button could be added as an alternative to restarting blender, or a timer that flushes memory if activated e.g. every five minutes. This could be manually inactivated for tasks that require the preservation of data in memory, but could be turned on while working in the viewport.

i5 11600k intel UHD750 graphics. win 10 blender 2.82, 2.91, 2.93, 3.0 Every aspect of blender is affected, cycles, eevee, viewport maneuvering, phisics simulations, evrything. Rendering and simulations increase the slowing down rate. Maybe a GPU memory flush button could be added as an alternative to restarting blender, or a timer that flushes memory if activated e.g. every five minutes. This could be manually inactivated for tasks that require the preservation of data in memory, but could be turned on while working in the viewport.

Franklyn Afeso commented

2022-02-07 17:13:11 +01:00

@obox try downgrading your driver to the one listed above. I've done that and blender's been working fine for me now. Like you said, it affected every part of blender

Germano Cavalcante commented

2022-02-11 16:55:18 +01:00

Added subscribers: @Granty, @OmarEmaraDev

Zach Ogdahl commented

2022-02-13 04:44:34 +01:00

Added subscriber: @gokarter64

William B commented

2022-02-14 12:00:41 +01:00

Wow, @afeso that solved it for me! Blender is finally usable again (and no collateral problems so far either. . 48 hours in)! Please, everyone on this thread, see Franklyn's comment. Slight variation that worked here:

The newest intel driver actually works fine, it is just that my Dell XPS didn't allow it to get installed. This is what tricked me for a while. Neither letting Dell or Intel auto-update drivers changed my Intel® Iris® Plus Graphics 640 to the newest version, it was stuck on the OEM version (27 I think). I thought that it was updating, but it was not.

Download the newest intel driver from this link: (depending on your processor, you may need a different version, but luckily intel has fixed the memory leak in this newest one if you can get your system to use it)
https://www.intel.com/content/www/us/en/download/19344/intel-graphics-windows-dch-drivers.html
Open windows / Device Manager and find Display Adaptors
Turn off all internet connections (Wifi and ethernet) (I thought I could skip this, but you can't)
Find the problem driver (Intel Iris for me), and say "Uninstall", and make sure to check "Delete Files" as well
Actions > Scan for Changes (and repeat steps 4-5) until it only lists "Basic Windows Display" or something like that
Restart (keep internet off)
Install the new intel driver you downloaded
Confirm in your Device Manager that it lists the new version (30.0.101.1340 for me in early 2022)
Turn back on your internet connections, let the system install updates (my laptop's brightness adjustment initially didn't work, but after allowing update to become active again, it all got fixed nicely)

I really hope the others can try this and have success.

Blender developers --> I noticed about a month ago that Adobe Illustrator somehow checks the drivers and notified me that my particular driver was problematic. It warned me when trying to open the program. This was really helpful since I then knew that Illustrator's performance (which is surprisingly not very affected by this driver compared to Blender which is devastated by it) could be better. It evidently can hurt enough users that Adobe tries to deal with it, so perhaps Blender could do the same, and help unsuspecting new users get a good Blender experience by warning them.

Wow, @afeso that solved it for me! Blender is finally usable again (and no collateral problems so far either. . 48 hours in)! Please, everyone on this thread, see Franklyn's comment. Slight variation that worked here: The newest intel driver actually works fine, it is just that my Dell XPS didn't allow it to get installed. This is what tricked me for a while. Neither letting Dell or Intel auto-update drivers changed my Intel® Iris® Plus Graphics 640 to the newest version, it was stuck on the OEM version (27 I think). I thought that it was updating, but it was not. 1. Download the newest intel driver from this link: (depending on your processor, you may need a different version, but luckily intel has fixed the memory leak in this newest one if you can get your system to use it) https://www.intel.com/content/www/us/en/download/19344/intel-graphics-windows-dch-drivers.html 2. Open windows / Device Manager and find Display Adaptors 3. Turn off all internet connections (Wifi and ethernet) (I thought I could skip this, but you can't) 4. Find the problem driver (Intel Iris for me), and say "Uninstall", and make sure to check "Delete Files" as well 5. Actions > Scan for Changes (and repeat steps 4-5) until it only lists "Basic Windows Display" or something like that 6. Restart (keep internet off) 7. Install the new intel driver you downloaded 8. Confirm in your Device Manager that it lists the new version (30.0.101.1340 for me in early 2022) 9. Turn back on your internet connections, let the system install updates (my laptop's brightness adjustment initially didn't work, but after allowing update to become active again, it all got fixed nicely) I really hope the others can try this and have success. Blender developers --> I noticed about a month ago that Adobe Illustrator somehow checks the drivers and notified me that my particular driver was problematic. It warned me when trying to open the program. This was really helpful since I then knew that Illustrator's performance (which is surprisingly not very affected by this driver compared to Blender which is devastated by it) could be better. It evidently can hurt enough users that Adobe tries to deal with it, so perhaps Blender could do the same, and help unsuspecting new users get a good Blender experience by warning them.

Félix Gutiérrez commented

2022-02-14 19:57:02 +01:00

Added subscriber: @william-70

Félix Gutiérrez commented

2022-02-14 19:57:02 +01:00

Hello, in my case Intel notified me yesterday that there was a new update that is exactly the one that @william-70 B (AquilaTheEagle) comments on. I haven't had to uninstall anything, I simply updated from the page with the automatic installer and yes, memory usage no longer increases wildly by making new windows, and especially when creating a new project the memory is reset again. I still don't know if the main problem persists, because I haven't tried it enough yet. But everything seems to indicate that indeed yes (or at least it is an advance). All the best.

Carl Henderson commented

2022-02-14 23:46:27 +01:00

I have just tried the latest Intel Driver located here: https://www.intel.com/content/www/us/en/download/19344/intel-graphics-windows-dch-drivers.html version 30.0.101.1340 with latest Blender 3.0.1 and still have the lagging issue.

I have not tried the older Intel driver named in previous comments (26.20.100.8184) but will try to do so soon.

I have just tried the latest Intel Driver located here: https://www.intel.com/content/www/us/en/download/19344/intel-graphics-windows-dch-drivers.html version 30.0.101.1340 with latest Blender 3.0.1 and still have the lagging issue. I have not tried the older Intel driver named in previous comments (26.20.100.8184) but will try to do so soon.

Félix Gutiérrez commented

2022-02-15 16:46:53 +01:00

At the moment it works fine for me (although I haven't used it for a long time yet). But I have tested memory usage. Before, when opening a new project the memory stayed exactly the same. Now it resets but not completely. I have pushed blender up to 9g and when creating a new one, it only went down to 2900mb. I have closed blender and reopened, I have done it again up to 8g and it has gone down to 1400mb. Just opened it only uses 300-350 mb. I don't know if it's important.

Piotr Nikov commented

2022-02-15 16:52:09 +01:00

In #86778#1307389, @AquilaTheEagle wrote:
Wow, @afeso that solved it for me! Blender is finally usable again (and no collateral problems so far either. . 48 hours in)! Please, everyone on this thread, see Franklyn's comment. Slight variation that worked here:

The newest intel driver actually works fine, it is just that my Dell XPS didn't allow it to get installed. This is what tricked me for a while. Neither letting Dell or Intel auto-update drivers changed my Intel® Iris® Plus Graphics 640 to the newest version, it was stuck on the OEM version (27 I think). I thought that it was updating, but it was not.

Download the newest intel driver from this link: (depending on your processor, you may need a different version, but luckily intel has fixed the memory leak in this newest one if you can get your system to use it)
https://www.intel.com/content/www/us/en/download/19344/intel-graphics-windows-dch-drivers.html

Open windows / Device Manager and find Display Adaptors

Turn off all internet connections (Wifi and ethernet) (I thought I could skip this, but you can't)

Find the problem driver (Intel Iris for me), and say "Uninstall", and make sure to check "Delete Files" as well

Actions > Scan for Changes (and repeat steps 4-5) until it only lists "Basic Windows Display" or something like that

Restart (keep internet off)

Install the new intel driver you downloaded

Confirm in your Device Manager that it lists the new version (30.0.101.1340 for me in early 2022)

Turn back on your internet connections, let the system install updates (my laptop's brightness adjustment initially didn't work, but after allowing update to become active again, it all got fixed nicely)

This totally works for me, no more slowdows!! Thanks @AquilaTheEagle & @Franklyn Afeso (afeso)!!!!

> In #86778#1307389, @AquilaTheEagle wrote: > Wow, @afeso that solved it for me! Blender is finally usable again (and no collateral problems so far either. . 48 hours in)! Please, everyone on this thread, see Franklyn's comment. Slight variation that worked here: > > The newest intel driver actually works fine, it is just that my Dell XPS didn't allow it to get installed. This is what tricked me for a while. Neither letting Dell or Intel auto-update drivers changed my Intel® Iris® Plus Graphics 640 to the newest version, it was stuck on the OEM version (27 I think). I thought that it was updating, but it was not. > 1. Download the newest intel driver from this link: (depending on your processor, you may need a different version, but luckily intel has fixed the memory leak in this newest one if you can get your system to use it) > https://www.intel.com/content/www/us/en/download/19344/intel-graphics-windows-dch-drivers.html > 2. Open windows / Device Manager and find Display Adaptors > 3. Turn off all internet connections (Wifi and ethernet) (I thought I could skip this, but you can't) > 4. Find the problem driver (Intel Iris for me), and say "Uninstall", and make sure to check "Delete Files" as well > 5. Actions > Scan for Changes (and repeat steps 4-5) until it only lists "Basic Windows Display" or something like that > 6. Restart (keep internet off) > 7. Install the new intel driver you downloaded > 8. Confirm in your Device Manager that it lists the new version (30.0.101.1340 for me in early 2022) > 9. Turn back on your internet connections, let the system install updates (my laptop's brightness adjustment initially didn't work, but after allowing update to become active again, it all got fixed nicely) This totally works for me, no more slowdows!! Thanks @AquilaTheEagle & @Franklyn Afeso (afeso)!!!!

Germano Cavalcante commented

2022-02-16 18:47:12 +01:00

Added subscribers: @XZS, @Jeroen-Bakker, @PratikPB2123

橙月 commented

2022-02-20 10:57:43 +01:00

Added subscriber: @0.0

橙月 commented

2022-02-20 10:57:43 +01:00

In #86778#1270942, @Pyer wrote:
Hello!
Here is a video illustrating the issue in realtime. I left the TaskManager in frame in case it reveals something.
The steps:
. I load a simple scene (GreasePencil in my case).
. I go back and forth in the Timeline. It's smooth.
. I switch to Render Viewport..
. Just before fiddling around in the Timeline again I opened the Preference Window and moved it around. Just to show that the whole Blender interface is still smooth.
. I then went back and forth in the Timeline. Slowdown appears. The playhead no longer sticks to the mouse/pen movement.
. Opening the Preference Window and moving it around shows stutter and no longer is smooth.
Could this be a memory leak of sorts? A driver issue? Or is it because these Intel cards don't have any VRAM and start using er, something else (I have 16G of Ram and a lot of disk space)?
Either way it'd be great to find a solution for this. Being able to work on the go (with the Surface Pro in my case) is pretty awesome...
Thanks for any helpful hints or insights!

Piotr

My Movie 1-720p30.mp4

PS I'm on a SP8 WIN11 latest Intel Drivers.

surface pro 8 win10 1135g7 has same problem, IntelDrivers:27.20.100.9624

> In #86778#1270942, @Pyer wrote: > Hello! > Here is a video illustrating the issue in realtime. I left the TaskManager in frame in case it reveals something. > The steps: > . I load a simple scene (GreasePencil in my case). > . I go back and forth in the Timeline. It's smooth. > . I switch to Render Viewport.. > . Just before fiddling around in the Timeline again I opened the Preference Window and moved it around. Just to show that the whole Blender interface is still smooth. > . I then went back and forth in the Timeline. Slowdown appears. The playhead no longer sticks to the mouse/pen movement. > . Opening the Preference Window and moving it around shows stutter and no longer is smooth. > Could this be a memory leak of sorts? A driver issue? Or is it because these Intel cards don't have any VRAM and start using er, something else (I have 16G of Ram and a lot of disk space)? > Either way it'd be great to find a solution for this. Being able to work on the go (with the Surface Pro in my case) is pretty awesome... > Thanks for any helpful hints or insights! > > Piotr > > [My Movie 1-720p30.mp4](https://archive.blender.org/developer/F12733544/My_Movie_1-720p30.mp4) > > PS I'm on a SP8 WIN11 latest Intel Drivers. surface pro 8 win10 1135g7 has same problem, IntelDrivers:27.20.100.9624

橙月 commented

2022-02-20 21:43:02 +01:00

I updated my intel xe graphics driver to 30.0.101.1340 and solved this problem in blender v2.8.3 /blender v3.0
( ﾟ∀ ﾟ)

@Pyer

I updated my intel xe graphics driver to 30.0.101.1340 and solved this problem in blender v2.8.3 /blender v3.0 ( ﾟ∀ ﾟ) @Pyer

Carl Henderson commented

2022-02-20 21:47:09 +01:00

I have just tried again with the latest Intel Driver located here: https://www.intel.com/content/www/us/en/download/19344/intel-graphics-windows-dch-drivers.html version 30.0.101.1340 with latest Blender 3.0.1 and the lagging issue IS resolved.

Richard Antalik commented

2022-03-01 02:35:58 +01:00

Added subscriber: @Lucax2

Richard Antalik commented

2022-03-18 00:49:45 +01:00

Added subscriber: @EB-4

Pratik Borhade commented

2022-04-04 05:45:05 +02:00

Added subscribers: @SpiderKinze, @lichtwerk

Campbell Barton commented

2022-04-19 02:22:18 +02:00

Added subscriber: @ideasman42

Campbell Barton commented

2022-04-19 02:22:18 +02:00

@tommyoliversays can you confirm that updating the driver resolves the problem?

Stay_Here commented

2022-04-19 02:29:44 +02:00

Removed subscriber: @Stay_Here

Pratik Borhade commented

2022-04-28 03:30:46 +02:00

Added subscriber: @Ableseth

Pratik Borhade commented

2022-05-02 20:42:50 +02:00

Added subscriber: @Blubvis725

Pratik Borhade commented

2022-05-09 08:37:31 +02:00

Added subscriber: @Animatical

Jeroen Bakker commented

2022-05-09 14:44:06 +02:00

I am in favor of closing this issue as it seems to be fixed by Intel. The newer reports don't have the information to point out that they use the latest intel driver (from the intel website). I will lower the priority of the issue until we decided to close it.

Jeroen Bakker commented

2022-05-09 15:00:43 +02:00

As discussed with the triaging team. We keep this issue open as there are still a lot of users that have this issue. Users aren't always allowed to update to the latest intel driver due to security or vendor rulings.

Setting it to known issue as it isn't a blender issue.

As discussed with the triaging team. We keep this issue open as there are still a lot of users that have this issue. Users aren't always allowed to update to the latest intel driver due to security or vendor rulings. Setting it to known issue as it isn't a blender issue.

Animatical commented

2022-05-09 18:59:05 +02:00

This comment was removed by @Animatical

*This comment was removed by @Animatical*

Omar Emara commented

2022-05-23 11:25:33 +02:00

Added subscriber: @REDx3

Philipp Oeser removed the

Interest

EEVEE & Viewport

label 2023-02-09 15:13:56 +01:00

Pratik Borhade referenced this issue