2014
08.04

HAC 2.2.0.4 Update

  • Fixed a medals related bug some users were experiencing that would cause the game’s process to remain open after exiting.
  • Fixed a custom chat rendering issue on Vista.
  • Fixed a small typo that causes the Halo Reach medals script to fail when awarded the ‘Unfriggenbelievable’ medal. Download the updated script here.
2014
07.27

HAC 2.2.0.3 Update

Just a minor update to redirect all 1.09 clients (update to 1.10 already) to the new master server now that Gamespy has pulled the plug.

2014
06.01

HAC 2.2.0.2 Update

Changes:

  • Fixed an OpenSauce compatibility issue that crashed the game on launch.
  • Fixed a bug with 1.10 where the draw distance wasn’t automatically being increased for certain custom maps.

For those using WINE, if you could post your distro and whether you’re using HPC or HCE in the comments, that’d be helpful.

2014
05.28

Fixes:

  • Windows XP users will now be able to see the custom chat, although it’ll use an installed typeface rather than the featured one.  This bug is caused by Windows XP itself and there isn’t a suitable workaround (apart from getting a newer OS), although you’ll be able to select your own typeface at some point in the future.
  • Some maps could cause the game to crash after downloading. This was a regression (plain English: it worked, then I broke it) introduced in the January update.
  • Forgetting to use an option (0/1/true/false) with custom_chat will no longer cause a crash.

Additions:

  • Medals.

Medals:

 

This update introduces a Lua scriptable medal system. To get the ball rolling, I’ve provided three example medal packs (click to download); Halo 3, Halo Reach and Halo 4. To install a medal pack, simply download it to your HAC folder under the ‘packs’ directory (create it if it doesn’t exist) but do not extract it. For example:

Halo PC: C:\Users\Your_Username\Documents\My Games\Halo\hac\packs
Halo CE: C:\Users\Your_Username\Documents\My Games\Halo CE\hac\packs

If we installed the Halo Reach pack to our CE HAC folder, it’d look like this:

C:\Users\Your_Username\Documents\My Games\Halo CE\hac\packs\haloreach.zip

You can then use the following commands:

  • optic - display all available medal packs.
  • optic load <pack name> – load a medal pack. For example, optic load halo4.
  • optic unload - stop the medal system. You do not need to use unload to simply load another pack.

The optic load command only needs to be used once. HAC will remember your preference for the next time you start the game.

Creating your own medal packs:

Although you’re welcome to open the provided medal packs to see how I’ve done things, documentation will be forthcoming (next week, ideally).

Troubleshooting:

If you encounter any problems with using Optic, please see the troubleshooting page.

Enjoy!

2014
05.21

HAC 2.1.3.2 Update

Changes:

  • HAC and OpenSauce are once again compatible.
  • Fixed an error that could prevent custom_chat 1 from working (“Unable to load font!”).
  • Fixed a HUD issue where the game type icon wasn’t being scaled correctly on extremely wide resolutions.
  • Added a new command, font_size, that can be used to control the custom chat size. Example: font_size 30.

Known issues:

  • HAC no longer loads on WINE. I’m still looking into this.
  • Corrupt chat text on low-end graphics hardware. May not be able to solve this without access to a machine experiencing the problem.
2014
05.19

HAC 2.1.3.1 Update

Changes:

  • Fixed a bug in HAC’s crash handler that was causing some crashes to be falsely attributed to HAC.
  • Added more detailed error feedback for the custom_chat 1 command.
  • Fixed a bug that could potentially cause a crash when launching/maximising the game.

Compatibility notes:

  • OpenSauce and HAC 2 are currently incompatible. A solution is being worked on, so hold tight.
  • Optic may have compatibility issues on some systems. A solution is being worked on.
  • Halo Chat V2 won’t work if custom_chat 1 is being used (and vice versa). This isn’t considered to be a bug, so there are no plans to fix this.
2014
05.17

HAC 2.1.3 Update

Just a minor update to fix a few issues introduced by the rushed 2.1.2 that was primarily intended as a 1.10 compatibility patch.

Fixed:

  • Joining 1.10 servers on Halo PC (CE unaffected) will now work as expected.
  • Map downloading is once again functional.
  • “Play ball” is no longer announced in the place of “double kill”, as amusing as it was.

As a peace offering, a console command that can be used to enable a test version of the new chat system has been added. If you’d like to give it a try, use ‘custom_chat 1‘. An example of what to expect below.

chat_preview

2014
05.16

HAC 2.1.2 Update

Note: If you’re having problems since updating to 1.10, please remove all other mods to ensure that the problem is actually related to HAC 2.

Note #2: If you’re experiencing an ‘error 126‘, attempt installing the latest Direct3D9 from: http://www.microsoft.com/en-gb/download/details.aspx?id=35

Aside from 1.10 compatibility, here’s the list of changes:

Bug fixes:

  • The sightjacker will no longer advance by two players at a time when using the keyboard controls.
  • HUD colour resets now save correctly.
  • Field of view preferences had a small chance to reset if the game didn’t exit correctly.

Changes:

  • The sightjacker will now automatically continue to track your target after respawning.
  • The BSP upgrade is now available for all game versions rather than just CE 1.09.
  • The HUD colour shortcut key has been moved from F9 to F8.

New features overview:

  • The particle limit has been increased by 50%.
  • Active camouflage now renders correctly on Nvidia cards (not tied to 1.10).
  • Scope blur can be disabled via a console command without requiring the disablealpharendertargets config.txt mod.
  • Resolution selection is no longer limited to a maximum of 1600×1200 (not tied to 1.10).
  • Your resolution in windowed mode can now match your desktop resolution.
  • The game now has a windowed-fullscreen mode.

Active Camouflage:

The full active camouflage effect will now display correctly on Nvidia cards by default. If you wish to revert to the old effect, you can use the console command camo_fix 0.

Active Camouflage Fix

Scope Blur:

Scope blur can now be toggled with the command scope_blur 0/1. This removes the need to add the potential undesirable disablealpharendertargets option to your config.txt.

scopeblur

Resolutions & Windowed-Fullscreen mode:

The requirement to specify the -vidmode argument has been removed with a fix to Halo’s video options to allow for the selection of all supported resolutions.

Additionally, when running the game in windowed mode (-window), users can toggle between windowed and the new windowed-fullscreen mode by pressing alt + enter. As with other games that offer a windowed-fullscreen option, your game resolution must match your desktop resolution to be able to enter windowed-fullscreen. The reason for this limitation is simply that the window scaling used by Windows 7 and up makes the game look awful if it has to be stretched.

resfix

2014
05.13

HAC 2 & 1.10

Just a short post to confirm that HAC 2 will be updated to support 1.10 once it’s officially released as a finalised auto-update.

The update will be rolled out automatically hopefully just prior to the switch.

2013
12.28

HAC 2.1.1 Update

Widescreen HUD Fix:

Rather than stretching, the game’s HUD will now automatically resize to the correct proportions for your resolution’s aspect ratio (e.g. 1920×1080, 16:9).

This feature is enabled by default but can be disabled with the console command ‘hac_widescreen 0‘.

Widescreen HUD FixClick for full size

Custom HUD Colours:

Pressing F9 will allow you to set custom colours for the HUD. Shift + F9 will reset the colours to their default values.

When you press F9, you will be given instructions for adjusting the reticle colours, primary element colours, secondary element colours and tertiary element colours.

  • Reticle colours – Self-explanatory
  • Primary colours – Includes most of the UI such as your shield, health and ammo (the blue elements).
  • Secondary colours – Includes the depleted ammo/grenade indicators.
  • Tertiary colours – Includes flashing ammo/grenade/shield warnings.

The easiest way to figure it out is to play around with the values a bit and see what they affect.