[D3D9] Halo CE SPV3 Installer / Launcher Flickering UI

[ThisNekoGuy]

To reproduce this manually without a trace these steps need to be followed:

1. Create a clean wine prefix: WINEPREFIX=$PWD/pfx64 winecfg
2. Run WINEPREFIX=$PWD/pfx64 winetricks -q dotnet461 mfc42 arial dxvk (dotnet461 and arial are needed to make the installer / launcher run; mfc42 is required for Halo CE)
3. cd to wherever the SPV3 installer is, if not already in that directory
4. WINEPREFIX=<path-to-the-prefix>/pfx64 wine start ./spv3.exe
5. At this point, the rendering issue should reveal itself (since the launcher and the installer seem to be the same executable - see below)
6. The installer expects a Halo CE installation but only permits the user to show detection of it if the original CE installer was used or if it's a running Steam process; the easiest way to do this is to just run the original installer and gather the necessary information to install oneself* (running Steam properly in Wine is far more difficult)
7. Once this is done, the SPV3 installer will permit the user to install but will falsely claim not to have enough storage space if you try to move the default install location; if you wish to change it, the only option at the moment is to use symlinks to manipulate where it goes
8. After this is done, it will prompt the user to install OpenSauce (provided with the installer) to the game directory
9. Now, the issue can once again be encountered with the launcher by running it: cd to the game directory and run WINEPREFIX=<path-to-the-prefix>/pfx64 wine start ./spv3.exe

---

• The trace(s) I collected are only a couple megabytes so I don't know how valuable they are
• In addition, while I was attempting to trace the issue, it doesn't occur with WineD3D; I'm only able to experience this issue when DXVK is installed
• I've had this issue for a long time with SPV3's installer / launcher across two Nvidia GPUs (namely the 1060 Max-Q and the 2080 Ti) and many of Nvidia's driver versions

Software information

• Name of the Game Launcher: spv3.exe
• Installer used: https://www.moddb.com/mods/spv3-for-halo-ce/downloads/spv330-release
• SHA256 of the Installer: 6c18d9a089ed17a764e9e56ca52764358ef3f26c4f2f9022b68a1df5e35a5089
• SHA256 of the Launcher: 6c18d9a089ed17a764e9e56ca52764358ef3f26c4f2f9022b68a1df5e35a5089 (They seem to be the same executable? - It seems to "install" itself into the game directory)

The installer / launcher is a 64-bit .NET 4.6.1 application, so I find that DXVK's behavior / influence on it (given that it's not actually a game) is very strange.

System information

• GPU: Nvidia RTX 2080 Ti
• Driver: 510.39.01
• Wine version: vanilla 7.0
• DXVK version: 1.9.3

Apitrace file(s)

spv3 installer trace.tar.gz
spv3 launcher trace.tar.gz

Log files

• d3d9.log: Not available
• d3d11.log: Not available
• dxgi.log: Not available

(None were produced in the tracing process)

[wils0nyan]

Return of Reckoning (warhammer online) also has a blacked out laucher (at least with latest mesa radv) so you can play the game but have to guess where the login and password box is

It's free to play no steam or anything, but you still have to download the client and make an account

The issue does not occur when using standard wine-staging 7, but occurs when using wine-staging 7+dxvk and doesn't seem to have anything to do with floating emulation i think or anything. It's a dx9 gamebyro engine game, but that probably has no relevance to the launcher.

[Blisto91]

@K0bin If the solution for Return of Reckoning was a fine workaround (i see it haven't been merged) then I'll make a pr with the same for this since it's the same issue (tested). If you don't mind it being for a mod launcher.