Versions 1.0 to 1.09, where 1.08 and above don't need to have CD to run (therefore rendering Wine copy-protection issues... non-issue).
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 (selected in 'Test Results' table below)
What does not
What was not tested
Played with a PS4 controller (can be configured in the game's menu) as well as keyboard and mouse on 2560x1440 (-vidmode) everything on high for about one hour.
I had to change the fps to 30, otherwise the models don't move completely smooth. This is most likely related to the game I guess and should not have anything to do with Wine.
Additionally I set multisampling to 32x and texture filtering to 16x via NVidia's environment variables as those options are missing in the game.
Run the game. The working directory must be the Halo directory.
cd .wine/drive_c/Program\ Files/Microsoft\ Games/Halo
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/
Active camouflage fix
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
HOWTO Run in windowed mode
Use argument -windowed to play correctly
Example: wine halo.exe -windowed
The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
Returns strange error, and won't display graphics
by David Henderson on Friday September 19th 2014, 21:57
On Ubuntu 14.04 with Intel Iris Pro graphics, Halo will launch but will just display a black screen. The music and menu sounds work correctly when I push the arrow keys.
When I try in safe mode, It's all black except for some flashing lines in the lower right quadrant of the screen. I also get spammed with the same error in the terminal:
fixme:d3d:process_vertices_strided Didn't expect the destination to have a normal
One way to fix
by Zachary J on Thursday May 15th 2014, 19:58
I found this solution after I got so frustrated when this error occurred constantly after upgrading to Fedora 20. Disabling prelink solved this problem. The procedure is as follows. You need to follow the first two steps as root, and know how to use a console editor and run a console command.
1. Disable prelink by editing the file /etc/sysconfig/prelink:
2. Undo the prelink by executing the command /etc/cron.daily/prelink
4. Try the game. If the error still occurs, go to step 3