https://bugs.winehq.org/show_bug.cgi?id=45451
Bug ID: 45451 Summary: Doom 2016 Freezing and Crashing in background Product: Wine Version: 3.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winevulkan Assignee: wine-bugs@winehq.org Reporter: linards.liepins@gmail.com Distribution: ---
Created attachment 61784 --> https://bugs.winehq.org/attachment.cgi?id=61784 winetricks installed module list
After I enabled Vulkan via enabling it in kernel cmdline (radeon.cik_support=0 amdgpu.cik_support=1), was able to launch the game. Once all intro cinematics was finished, the game loading bar was showing up, but it stopped at 99%. See following link for similar reports:
I tried several options suggested there and none of them appears to be fixing the issue.
I have created all possible graphics (& vulkan) related logs about my system and attached in this bug.
Also attached game crash log, created by Id Engine.
I also attached winetricks installed module list.
https://bugs.winehq.org/show_bug.cgi?id=45451
--- Comment #1 from Linards linards.liepins@gmail.com --- Created attachment 61785 --> https://bugs.winehq.org/attachment.cgi?id=61785 terminal log
https://bugs.winehq.org/show_bug.cgi?id=45451
--- Comment #2 from Linards linards.liepins@gmail.com --- Created attachment 61786 --> https://bugs.winehq.org/attachment.cgi?id=61786 vulkaninfo log
https://bugs.winehq.org/show_bug.cgi?id=45451
--- Comment #3 from Linards linards.liepins@gmail.com --- Created attachment 61787 --> https://bugs.winehq.org/attachment.cgi?id=61787 OpenCL log
https://bugs.winehq.org/show_bug.cgi?id=45451
--- Comment #4 from Linards linards.liepins@gmail.com --- Created attachment 61788 --> https://bugs.winehq.org/attachment.cgi?id=61788 GLXInfo log
https://bugs.winehq.org/show_bug.cgi?id=45451
--- Comment #5 from Linards linards.liepins@gmail.com --- Link about used kernel cmdline switches to enable AMDGPU driver, supporting Vulkan:
https://bugs.freedesktop.org/show_bug.cgi?id=105068
https://bugs.winehq.org/show_bug.cgi?id=45451
--- Comment #6 from Linards linards.liepins@gmail.com --- Created attachment 61789 --> https://bugs.winehq.org/attachment.cgi?id=61789 ID Crash Log
https://bugs.winehq.org/show_bug.cgi?id=45451
--- Comment #7 from Linards linards.liepins@gmail.com --- Link about other people having same 99% freeze:
https://steamcommunity.com/app/379720/discussions/0/351660338709794024/
https://bugs.winehq.org/show_bug.cgi?id=45451
Robert Walker bob.mt.wya@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bob.mt.wya@gmail.com
--- Comment #8 from Robert Walker bob.mt.wya@gmail.com --- This is not a standard path for a Steam library game:
/home/linards/.wine/drive_c/Program Files (x86)/Doom/Doomx64vk.exe
Is this really the legit Steam version of DOOM 2016 - or some cracked version?
You should be starting Wine applications with:
wine start /unix "/home/linards/.wine/drive_c/Program Files (x86)/Doom/Doomx64vk.exe"
or
cd "/home/linards/.wine/drive_c/Program Files (x86)/Doom/" wine "Doomx64vk.exe"
Not all Windows applications will correctly determine the PATH for their binary (which includes the PWD). See: https://wiki.winehq.org/Wine_User%27s_Guide#Using_Wine
https://bugs.winehq.org/show_bug.cgi?id=45451
--- Comment #9 from Robert Walker bob.mt.wya@gmail.com --- Also you'd want to attach a terminal log with:
export WINEDEBUG=+timestamp,+tid,+wgl,+opengl
Because the problem may be related to:
Max core profile version: 4.5 Max compat profile version: 3.0
The Doom Vulkan renderer - still requires full OpenGL 4.5 (??) support just to start - before it switches to the Vulkan renderer (even running the vulkan renderer directly).
See (for example): https://www.gamingonlinux.com/forum/topic/2854?page=1
https://bugs.winehq.org/show_bug.cgi?id=45451
zzzzzyzz@hacari.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |zzzzzyzz@hacari.org
https://bugs.winehq.org/show_bug.cgi?id=45451
--- Comment #10 from Linards linards.liepins@gmail.com --- (In reply to Robert Walker from comment #9)
Also you'd want to attach a terminal log with:
export WINEDEBUG=+timestamp,+tid,+wgl,+opengl
Because the problem may be related to:
Max core profile version: 4.5 Max compat profile version: 3.0
The Doom Vulkan renderer - still requires full OpenGL 4.5 (??) support just to start - before it switches to the Vulkan renderer (even running the vulkan renderer directly).
See (for example): https://www.gamingonlinux.com/forum/topic/2854?page=1
Sorry for a very long delay on reply.
Last time I checked I had identical output information with and without your offered switches.
Now, when I test with wine-3.15-staging, I cannot even run game anymore as it crashes with error message: 'Internal error 0x06: System error!'
See log: https://pastebin.com/m6RcienD
https://bugs.winehq.org/show_bug.cgi?id=45451
--- Comment #11 from Robert Walker bob.mt.wya@gmail.com --- (In reply to Linards from comment #10)
Sorry for a very long delay on reply.
Last time I checked I had identical output information with and without your offered switches.
Now, when I test with wine-3.15-staging, I cannot even run game anymore as it crashes with error message: 'Internal error 0x06: System error!'
See log: https://pastebin.com/m6RcienD
Please attach logs to this bug report. Don't post them on external sites (especially pastebin - which has a dodgy reputation!)
Please stay on topic to this bug report! I know it's annoying - but if you want end-user support that's what the WineHQ forums are for... https://forum.winehq.org/viewforum.php?f=8
To ensure your wine vulkan layer is working... Use:
winetricks vulkansdk
and run _BOTH_ the 32-bit and 64-bit (included) Vulkan cube demos.
Bin32/cube.exe Bin/cube.exe
Also checkout the native vulkaninfo executables are happy(ish):
RunTimeInstaller/x86/vulkaninfo.exe RunTimeInstaller/x64/vulkaninfo.exe
The print some garbage at the start, on my system (basically because the SDK isn't installed to my dxvk WINEPREFIX). But they'll confirm that wine-vulkan is choosing the correct Vulkan render device (e.g. AMD amdgpu and not Intel).
https://bugs.winehq.org/show_bug.cgi?id=45451
--- Comment #12 from Linards linards.liepins@gmail.com --- (In reply to Robert Walker from comment #11)
(In reply to Linards from comment #10)
Sorry for a very long delay on reply.
Last time I checked I had identical output information with and without your offered switches.
Now, when I test with wine-3.15-staging, I cannot even run game anymore as it crashes with error message: 'Internal error 0x06: System error!'
See log: https://pastebin.com/m6RcienD
Please attach logs to this bug report. Don't post them on external sites (especially pastebin - which has a dodgy reputation!)
Please stay on topic to this bug report! I know it's annoying - but if you want end-user support that's what the WineHQ forums are for... https://forum.winehq.org/viewforum.php?f=8
To ensure your wine vulkan layer is working... Use:
winetricks vulkansdk
and run _BOTH_ the 32-bit and 64-bit (included) Vulkan cube demos.
Bin32/cube.exe Bin/cube.exe
Also checkout the native vulkaninfo executables are happy(ish):
RunTimeInstaller/x86/vulkaninfo.exe RunTimeInstaller/x64/vulkaninfo.exe
The print some garbage at the start, on my system (basically because the SDK isn't installed to my dxvk WINEPREFIX). But they'll confirm that wine-vulkan is choosing the correct Vulkan render device (e.g. AMD amdgpu and not Intel).
Just checked and all LunarG Vulkan components works as expected.
https://bugs.winehq.org/show_bug.cgi?id=45451
--- Comment #13 from Robert Walker bob.mt.wya@gmail.com --- @Linards,
You might also want to check out this bug report: https://bugs.winehq.org/show_bug.cgi?id=45826
https://bugs.winehq.org/show_bug.cgi?id=45451
Linards linards.liepins@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NOTOURBUG Status|UNCONFIRMED |RESOLVED
--- Comment #14 from Linards linards.liepins@gmail.com --- After Upgrade from Fedora 28 to Fedora 29 issue was fixed and I was able to play the game with very low FPS on my radeon hd7790 with radeon driver; nop jet tried with vulkan.
I assume the issue was with very old Mesa (18.0.x branch) and its bugs.
https://bugs.winehq.org/show_bug.cgi?id=45451
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|winevulkan |-unknown Status|RESOLVED |CLOSED
--- Comment #15 from Matteo Bruni matteo.mystral@gmail.com --- (In reply to Linards from comment #14)
After Upgrade from Fedora 28 to Fedora 29 issue was fixed and I was able to play the game with very low FPS on my radeon hd7790 with radeon driver; nop jet tried with vulkan.
I assume the issue was with very old Mesa (18.0.x branch) and its bugs.
Reported fixed upstream.