WineHQ

Halo SPV3

An updated version of Halo SPV3 from version 3.2.x
It's an extensive mod of the original Halo Custom Edition game.

Application Details:

Version: 3.3.x
License: Free to use
URL: https://www.moddb.com/mods/spv...
Votes: 0
Latest Rating: Silver
Latest Wine Version Tested: 7.0

Maintainers: About Maintainership

No maintainers. Volunteer today!

Free Download Halo SPV3 Moddb

Test Results

Old test results
The test results for this version are very old, and as such they may not represent the current state of Wine. Please consider submitting a new test report.
Selected Test Results

What works

  • The installer*
  • The launcher*
  • Using the "update" button in the launcher
  • OpenSauce*
  • The game
  • Loading checkpoint saves


* = needs (a) workaround(s)

What does not

  • Running the installer with a clean / brand new Wine prefix
  • Changing the default install location for SPV3
  • Editing the default install location "by hand" by attempting to edit the install location field (causes the installer to freeze)
  • ALT+TAB -- ALT+TABBING does "work" but at the cost of the window being stuck transparent until the Wine process is killed
  • The Gbuffer setting works but is partially responsible for some serious slowdowns / FPS / performance drops (from 60 frames to very few) in some areas (and I have a 2080 Ti, so that's saying something); though, even with it disabled, performance can still be pretty shoddy at times
  • Some textures might occasionally get stretched out in some areas
  • With WineVulkan, the launcher works but running the game does not

Workarounds

winetricks -q dotnet461 arial mfc42

  • dotnet461 is required for the installer since it's a .NET program and Wine-mono can't run it
  • Arial is also required for the installer (supposedly a common prerequisite for many .NET 4.x UI apps)
  • mfc42 is required for the original Halo CE installer, which is a prerequisite for the SPV3 installer if a MCC installation (and by extension Windows Steam) is not present in the prefix

Afterwards, dinput8.dll needs a "native,builtin" override because OpenSauce (an "optional" but highly recommended dependency) requires it for the game to launch; otherwise, the user will receive a false error message about missing assets at launch.

Additionally, the SPV3 installer is 64-bit program so having dotnet461 installed in a 64-bit prefix might actually be required.

Lastly, changing the default install location for SPV3 will throw a false message about not having enough storage space on the selected drive, so the only way to get around this is to use symbolic links to redirect the default location to where you really want it to be.

What was not tested

  • Firefight mode
  • Most of the game's story missions (I did the first mission, which is pretty long)

Hardware tested

Graphics:

  • GPU: Nvidia
  • Driver: proprietary

Additional Comments

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
Workaround?
RatingSubmitter
CurrentArch Linux x86_64Jan 24 20227.0No, but has workaround Yes YesSilverNeko-san 
ShowArch LinuxOct 16 20216.16-stagingNo Not installable YesGarbageNeko-san 
ShowArch LinuxMar 29 20216.5-stagingNo Not installable YesGarbageNeko-san 

Known Bugs

Bug # Description Status Resolution Other apps affected
45748 Halo SPV3 installer (.NET 4.5/4.6 app) fails to run NEEDINFO View

Show all bugs

HowTo / Notes

Official Unofficial Instructions for 3.3.0

Instructions provided by JediMasterChief in the Halo SPV3/Legacies Discord server.

Use Winetricks, wine-ge-custom and a 64-bit prefix
Ensure you have a 32-bit graphics driver installed and set up in addition to 64-bit drivers e.g.

$ VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.i686/json:/usr/share/vulkan/icd.d/radeon_icd.x86_64.json
  1. Install mfc42 through winetricks
  2. Install Halo CE and 1.10 Patch. You can simply double click if using default prefix, use the terminal to specify wine prefix to use before running the files, or run wine explorer via winetricks in the prefix of choice
  3. Through Winetricks, install .Net 4.6.1 or later and the arial font
  4. Create the directory you want to install SPV3 into via your Linux file manager, assuming you want any other location than default
  5. Run SPV3 installer using the same methods as step 2.
  6. Navigate to the location you want to install to via browse. Avoid clikcing on the text box. Give the installer a couple of moments to settle on that location before clicking install.
  7. (potentially optional) Once the Open Sauce step is reached, skip it and instead use the latest AmaiSosi from github or from the Manua Upgrade package. If unable to install to SPV3's directory, try clearing the textbox and reselecting SPV3's directory.
  8. Open winecfg, add SPV3's haloce.exe to the applications menu, then with that exe selected in that menu, navigate to libraries and add an native, builtin dinput8.dll override, and configure other options as needed.
  9. Follow the normal SPV3 setup from there.
  10. Download SPV3.3.0a Manual Upgrade and copy its contents into SPV3's game directory, overwriting where necessary. 3.3.0b may be released before 3.3.1

Note: SPV3.3.1 or later will introduce Linux executables of our C#/.NET apps in addition to a mod loader (removing the need for the dinput8 override) in the form of one of the following:

  • Monolith 0.0.3 (replaces Halo's keystone.dll)
  • Monolith 1.0.5 (strings.dll) + Chimera 1.0.0 alpha (./chimera.dll)
  • Chimera 1.0.0 (strings.dll, Monolith built-in).

Note: Custom Edition pre-install is only for SPV3's haloce.exe stock DRM to work. Alternative include using a mostly-zeroed registry key, patching the DRM out of the EXE, and skipping the DRM during runtime.

Linux compatibility for the Loader/Installer is tracked here: HaloSPV3/SPV3.Loader#54


EDIT (2022-09-04):

JediMasterChief — Today at 11:47 AM

@BinToss Actually, I may take back the DSOAL recommendation. Going to run some tests, but I was crashing a lot in the Library with it on.
Actually, it may have been that DXVK-ASYNC

EDIT (2022-09-07)

JediMasterChief — Today at 7:55 PM

I think I may have got my crashes sorted. Forgot to set a specific 32-bit Vulkan driver. Only did the 64-bit driver. May have defaulted to one of the official AMD drivers rather than Mesa.
Vulkan #Switching_between_AMD_drivers
Refer to section 2.1 and its subsections. May apply to other OSs and someone else would have to test Nvidia and Intel
Though I'm not sure if Nvidia and Intel have multiple Vulkan Drivers

Comments

Comments Disabled

Comments for this application have been disabled because there are no maintainers.
Back