What does not
What was not tested
Running the game without applying the most recent patch first. The most recent version, of course, no longer requiring the install CD to be in the disc drive.
Since the lack of the MFC library really isn't a bug, I don't count it as a problem with Wine or Halo. Also, the mouse can sometimes be a little laggy, but I believe this is an inherent problem with the game itself. It seems that if you can maintain a framerate that is generally higher than 30 (i.e. in VSYNC or NO VSYNC modes), the mouse operates quite smoothly. Most computers with decent graphics chipsets or graphics cards _should_ be able to do this; the game is from 2001, after all! My system specs: OS: Ubuntu 11.04 x86_64 GFX: NVIDIA GTS 250 PCIe x16 256-bit GDDR3 512MB CPU: AMD Phenom II X2 @ 3.65ghz RAM: 4GB DDR3 1600 (CAS 9) Also, pulseaudio quite literally destroys any audio synchronization between the game events and sound itself. This however is a problem with PA and Ubuntu, and not Wine.
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|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|
|Show||Arch Linux x86_64||Jul 04 2013||1.6-rc4||Yes||Yes||Platinum||Serge Hooge|
|Show||Linux Mint 14 "Nadia"||Dec 14 2012||1.5.18||Yes||Yes||Gold||Carlos Rodriguez|
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