Bug 109233 - [Wine / Vulkan] Doom 2016 Hangs on Main Menu
Summary: [Wine / Vulkan] Doom 2016 Hangs on Main Menu
Status: NEW
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Vulkan/intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-06 18:49 UTC by Benjamin Hodgetts
Modified: 2019-01-08 12:28 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Benjamin Hodgetts 2019-01-06 18:49:54 UTC
The game seems to start up fine, the splash screens and videos are displayed, but semi-hangs when it reaches the main menu. The music is still playing but the screen remains black and the styled cursor doesn't move from the top left corner.

The program can still be killed cleanly and there's no errors printed on the command line or any kernel errors either.

Not sure what else to provide here given the lack of errors presented anywhere.

GPU: Intel Iris Plus 655
Wine: 4.0-rc5 ( Staging Esync )
Mesa: Mesa 19.0.0-devel (git-8847370424, also tested on Mesa 18.3.1)
Kernel: 4.20.0-arch1-1-ARCH
Comment 1 Denis 2019-01-08 09:22:21 UTC
Hi Benjamin, fast question - you are running Doom thru the Steam Play or manually installed wine+dxvk?

I think that second combination. If so, could you please run (if you have possibility, for sure) thru the Steam Play? (using their proton?) Just for comparison of the results.
Comment 2 Benjamin Hodgetts 2019-01-08 10:12:10 UTC
I'm running via a normal install of Wine with DXVK installed.

I can try SteamPlay but it'll take me a few days to download the game again through Steam due to its size and my rubbish internet connection (I'm currently using an install copied over from one of my other machines which I don't think Steam will recognise).
Comment 3 Denis 2019-01-08 12:28:36 UTC
Actually, proton simply has lower wine version, current proton (4.16 beta) has wine-3.16. So relevant check will be to check this wine version also I think. Unfortunately I don't have exactly the same gpu, so can check only on nearest UHD630 and HD620


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.