[Bug 57816] New: Splinter Cell: Pandora Tomorrow (2004): crashes when changing game resolution when used with DXVK
https://bugs.winehq.org/show_bug.cgi?id=57816 Bug ID: 57816 Summary: Splinter Cell: Pandora Tomorrow (2004): 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: wine-bugs(a)winehq.org Reporter: daniel.penalized(a)proton.me Distribution: ArchLinux Created attachment 78026 --> https://bugs.winehq.org/attachment.cgi?id=78026 output log When I change the game resolution via the options 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 SplinterCell2.ini configuration file: WindowedViewportX=1600 WindowedViewportY=1200 and the SplinterCell2.ini configuration file: Resolution=1600x1200 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.31). - 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. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57816 --- Comment #1 from daniel <daniel.penalized(a)proton.me> --- (In reply to daniel from comment #0)
and the SplinterCell2.ini configuration file:
Resolution=1600x1200
Oops! The second configuration file is called SplinterCell2.ini and NOT SplinterCell2.ini. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57816 --- Comment #2 from daniel <daniel.penalized(a)proton.me> --- (In reply to daniel from comment #1)
(In reply to daniel from comment #0)
and the SplinterCell2.ini configuration file:
Resolution=1600x1200
Oops! The second configuration file is called SplinterCell2.ini and NOT SplinterCell2.ini.
Sorry about that, I made a mistake again. The first file is called SplinterCell2.ini and the second is called SplinterCell2User.ini. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57816 --- Comment #3 from daniel <daniel.penalized(a)proton.me> --- 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 1024x768)! The same problem also occurs in the first game in the series: https://bugs.winehq.org/show_bug.cgi?id=57815. I opened two different bugs as recommended in the wine Wiki. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57816 --- Comment #4 from daniel <daniel.penalized(a)proton.me> --- 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!. although the output log I've attached here specifically doesn't contain this message, it has appeared several times in Splinter Cell 2) You need to edit the SplinterCell2.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 OverrideOptimalRefreshRate=False option: [D3DDrv.D3DRenderDevice] OverrideOptimalRefreshRate=False UseVsync=True Now you can change to any resolution. What should I do about this bug report? Should I close it? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=57816 --- Comment #5 from D <daniel.penalized(a)proton.me> --- I can't reproduce the crash anymore on DXVK 2.7.1, Mesa 25.2.7-arch1.1 and Wine 10.19. I don't know exactly which of the three solved this issue, but I believe this bug report can be closed. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=57816 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #6 from joaopa <jeremielapuree(a)yahoo.fr> --- DXVK is not supported in this tracker. Please test with the latest vanilla wine (currently 10.19) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=57816 D <daniel.penalized(a)proton.me> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #7 from D <daniel.penalized(a)proton.me> --- (In reply to joaopa from comment #6)
DXVK is not supported in this tracker. Please test with the latest vanilla wine (currently 10.19)
As mentioned in the issue description, this does not happen with WineD3D OpenGL (and as far as I know, WineD3D Vulkan only supports D3D10 and above, so I cannot test it). And a DXKV developer pointed it out as a Wine issue: https://github.com/doitsujin/dxvk/issues/4658 (In turn, a Wine contributor suggested that it could be an issue with Mesa Vulkan Wayland WSI). Anyway, apparently the issue has been resolved by one of the three parties. I am closing this bug report! -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla