[Bug 44681] New: Outcast Second Contact: Black screen

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

Bug ID: 44681
           Summary: Outcast Second Contact: Black screen
           Product: Wine
           Version: 3.3
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Created attachment 60690
  --> https://bugs.winehq.org/attachment.cgi?id=60690
debug log in dx11

The game Outcast: Second Contact (from GOG) starts and runs but only shows a
black screen.
> From the logs

0033:fixme:d3d:wined3d_device_resolve_sub_resource Unhandled multisample
resolve, dst_format WINED3DFMT_R8G8B8A8_TYPELESS, src_format
WINED3DFMT_R8G8B8A8_TYPELESS, format WINED3DFMT_R8G8B8A8_UNORM.
0032:err:d3d:wined3d_debug_callback 0x77f1480: "GL_INVALID_ENUM in
glTexSubImage2D(target=GL_TEXTURE_2D_MULTISAMPLE)".

I'm guessing this is bug #39754 but filing a new one just to be sure.

I also tried forcing the game to start in d3d9 mode by disabling the d3d11 dll.
I have no idea if it works for this title, but is supported in some other Unity
games. The behavior is similar, but the game shows a pink screen and logs:

0032:err:d3d:wined3d_debug_callback 0xd8810: "GL_INVALID_ENUM in
glTexSubImage2D(target=GL_TEXTURE_2D_MULTISAMPLE)".

Attaching logs from dx11 and dx9 runs.

[Bug 44681] Outcast Second Contact: Black screen

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

--- Comment #1 from Sven Arvidsson  ---
Created attachment 60691
  --> https://bugs.winehq.org/attachment.cgi?id=60691
debug log in dx9

[Bug 44681] Outcast Second Contact: Black screen

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

Sven Arvidsson  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Hardware|x86                         |x86-64

[Bug 44681] Outcast Second Contact: pink screen (Direct3D9)

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

Józef Kucia  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|-unknown                    |directx-d3d
            Summary|Outcast Second Contact:     |Outcast Second Contact:
                   |Black screen                |pink screen (Direct3D9)
                 CC|                            |[e-mail]

--- Comment #2 from Józef Kucia  ---
(In reply to Sven Arvidsson from comment #0)
> I'm guessing this is bug #39754 but filing a new one just to be sure.

Yes, it's the same issue. Let's make this bug about Direct3D9.

[Bug 44681] Outcast Second Contact: pink screen (Direct3D9)

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

Fabian Maurer  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.winehq.org/sho
                   |                            |w_bug.cgi?id=39754
                 CC|                            |[e-mail]

[Bug 44681] Outcast Second Contact: pink screen (Direct3D9)

[WineHQ Bugzilla]

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

Sven Arvidsson  changed:

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

--- Comment #3 from Sven Arvidsson  ---
Behavior is unchanged in 6.15.

But considering it's also the same with d9vk, the fact that I don't really know
if the game actually have a d3d9 backend, and that it nowadays starts as normal
with d3d11 I will close this bug.

[Bug 44681] Outcast Second Contact: pink screen (Direct3D9)

[WineHQ Bugzilla]

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

Gijs Vermeulen  changed:

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

--- Comment #4 from Gijs Vermeulen  ---
Closing.