Hi. I think that it is good to create a new issue so we will have possibility to track improvements on this. I linked the original ticket, also below link to the renderdoc trace which reproduces issue: https://drive.google.com/open?id=14RkKwuJRZuUgDGzSUH0qsB2hzpU-i7zW So as soon as Jason and dxvk dev provides fixes, I will be able to test them within this bug.
With Steam Play 3.16-5 Beta with DXVK 0.93, the menu performance is pretty similar as with that Mesa branch tested before: around 20 FPS in videos and menus but it has some bugs it hadn't before. The main menu keeps resetting: it loads correctly but then the screen become black, it loads again and the cycle at infinitum. It is possible to navigate on it, but it is pretty strange. I don't observe this using Steam Play 3.16-4 (but observe bad performance). Unfortunately, the main game is still an absolute disgrace running at 1 FPS.
Created attachment 142816 [details] Video showing the problem
(In reply to leozinho29_eu from comment #1) > With Steam Play 3.16-5 Beta with DXVK 0.93, the menu performance is pretty > similar as with that Mesa branch tested before: around 20 FPS in videos and > menus but it has some bugs it hadn't before. > > The main menu keeps resetting: it loads correctly but then the screen become > black, it loads again and the cycle at infinitum. It is possible to navigate > on it, but it is pretty strange. I don't observe this using Steam Play > 3.16-4 (but observe bad performance). Unfortunately, the main game is still > an absolute disgrace running at 1 FPS. We can definitely look into the 1FPS issue, but for the infinite loading loop, I think you should file a bug against Proton : https://github.com/ValveSoftware/Proton
I have upgraded Mesa to 19.0.0-devel (git-c6b37e5412) and Vulkan to 1.1.96 and I noticed constant messages on Steam logs: INTEL-MESA: error: vulkan/anv_descriptor_set.c:530: VK_ERROR_OUT_OF_POOL_MEMORY Around every 5 seconds this message appears. I did not notice performance changes on this game, but on DiRT 3 Complete Edition it started slower and with significant stutter (cache being built?), but then became better than the previous experiences. About the menu issue, it was really a Proton regression.
Closing, the menu issue was coming from Proton.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.