Enemy Engaged: Apache vs Havoc

From PCGamingWiki, the wiki about fixing PC games
This page is a stub: it lacks content and/or basic article components. You can help to expand this page by adding an image or additional information.
Enemy Engaged: Apache vs Havoc
Enemy Engaged: Apache vs Havoc cover
Strategy First
Release dates
Windows October 18, 1998
Enemy Engaged: Apache vs Havoc on MobyGames
Enemy Engaged: Apache vs Havoc on Wikipedia
Enemy Engaged
Enemy Engaged: Apache vs Havoc 1998
Enemy Engaged: Comanche vs Hokum 1999
Enemy Engaged 2 2007

General information

GOG.com Community Discussions for game series
GOG.com Support Page


Source DRM Notes Keys OS
DRM details are not known
Install Patch 1.1e.

Essential improvements[edit]


Patch 1.1e fixes various issues. The GOG.com version is already patched.

Game data[edit]

Configuration file(s) location[edit]

System Location

Save game data location[edit]

System Location

Save game cloud syncing[edit]

System Native Notes
GOG Galaxy

Video settings[edit]

General settings.
General settings.

Graphics feature State Notes
Widescreen resolution
4K Ultra HD
Field of view (FOV)
See the glossary page for potential workarounds.
Borderless fullscreen windowed
See the glossary page for potential workarounds.
Anisotropic filtering (AF)
See the glossary page for potential workarounds.
Anti-aliasing (AA)
See the glossary page for potential workarounds.
Vertical sync (Vsync)
See the glossary page for potential workarounds.
60 FPS and 120+ FPS

Input settings[edit]

Audio settings[edit]

Audio feature State Notes
Separate volume controls
Effects, Music, Speech, Co-pilot speech.
Surround sound
Closed captions
Mute on focus lost


Multiplayer types

Type Native Notes
LAN play
Online play

Issues unresolved[edit]

"Unable to create Zbuffer surface: DDERR_NOZBUFFERHW" Error"[edit]

This is likely caused by a PowerVR card in your computer. These cards are not supported and there is currently no fix.

Issues fixed[edit]

Rainbow coloring[edit]

See the Rainbow color problems in older games page for details on fixing this issue

Problem with Riva128 chipsets[edit]

Riva128 chipsets can cause graphical artifacts, use this fix if you believe you're having graphical artifact problems.
/3dce command line option[citation needed]
  1. Open the command line while in-game
  2. Input /3dce
  3. Play game

Invisible pylons and power lines[edit]

3Dfx chipsets, notably the Voodoo2, cannot render lines in newer versions. Reverting to version 2.5 of your graphics drivers will correct this problem.

Other information[edit]

Console commands[edit]

Parameter Description
/3dce "3D clean edge" - Cleans up the graphical artifact
/3dreset "3D reset" - Sets the default screen resolution to 640x480. This may be required if the game crashed whilst attempting to use an unsupported display resolution.
/cbar:[value] "city block approximation range" - Sets the distance (in meters) at which city buildings approximate. The default value is 500 metres (/cbar:500). On faster PCs you can increase this value to reduce the 'pop-up'effect.
/cg "clean graphics" - Re-installs the graphics files from the CD.
/dcdz:[value] "dynamics cyclic dead zone" - Sets the joystick dead zone as a percentage. The default value is 0 (/dcdz:0).
/ns "no sound" - Disables sound if the program has problems with your sound card.
/cdrs:[value] "comms data record size" - Sets the initial estimate for the maximum size of the campaign data (in bytes). If the value is too low the program will be slower connecting, too large will waste memory. The default value is 200000 (/cdrs:200000).
/cist:[value] "comms initial sleep time" - Sets the length of time (in milliseconds) the program will wait before sending packets. This is to allow DirectPlay to establish a stable connection and may vary with proprietary service providers. The default value is 500 (/cist:500).
/cpt:[value] "comms packet timer" - Sets the length of time (in seconds) the program will wait for a packet before re-requesting it. The default value is 5 seconds (/cpt:5).
/crls:[value] "comms re-send list size" - Sets the number of packets kept in the history buffer. This is required for re-sending lost or corrupt packets. The default value is 1000 (/crls:1000). Increasing this value may improve reliability but requires more memory.
/crl:[value] "comms re-request limit" - Sets the number of times a missing packet will be re-requested. The default value is 10 (/crl:10).
/crto:[value] "comms re-send timeout" - Sets the length of time (in seconds) the program will wait for a re-requested packet before asking for it again. The default value is 1 second (/crto:1). This value may vary with service providers.
/mur:[value] "maximum update rate" - Sets the maximum update rate (in iterations per second) for the communication system. This is independent to the visual frame rate but will never exceed it. This may be used to limit the amount of packets sent and help avoid 'swamping' a connection. The default values vary according to the connection method:

IPX  : 15 (/mur:15)

Serial : 15 (/mur:15)

Modem  : 5 (/mur:5)

TCP/IP : 5 (/mur:5)


Executable 32-bit 64-bit Notes

System requirements[edit]

Minimum Recommended
Operating system (OS) XP, Vista
Processor (CPU) 1 GHz
System memory (RAM) 512 MB
Hard disk drive (HDD) 211 MB
Video card (GPU) DirectX 7 compatible