Summary: | Doom 2016 - Rendering issues | ||
---|---|---|---|
Product: | Mesa | Reporter: | Ahmed Elsayed <ahmed.com> |
Component: | Drivers/Gallium/radeonsi | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED NOTOURBUG | QA Contact: | Default DRI bug account <dri-devel> |
Severity: | normal | ||
Priority: | medium | CC: | airlied, chadversary, daniel |
Version: | 18.2 | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Ahmed Elsayed
2018-09-09 13:47:09 UTC
System information: Operating system: Manjaro KDE (the latest version). GPU: AMD HD 8750M Driver: 18.2.0-1 Wine version: 3.15 staging So just to check, you enabled Vulkan instead of GL rendering? Doom is using GL by default. I tried both OpenGL and Vulkan and same gave me the same behavior. I am trying to compile Mesa 18.3 for the third time because it failed in the last 2 times. I hope it will be built without errors this time. I tried also Mesa 18.3 and I have the same problem. Ok I think this is a regression with wine staging. First of all I can confirm this is not a RADV bug setting +r_renderapi 1 in launch options for steam launches the Vulkan path and its working fine. As for the GL path it is using EXT_direct_state_access even though he don't advertise it. This seems to be a regression in wine staging and I've seen the same issue with Wolfenstein: The Old Blood recently. I'm moving this bug to radeonsi for now but I'm tempted to close as not our bug. I can start the game with Vulkan but it stops loading at 99%, but with opengl, I can hear the menu sounds but I can see only the red fog. I filed a bug in Wine but no one answered me. https://bugs.winehq.org/show_bug.cgi?id=45826 (In reply to Timothy Arceri from comment #5) > Ok I think this is a regression with wine staging. First of all I can > confirm this is not a RADV bug setting +r_renderapi 1 in launch options for > steam launches the Vulkan path and its working fine. > > As for the GL path it is using EXT_direct_state_access even though he don't > advertise it. This seems to be a regression in wine staging and I've seen > the same issue with Wolfenstein: The Old Blood recently. > > I'm moving this bug to radeonsi for now but I'm tempted to close as not our > bug. Do you mean that this is a bug present in Staging but not in upstream Wine? In particular, is the patchset "opengl32-Revert_Disable_Ext" to blame? (In reply to Zebediah Figura from comment #7) > Do you mean that this is a bug present in Staging but not in upstream Wine? > In particular, is the patchset "opengl32-Revert_Disable_Ext" to blame? I'm not sure I use Fedora which uses wine staging by default, but I do know this is a recent regression. (In reply to Zebediah Figura from comment #7) > Do you mean that this is a bug present in Staging but not in upstream Wine? > In particular, is the patchset "opengl32-Revert_Disable_Ext" to blame? Ok so it seems someone has confirmed this patch is the problem in the wine bug, so I'm going to close this bug. (In reply to Ahmed Elsayed from comment #6) > I can start the game with Vulkan but it stops loading at 99%, but with > opengl, I can hear the menu sounds but I can see only the red fog. > > I filed a bug in Wine but no one answered me. > > https://bugs.winehq.org/show_bug.cgi?id=45826 Using the normal wine instead of wine-staging solved this issue, and the game is working fine with opengl. Thanks for your help. (In reply to Timothy Arceri from comment #9) > (In reply to Zebediah Figura from comment #7) > > Do you mean that this is a bug present in Staging but not in upstream Wine? > > In particular, is the patchset "opengl32-Revert_Disable_Ext" to blame? > > Ok so it seems someone has confirmed this patch is the problem in the wine > bug, so I'm going to close this bug. It was wine bug. Sorry for posting here. And thanks for your patient. |
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.