What does not
Specular shields on spartans/elites and specular highlighting on invisibility. This is only a visual problem and detracts nothing from gameplay.
Lightmaps sometimes look strange (usually from headlights of warthog).
What was not tested
Halo will not run in fullscreen mode; It will only work inside a window.
Halo works really well now in Wine! Before you rate this game as garbage, please follow the instructions and properly add mfc42.dll to system32 in your wine directory! Also make sure that you either have Halo run in window mode or inside the wine virtual desktop window, or else Halo WILL NOT RUN! This is one of the few major bugs I found in the game. I'll repeat: Halo will not run in fullscreen mode; It will only work inside a window. The chat text in the multiplayer can also be made to work. The chat not working has been listed as a bug and this is simply incorrect. To get the chat working, you must have the Microsoft XML Parser installed. It should come with the game, but for some reason it doesn't always install properly. The easiest way to install msxml is to download Winetricks and use it to install msxml3, msxml4, and msxml6. If you decide to install it manually, you must register the dlls by either using winecfg or use the following commands: wine regsvr32 msxmL4.dll wine regsvr32 msxmL3.dll wine regsvr32 msxmL2.dll wine regsvr32 msxmL.dll 3 You may also need to install ttf-symbol-replacement-wine in order to give Halo the proper fonts to use for the chat. The mouse/camera are jittery in 30fps mode, but this will go away if you set the game to No Vsync mode. The jitteriness almost entirely goes away and the gameplay is incredibly smooth. Using Vsync also seems to work fine too, but I prefer to use No Vsync because I like to turn off my compositor during gameplay. To start Halo, I have a shell script that I run that's inside of the same directory as halo.exe. Here's what it looks like: ------------------ #!/bin/bash xset m 1 1 __GL_SYNC_TO_VBLANK=1 wine ./halo.exe -vsync -vidmode 800,600,60 -use14 -window xset m default ------------------ In your Wine configuration, make sure that "Allow DirectX apps to stop the mouse from leaving their window" is turned on. I've noticed that Halo actually changed the speed of your mouse in your system. If this happens, you can just change it back in your distro's mouse settings.
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||MacOs Catalina 10.15||Apr 07 2021||5.0.4-staging||N/A||Yes||No||Bronze||Thomas Helton|
|Show||Ubuntu 20.10 "Groovy" (+ variants like Kubuntu)||Dec 14 2020||5.0.3||No, but has workaround||Yes||Yes||Bronze||Charles Edward Rogers Jr.|
|Show||Manjaro Linux 18.0.0||Apr 05 2019||4.5||Yes||Yes||Yes||Gold||Bob Niemöller|
|Show||Debian GNU/kFreeBSD Unstable "Sid"||Aug 30 2014||1.7.25||Yes||Yes||Platinum||Johannes|
|Show||Fedora 20 x86_64||May 15 2014||1.7.18||Yes||Yes||Silver||Zachary J|
mount -oloop Halo.iso /cdrom
~/.wine/drive_c/Program\ Files/Microsoft\ Games/Halo/haloupdate.exe
cd .wine/drive_c/Program\ Files/Microsoft\ Games/Halo ./halo.exe
Installing 'halotrialsetup.exe' into a clean wineprefix should work fine with wine-1.3.37.
To run the game, the working directory must be the Halo Trial directory, e.g.
cd ~/.wine/drive_c/Program\ Files/Microsoft\ Games/Halo\ Trial/ wine halo.exe
2015-10-06 Admin note: the following issue has been patched in version 1.0.10 of Halo Custom Edition and Halo Combat Evolved.
2014-11-08 Admin note: the following was extracted from a user comment made on 2013-10-30 and may or may not be relevant to current Wine.
THIS DOES NOT APPLY TO CURRENT VERSION OF HALO CE/PC
Wine is, like Windows, affected by a bug where Halo doesn't render
shaders as well on Nvidia hardware. The most visible symptom is that the
active camouflage is only using transparency instead of the proper way
where it is using a pretty neat shader.
The Windows fix is based on making Halo believe it is running on an ATI card, which is not so complicated within Wine. Loosely based on the Windows fix, enter these into the registry:
As DWORD: "HKCU\Software\Wine\Direct3D\VideoPciDeviceID" = "724b"
As DWORD: "HKCU\Software\Wine\Direct3D\VideoPciVendorID" = "1002"
If your Halo is in a more vast prefix, it is recommended to specify it exclusively for the halo.exe as this fix may have the potential to burn your house down.
This picture will display the basic improvement: i.imgur.com/Rq93SgZ.jpg
Use argument -windowed to play correctly
Example: wine halo.exe -windowed