Display freezing and very bad performance with Blender's experimental Eevee-next

[a-One-Fan]

Checklist [README]

• [X] Device is not undervolted nor overclocked
• [X] Device is using the latest drivers
• [X] Application is not cracked, modded and use the latest patch

Application [Required]

Blender 4.0 8ea68765fcac

Processor / Processor Number [Required]

Ryzen 7 3700x

Graphic Card [Required]

Arc A770 LE 16GB

GPU Driver Version [Required]

• [X] 31.0.101.4578
• [ ] 31.0.101.4577
• [ ] 31.0.101.4576
• [ ] 31.0.101.4575
• [ ] 31.0.101.4514
• [ ] 31.0.101.4502
• [ ] 31.0.101.4499
• [ ] 31.0.101.4382
• [ ] 31.0.101.4369
• [ ] 31.0.101.4335
• [ ] 31.0.101.4314
• [ ] 31.0.101.4311
• [ ] 31.0.101.4257
• [ ] 31.0.101.4255
• [ ] 31.0.101.4148
• [ ] 31.0.101.4146
• [ ] 31.0.101.4125
• [ ] 31.0.101.4123
• [ ] 31.0.101.4091
• [ ] 31.0.101.4090
• [ ] 31.0.101.4034

Rendering API [Required]

• [X] Vulkan
• [ ] OpenGL
• [ ] DirectX12
• [ ] DirectX11
• [ ] DirectX10
• [ ] DirectX9
• [ ] Not applicable

Windows Build Number [Required]

• [X] Windows 11 22H2
• [ ] Windows 11 21H2
• [ ] Windows 10 22H2
• [ ] Windows 10 21H2
• [ ] Other (Please specify)

Other Windows build number

No response

Intel System Support Utility report

igcit_ssu_4578.txt

Description and steps to reproduce [Required]

Grab today's 4.0 build (8ea68765fcac), or just any recent 4.0 build really.

Enable developer extras (Edit > preferences > interface > display > developer extras) Enable Eevee-next from the now visible experimental settings (Edit > preferences > experimental > prototypes > Eevee-next) Before switching to Eevee-next, you may want to switch to Eevee and reduce the viewport samples to 1 or 2 in order to not make your PC near unusable for very long. Switch to the Eevee-next renderer in the render properties. Switch to rendered shading or material preview shading. Everything except the cursor will freeze every ~2 seconds, sometimes everything will freeze including the cursor. If you set your samples low, after about a minute the freezing should stop. You can pan around the viewport to get it to freeze again.

While Eevee-next is experimental, I've seen AMD have been fixing their driver bugs with it, and it's better to report this issue 12 months before it releases than 12 hours after. I have not had this issue with my RX 480.

Device / Platform

No response

Crash dumps [Required, if applicable]

No response

Application / Windows logs

No response

[a-One-Fan]

Issue no longer happens with 4.1 / newer drivers, closed.