[Bug 57815] New: Splinter Cell (2002): crashes when changing game resolution when used with DXVK

[WineHQ Bugzilla]

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

Bug ID: 57815
           Summary: Splinter Cell (2002): crashes when changing game
                    resolution when used with DXVK
           Product: Wine
           Version: 10.1
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: winewayland
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ArchLinux

Created attachment 78025
  --> https://bugs.winehq.org/attachment.cgi?id=78025
output log

When I change the game resolution via the settings menu, the game crashes.

You can also crash when you start the game (right after the introductory
video). Just change the game resolution via the SplinterCellUser.ini
configuration file:

Resolution=1920x1080

This behavior only happens when used with DXVK. It doesn't happen with WineD3D
OpenGL (it's impossible to test with WineD3D Vulkan, as it completely breaks
the look of the game). And of course, it doesn't happen with winex11.drv
either.

- The game was installed via CD-ROM and is up to date with the latest update
(v1.3).
- I use labwc/wlroots as WM.
- Although I'm on Arch Linux, I compile wine manually with these options:
./configure --prefix=/usr --enable-archs=i386,x86_64 --enable-win64. So I'm
using the new WoW64 mode, but this behavior also happens in normal wine.

[Bug 57815] Splinter Cell (2002): crashes when changing game resolution when used with DXVK

[WineHQ Bugzilla]

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

joaopa  changed:

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

--- Comment #1 from joaopa  ---
How do you know it is a wine bug, not a DXVK bug?

[Bug 57815] Splinter Cell (2002): crashes when changing game resolution when used with DXVK

[WineHQ Bugzilla]

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

--- Comment #2 from daniel  ---
(In reply to joaopa from comment #1)
> How do you know it is a wine bug, not a DXVK bug?

I already reported it as a DXVK bug
(https://github.com/doitsujin/dxvk/issues/4658) and it was closed because it
was considered a wine bug.

[Bug 57815] Splinter Cell (2002): crashes when changing game resolution when used with DXVK

[WineHQ Bugzilla]

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

--- Comment #3 from daniel  ---
Just to add a little extra information: the game crashes when you change to any
of the resolutions other than the game's default (in this case, the default is
640x480)!

The same problem also occurs in the second game in the series:
https://bugs.winehq.org/show_bug.cgi?id=57816. I opened two different bugs as
recommended in the wine Wiki.

[Bug 57815] Splinter Cell (2002): crashes when changing game resolution when used with DXVK

[WineHQ Bugzilla]

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

--- Comment #4 from daniel  ---
So, the problem is solved by enabling the game's vsync! (and is related to the
message that appears in the output log: wp_tearing_control_manager_v1#19: error
0: Tearing control object already exists!)

You need to edit the SplinterCell.ini configuration file. In the
[D3DDrv.D3DRenderDevice] section, you add the UseVsync=True option anywhere on
the line, in my case I put it on the last line, after FullScreenVideo=True
option:

[D3DDrv.D3DRenderDevice]
FullScreenVideo=True
UseVsync=True

Now you can change to any resolution. What should I do about this bug report?
Should I close it?

[Bug 57815] Splinter Cell (2002): crashes when changing game resolution when used with DXVK

[WineHQ Bugzilla]

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

Giacomo Orlandi  changed:

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

--- Comment #5 from Giacomo Orlandi  ---
(In reply to daniel from comment #4)
> Now you can change to any resolution. What should I do about this bug
> report? Should I close it?

As far as I understand, even though there is a workaround, it's still a bug, so
IMO it shouldn't be closed. But I'm not a Wine expert.