Graphical glitches with Resident Evil 3 (GOG) and the Seamless HD Project mod

[ShadowOne333]

Good day.

I've been trying to get RE3 working on Linux/Steam Deck with the HD/Seamless HD Project (SHDP) mod for over two months now, but no matter what I try, I always end up with the same result, which is the actual backgrounds/textures looking really small on the upper-left corner of the screen, as seen in these images:

https://imgur.com/a/Bj8o51s

To get the game running on Linux, be it any distribution or Steam Deck, I use the following DLL overrides:

WINEDLLOVERRIDES="d3d9,d3dcompiler_47,ddraw,dinput8,dsound,libwebp,xaudio2_9"=n,b

Those same overrides are the ones I use for RE2 and it works perfectly with Classic Rebirth alongside the Seamless HD Project mod. RE1 CR+SHDP does work too, although that one required some dgVoodoo2 intervention). While RE3 does work with Classic Rebirth on its own, it's the HD mod causes that graphical issue on any Linux machine I tried, Steam Deck included.

I tried screwing around with the DLLs, and found that dinpu8 is the one that seems to load the HD textures.
According to some tests by several other people from both the Proton GE Discord and the Seamless HD Project Discord, it seems like the issue could be related to the implementation of DirectX made by Wine/Proton, be it WineD3D or DXVK.

(Check the Proton and Wine logs for debugging reference at the bottom of the post)

I also attempted running DXVK_HUD=full as suggested by a community member to test whether or not DXVK was properly running, and this was the result

Software information

Resident Evil 3: Nemesis (1999) from GOG

• It's important to note that the version of RE3 needed for the mods to work is the Japanese version.

To run the game with the exact same conditions to reproduce the HD textures/backgrounds glitch, the following is required:

• Official SourceNext 1.1.0 patch
• Classic Rebirth mod for RE3
• Resident Evil 3 HD mod

Once the game is properly installed with the Japanese language, all that's needed is:

• Replace the original EXE with the one from the Official 1.1.0 SourceNext patch
• Replace the ddraw.dll from the original game with the one from the Classic Rebirth mod
• Copy all contents from the RE3 HD mod into the same place as the EXE. Warning: If the HD mod has a ddraw.dll file, do NOT replace the one from the Classic Rebirth mod!
• To make the game run under Linux/Steam Deck, the following DLL overrides are required:
  WINEDLLOVERRIDES="ddraw,dinput8"=n,b
  Those are the bare minimum of DLL needed to get the HD mod running. Afterwards, running the Wine DLL Override command alongside wine "BIOHAZARD(R) 3 PC.exe" should make the game run with the following window opening, and then the game window with the graphical glitch:
  
  

System information

Steam Deck specs:

• GPU: 8 RDNA 2 CUs, 1.6GHz (1.6 TFlops FP32)
• Driver: Mesa 24.2.5
• Wine version: 9.0, Proton 7.0-6, 8.0-5, 9.0-3, Experimental, Proton GE 9.16.
• DXVK version: 2.4.1

Apitrace file(s)

Pending
For instructions on how to use apitrace, see: https://github.com/doitsujin/dxvk/wiki/Using-Apitrace

Log files

• Proton logs:
  steam-0.log
  steam-1266089300.log

• Wine's game.log

[keenanweaver]

For what it's worth, I have the same problem and also never figured it out. I tend to use dgVoodoo v2.79.3 as the ddraw compatibility layer, but I experienced the same problem without it (and without DXVK).

RE2 with SHDP does not have the same problem, which is puzzling. I've used the GOG & CD versions of both games.

I actually don't like the look of the SHDP at all, so I don't play them with it. But it's definitely a problem for those who want to use it.

Regardless, I'm not sure if the DXVK folks would take this issue on.

My system information:

• GPU: AMD Radeon RX 7900 XTX
• Driver: Mesa 24.2.5
• Wine version: GE-Proton 9-18, Kron4ek 9.20, sys-wine 9.20
• DXVK version: 2.4.1

[ShadowOne333]

I have updated the OP to include both the Proton and Wine logs, as well as the exact versions of the driver, Proton versions I tried and also the DXVK version (which could be seen in the image I added in the OP with the Proton HUD).

[Desconvidado]

this issue is present even when not using dxvk.

You probably shouldn't be opening a bug report here.

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