Same here. I am just going to wait until they fix it in 5.8.1 I’ll keep using 5.6
5.8.1 still here
Been battling this issue for a few days now on my laptop. And I’ve found an alternative fix for those that might come across this. For full context, my laptop details:
CPU: 10875H (with iGPU)
dGPU: 2070S (driver 610 currently, but 595 presented exact same issues)
OS: Debian stable
DE: KDE Plasma (Wayland)
For battery longevity, I initially set up my laptop to primarily use the iGPU instead of my dGPU. As such, it is also the primary compositor for my desktop environment. This ended up being the thing that caused issues. Setting the envvar KWIN_DRM_DEVICES=/dev/dri/card1:/dev/dri/card0 (with card1 being my dGPU and card0 being my iGPU) in a file ~/.config/plasma-workspace/env/10-prefer-dgpu.sh fixed it for me. From my understanding this forces my dGPU to be the primary compositor for the entire desktop session. And this config change came coupled with Unreal being noticeably snappier and more stable.
Crucially, the crashes presented themselves identically as VK_ERROR_DEVICE_LOST, but might be caused by a different link in the chain. I have left the r.Vulkan.EnablePipelineLRUCache=1 applied from earlier testing, but left out the WaitForIdleOnSubmit, as this would yield a frozen editor. I don’t know if these are needed after performing the switch of primary compositor GPU.