[Bug 45826] New: Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

Bug ID: 45826
           Summary: Doom 2016 - Rendering issues
           Product: Wine-staging
           Version: 3.15
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
                CC: [e-mail], [e-mail]
      Distribution: ---

Created attachment 62283
  --> https://bugs.winehq.org/attachment.cgi?id=62283
wine error log

I can't run Doom 2016 with Mesa 18.1.7 or Mesa 18.1.8, so I tried Mesa 18.2.0-1
and the game started but it look so weird, and I can hear the menu sounds but I
can't see the menu.

System information:

Operating system: Manjaro KDE
GPU: AMD HD 8750M
Driver: Mesa 18.2.0-1
Wine version: 3.15 staging-nine

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

--- Comment #1 from [e-mail] ---
Created attachment 62284
  --> https://bugs.winehq.org/attachment.cgi?id=62284
That is how the game look at the intro

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

--- Comment #2 from [e-mail] ---
Created attachment 62285
  --> https://bugs.winehq.org/attachment.cgi?id=62285
That is how the game look when loading

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #62284|That is how the game look   |That is how the game look
        description|at the intro                |in the intro

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

--- Comment #3 from [e-mail] ---
Created attachment 62286
  --> https://bugs.winehq.org/attachment.cgi?id=62286
That is how the game look in the menu

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

--- Comment #4 from [e-mail] ---
One more thing, starting the game with Vulkan doesn't work at all, and starting
the game with Opengl end up with rendering issues.

And I can play any other game that use Vulkan without any problem.

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
       Distribution|---                         |ArchLinux

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

--- Comment #5 from [e-mail] ---
I filed a bug at Mesa but someone there say that it is a wine bug. That is why
I filed the bug here.

Link for the bug at Mesa:

https://bugs.freedesktop.org/show_bug.cgi?id=107873

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #6 from [e-mail] ---
vulkan works fine here. opengl is a shit show.

you're probably missing the icd loader for vulkan or the vulkan portion of mesa
drivers, that would cause it not to run:

https://wiki.archlinux.org/index.php/Vulkan#Installation

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

--- Comment #7 from [e-mail] ---
Vulkan is installed and running with other games just fine, but this game
doesn't work with vulkan or opengl. It was working before the new wine and
drivers updates, and now I can't run it at all.

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

--- Comment #8 from [e-mail] ---
Just tested both OpenGL and Vulkan on vanilla wine, both worked fine here.
Staging OpenGL has rendering issues. Currently digging to see what patchset
causes it.

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

--- Comment #9 from [e-mail] ---
(In reply to ahmed.com from comment #7)
> Vulkan is installed and running with other games just fine, but this game
> doesn't work with vulkan or opengl. It was working before the new wine and
> drivers updates, and now I can't run it at all.

Have you tested any other native vulkan games in wine? (not dxvk)

dxvk auto-detects if there is a dedicated/discrete gpu and uses it first.

Vulkan by itself uses the first available vulkan gpu it detects.

what is the output of:

vulkaninfo | grep "GPU id"

(you may need to install vulkan-tools)

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

--- Comment #10 from [e-mail] ---
staging OpenGL works if you remove opengl32-Revert_Disable_Ext patchset.

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

--- Comment #11 from [e-mail] ---
(In reply to GloriousEggroll from comment #9)
> (In reply to ahmed.com from comment #7)
> > Vulkan is installed and running with other games just fine, but this game
> > doesn't work with vulkan or opengl. It was working before the new wine and
> > drivers updates, and now I can't run it at all.
>
> Have you tested any other native vulkan games in wine? (not dxvk)
>
> dxvk auto-detects if there is a dedicated/discrete gpu and uses it first.
>
> Vulkan by itself uses the first available vulkan gpu it detects.
>
> what is the output of:
>
> vulkaninfo | grep "GPU id"
>
> (you may need to install vulkan-tools)

I play Rise of the Tomb Raider (Native) which run without any problems.

the result of vulkaninfo | grep "GPU id" :

ERROR: [Loader Message] Code 0 : /usr/lib32/libvulkan_radeon.so: wrong ELF
class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib32/libvulkan_intel.so: wrong ELF
class: ELFCLASS32
WARNING: radv is not a conformant vulkan implementation, testing use only.
INTEL-MESA: warning: Haswell Vulkan support is incomplete
INTEL-MESA: warning: ../mesa-18.2.0/src/intel/vulkan/anv_device.c:1142:
FINISHME: Implement pop-free point clipping
                GPU id       : 0 (AMD RADV OLAND (LLVM 6.0.1))
                GPU id       : 1 (Intel(R) Haswell Mobile)
                GPU id       : 0 (AMD RADV OLAND (LLVM 6.0.1))
                GPU id       : 1 (Intel(R) Haswell Mobile)
                GPU id       : 0 (AMD RADV OLAND (LLVM 6.0.1))
                GPU id       : 1 (Intel(R) Haswell Mobile)
GPU id       : 0 (AMD RADV OLAND (LLVM 6.0.1))
GPU id       : 1 (Intel(R) Haswell Mobile)

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

--- Comment #12 from [e-mail] ---
I meant have you tried any vulkan games that run in WINE besides doom?
(Wolfenstein 2 if you have it). Ferals native ports let you choose which gpu so
that's not so helpful in this case.

Is there any way you can disable the intel igpu in the bios and try that way?

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

--- Comment #13 from [e-mail] ---
just note: you may need to plug in a monitor if you disable the igpu. if you're
not comfortable with it, don't do it

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

--- Comment #14 from [e-mail] ---
(In reply to GloriousEggroll from comment #13)
> just note: you may need to plug in a monitor if you disable the igpu. if
> you're not comfortable with it, don't do it

(In reply to GloriousEggroll from comment #12)
> I meant have you tried any vulkan games that run in WINE besides doom?
> (Wolfenstein 2 if you have it). Ferals native ports let you choose which gpu
> so that's not so helpful in this case.
>
> Is there any way you can disable the intel igpu in the bios and try that way?

I can disable only the dgpu from the bios which doesn't help at my case.

I reported a bug at mesa, and someone mentioned that the patchset
"opengl32-Revert_Disable_Ext" is to blame, and I don't know what he is talking
about.

Here is the link >>> https://bugs.freedesktop.org/show_bug.cgi?id=107873

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

--- Comment #15 from [e-mail] ---
I am sorry! You mentioned the same thing in a previous post, but I don't know
how to remove opengl32-Revert_Disable_Ext patchset.

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

--- Comment #16 from [e-mail] ---
(In reply to ahmed.com from comment #15)
> I am sorry! You mentioned the same thing in a previous post, but I don't
> know how to remove opengl32-Revert_Disable_Ext patchset.

it is a wine-staging patchset. if you use normal wine (not staging) the game
works with opengl.

if you disable the dedicated gpu do you still get the same error when trying to
run the game with vulkan?

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

--- Comment #17 from [e-mail] ---
(In reply to GloriousEggroll from comment #16)
> (In reply to ahmed.com from comment #15)
> > I am sorry! You mentioned the same thing in a previous post, but I don't
> > know how to remove opengl32-Revert_Disable_Ext patchset.
>
> it is a wine-staging patchset. if you use normal wine (not staging) the game
> works with opengl.
>
> if you disable the dedicated gpu do you still get the same error when trying
> to run the game with vulkan?

Also, have you tried waiting out the 99% load in vulkan?

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

--- Comment #18 from [e-mail] ---
I waited for a half hour before I closed it.

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

--- Comment #19 from [e-mail] ---
(In reply to GloriousEggroll from comment #17)
> (In reply to GloriousEggroll from comment #16)
> > (In reply to ahmed.com from comment #15)
> > > I am sorry! You mentioned the same thing in a previous post, but I don't
> > > know how to remove opengl32-Revert_Disable_Ext patchset.
> >
> > it is a wine-staging patchset. if you use normal wine (not staging) the game
> > works with opengl.
> >
> > if you disable the dedicated gpu do you still get the same error when trying
> > to run the game with vulkan?
>
> Also, have you tried waiting out the 99% load in vulkan?

I will try that.

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

--- Comment #20 from [e-mail] ---
(In reply to GloriousEggroll from comment #17)
> (In reply to GloriousEggroll from comment #16)
> > (In reply to ahmed.com from comment #15)
> > > I am sorry! You mentioned the same thing in a previous post, but I don't
> > > know how to remove opengl32-Revert_Disable_Ext patchset.
> >
> > it is a wine-staging patchset. if you use normal wine (not staging) the game
> > works with opengl.
> >
> > if you disable the dedicated gpu do you still get the same error when trying
> > to run the game with vulkan?
>
> Also, have you tried waiting out the 99% load in vulkan?

Using the normal wine solved everything. Thanks for helping me.

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

--- Comment #21 from [e-mail] ---
did normal wine work with vulkan? (it should)

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

--- Comment #22 from [e-mail] ---
No it doesn't, and I am now sure that it uses my AMD card with Vulkan, because
I enabled performance metrics and switched to Vulkan and it showed the name of
my AMD card before it stopped at 99% as before.

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

Robert Walker  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #23 from [e-mail] ---
The game running smoothly with Wine-stable 3.15. Thanks for your support. I
changed to resolved.

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

Mathew Hodson  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #24 from Mathew Hodson  ---
This should be fixed in Wine Staging 3.17 with this commit:
https://github.com/wine-staging/wine-staging/commit/bd3794c11e682e8489959ff7...

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

Mathew Hodson  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|[e-mail]     |

[Bug 45826] Doom 2016 - Rendering issues

https://bugs.winehq.org/show_bug.cgi?id=45826

Alistair Leslie-Hughes  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #25 from Alistair Leslie-Hughes  ---
Closing Fixed Staging bugs.