We send this issue to Intel to come with direction. They are aware of this request and we are waiting for their We did some indept performance checks and the viewport isn't lacking it is the rendering of the properties panel. The most cost effective and quickest solution is that Intel would solve this issue in their driver. Which might be redone when moving to vulkan. 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). You can test that yourself when you switch to the render tab in the property panel. It seems that the Intel driver is not performing well when creating many of these calls. This part of blender uses a wrapper to convert legacy OpenGL calls to core profile calls. The bottleneck is in the property panel and font drawing. And gets updated when moving the active object in the 3d viewport. We send this issue to Intel to come with direction.īy default the object panel is open. [Blender We did some indept performance checks and the viewport isn't lacking it is the rendering of the properties panel. **Exact steps for others to reproduce the error** 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: !() The Problem gets a little less worse when going into render view once, it stays that way when moving back, though still not usable. Video of the Problem: Blender 12-07-26.mp4īroken: version: 2.82 (sub 1), branch: master, commit date: 22:10, hash: `e83a23acb2` 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. 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:Įxact steps for others to reproduce the error I'm suspecting the Iris graphics, as that is a similarity with some of the macs that reportedly had this problem. 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 could only find references to this behavior happening on Macs (the behavior is similar to ). Last edited by david3252 February 27th, 2023 at 09:41 PM.Graphics card: Intel(R) Iris(R) Plus Graphics Intel 4.5.0 - Build 25.20.100.7101ĭrivers 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.īroken: version: 2.82 (sub 1), branch: master, commit date: 22:10, hash: e83a23acb2Įvery other version of 2.8 I tried is also not working.īlender 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. TRM: 18027 18039 18034 18040 18039 18038 18027 18032 Thermal event interruptsWhat deal with Thermal event interrupts ?Įdit : it is the same with the Ubuntu 22.04 LTS Live USB Boot RTR: 0 0 0 0 0 0 0 0 APIC ICR read retries PMI: 4 6 6 4 1 1 4 3 Performance monitoring interrupts NMI: 4 6 6 4 1 1 4 3 Non-maskable interrupts I7-1260P with Integrated Iris Graphics (Mesa Intel® Graphics (ADL GT2)) Jan 18 11:03:19 usernamelaptop gsd-media-keys: : GFX: RenderThread detected a device reset in PostUpdate Jan 18 11:03:19 usernamelaptop kernel: i915 0000:00:02.0: Resetting chip for stopped heartbeat on rcs0 Jan 18 11:03:15 usernamelaptop kernel: Asynchronous wait on fence 0000:00:02.0:gnome-shell:2f8d4 timed out (hint:intel_atomic_commit_ready )
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |