Hind & Seek: Finding a Hind setup

DarkenedRoom
Dec 25, 2025
14 min read

This is a guide to running the 1996 Digital Integration (DI) sim Hind (also called HIИD or Hind: The Russian Combat Helicopter Simulation).

Hind can be considered if not a sequel, then a successor to the previous DI sim Apache (Longbow).

The DOS version will be running in DOSBox Staging and the Windows 95 3Dfx version in native Windows 10. The Windows 95 non-3Dfx/software rendered version will be omitted as it provides no additional enhancements over the DOS version.

Both Hind and Apache use a similar game engine resulting in a great deal of commonality between both configurations.

Release & patch history

Before continuing it's useful to take a look at the releases and the patches each release can use, to understand how the releases and patches relate to each other.

Original retail release (16 Sep 1996)

The original retail release was distributed on a single CD-ROM including both DOS and Windows 95 installers. The Windows installer is a 32-bit app which is compatible with Win10.

HIND v1.2: DOS version patch (4th Feb 1997)

The Hind v1.2: DOS version patch is a comprehensive bug/crash fix and enhancement patch for the DOS version only. It is a file replacement patch, replacing the existing hind.exe file. The bug fixes are listed in the readme file as:

Option to reverse collective control from preferences now functions.
Debug Fatal removed from 3D Visual code.
CTRL-4 (message to wingman) no longer crashes the game.
Problem causing occasional crashes at the final Afghanistan campaign animation fixed.
Bug causing occasional crashes after clicking 'Okay' button on situation screen removed.
*All* models of Thrustmaster sticks now technically supported.

And the enhancements listed in the readme file:

New WSO operation modes.
Audible undercarriage.
Optional 'wimp mode' landing cushion.
Description of crash-land cause.
Provision of R-60's for two-player flights.
Keyboard control for collective was always overridden by a connected throttle stick - not any more.

Items in bold are unique to the DOS version patch. This patch also includes legacy joystick/throttle configuration files that are only applicable to the DOS version.

HIND v1.2: Win95 version patch (6th Feb 1997)

The Hind v1.2: Win95 version patch is applicable only to the Win95 version of Hind. It provides many of the same bug/crash fixes and enhancements as the DOS version of the patch. It is a file replacement patch, replacing the existing hind95.exe file. The following addition bug fixes are unique to the Win95 version patch:

Disabling of rudder while panning corrected.

This patch omits legacy joystick/throttle configuration files, as stick/throttle is supported by Win95.

Digital Integration retail rerelease (17 Feb 1997)

Shortly after the patches were released there was a retail rerelease with both DOS and Win95 installers and both DOS and WIn95 v1.2 patches. Once again distributed on a single CD-ROM. The Windows installer remains a 32-bit app which is compatible with Win10. Patches should be installed automatically.

This version includes a 16-bit Digital Integration multimedia launcher app which in addition to running the Win95 installer, includes a preview of F-16.

Twin Pack: Hind / Apache Longbow (2 Jul 1997)

A compilation release featuring Apache Longbow and Hind. The Hind version is identical to the retail rerelease (Feb 1997) with both DOS and WIn95 v1.2 patches included. The Windows installer remains a 32-bit app which is compatible with Win10. Patches should be installed automatically.

The 32-bit launcher app is included with a DOS and Win95 installer, previews and demos.

Win95 3Dfx version patch (23 Mar 1998)

This patch provides 3Dfx support for the Win95 version of Hind. It should work on any previous Win95 version including v1.0, but it is recommended to patch to v1.2 before applying this patch. From the notes:

This patch has currently been tested with versions 1.1 and above of Hind (includes patch releases, 'Twinpack' & 'Front Line Fighters' releases). It should also work with v1.0.

This patch provides the following enhancements:

Possible average 50% speed increase.
New 'Dynamic lighting' system.
True colour Alpha blending on constructs such as cockpits, rotor blades, etc.
True colour Bilinear filtering and fogging effects.

This patch comprises of two compressed archives, the Hind 3Dfx patch archive and a common files archive. The release notes state: the patch archive is extracted to a folder, then the common files are extracted to the same folder. The patch installer can then be run.

3Dfx/Voodoo2 upgrade patch (26 Jun 1998)

The Voodoo 2 upgrade patch is a compatibility patch only adding Voodoo 2 support. It is a file replacement patch, replacing the existing hind95.exe file. From the release notes:

This is a 'compatibility patch' only. It does not offer extra features over previous 3Dfx Voodoo1 versions.

Sold Out Software release (15 Oct 1998)

The Sold Out Software budget rerelease is the most comprehensive release. Distributed on a single CD-ROM it includes:

A DOS installer, pre-patched with v1.2.
A non-3Dfx Win95 installer, pre-patched with v1.2
A 3Dfx installer, pre-patched with v1.2 and the 3Dfx patch.

The 3Dfx/Voodoo2 upgrade patch is not included with this release. This release uses a 32-bit Win95 installer compatible with Win10. In addition the manual is included in a digital pdf format.

Digital release on GOG/Steam/Zoom (15 Mar 2012)

Available on GOG/Steam and Zoom digital platforms. This digital release includes the DOS version of the game only, without installers, so a fresh/clean installation cannot be made. The hind.exe file seems to be a v1.0 or v1.1 copy, modified to prevent hanging when auto-detecting/configuring sound cards.

The standard DOS v1.2 patch cannot be used as the game will hang when loading sound files. Deleting the prefs.cfg file will cause the game to load, only to hang when trying to set the sound preferences. Therefore the use of a modified digital release v1.2 patch is required.

HIND v1.2: unofficial digital release patch (7 Feb 2017)

An unofficial patch to add v1.2 fixes and enhancements to the GOG version. It unknown if this will work with other releases. It is a file replacement patch replacing hind.exe and a sound file. It is recommended to only replace the executable initially, replacing the sound file if needed, as replacing the sound file may introduce new issues.

The patch compatibility with Steam or Zoom platform versions is unknown.

Obtaining patches

All patches are available from the Internet Archive at Hind patch collection. The 3Dfx Voodoo1/Voodoo2 patches are also available from soggi.org.

Patching strategies

The following are the recommended methods in patching the game.

Original retail release DOS version

Install original retail release DOS version.
Apply HIND v1.2: DOS version patch.

Retail rerelease/Twin pack compilation/Soft Out Software release DOS version

Install DOS version, pre-patched to v1.2.

Digital release DOS only (GOG platform)

Install digital release.
Apply HIND v1.2: unofficial digital release patch.

Digital release DOS only (other platforms)

Install digital release.

Original retail release Win95 version (non-3Dfx)

Install original retail release Win95 version.
Apply HIND v1.2: Win95 version patch.

Retail rerelease/Twin pack compilation release Win95 version (non-3Dfx)

Install Win95 version, pre-patched to v1.2.

Soft Out Software release Win95 version (non-3Dfx)

Install Win95 version with software renderer, pre-patched to v1.2.

Original retail release Win95 version (3Dfx)

Install original retail release Win95 version.
Apply HIND v1.2: Win95 version patch.
Apply Win95 3Dfx version patch.
Apply 3Dfx/Voodoo2 upgrade patch.

Retail rerelease/Twin pack compilation release Win95 version (3Dfx)

Install Win95 version, pre-patched to v1.2.
Apply Win95 3Dfx version patch.
Apply 3Dfx/Voodoo2 upgrade patch.

Soft Out Software release Win95 version (3Dfx)

Install Win95 version with 3Dfx/Voodoo renderer, pre-patched to v1.2.
Apply 3Dfx/Voodoo2 upgrade patch.

Media

Due to the age or the media and the drives required to read the media, it is recommended to rip cd-rom media to image files, to save wear and tear on media and the mechanical drives.

The cd-rom can be ripped to a data only .iso image format as there is no cd audio on the cd.

Game management

It is recommended to use my DOSBox game management strategy or similar strategy you may have developed. The recommended game management folders are:

cd - to store the cd image.
conf - to store any DOSBox or HOTAS configuration files.
hdd - the folder use as the emulated DOSBox hard disk.
patches - to store any patches.

The Windows version uses the following installation folder:

<Drive>:\Games\Win\Hind

And the following game management folder:

<Drive>:\Games\Win\Hind Setup

And the following sub-folders:

cd - to store the cd image
conf - to store any HOTAS configuration files.
patches - to store any patches.

HOTAS config

Joystick, throttle and rudder pedals are supported. Configuring axes may not be required if your HOTAS has 4 axes or less. When using a combination of devices totaling more than 4 axes, a virtual controller can be configured (with vendor software or Joystick Gremlin), limited to 4 axes. The physical axes to Windows axes were configured as follows:

For those using controllers from multiple vendors, the vJoy/Joystick Gremlin combination may be required instead of vendor specific HOTAS profile software. You may also have to use HidHide as a device firewall, to hide your real controllers, so only the vJoy virtual controllers are detected by Hind.

The physical axes to Windows axes were configured as follows:

Physical axis	Windows axis (DOS)	Windows axis (Win95)
Joystick x-axis	DX_X_AXIS	DX_X_AXIS
Joystick y-axis	DX_Y_AXIS	DX_Y_AXIS
Throttle	DX_Z_AXIS	DX_Z_AXIS
Rudder	DX_XROT_AXIS	DX_ZROT_AXIS

Note: These settings are identical to the predecessor, Apache (Longbow).

DOS version

This guide assumes the Sold Out Software, Oct 1998 release is used.

DOSBox config

This guide assumes the latest version of DOSBox Staging v0.82.2. This config only details the changes from the default configuration. It is identical to the predecessor, Apache (Longbow) DOSBox config. The changes are as follows:

[sdl]
host_rate			= vrr
vsync				= off
presentation_mode		= vfr

[dosbox]
memsize				= 32
dos_rate				= 1000

[cpu]
cpu_cycles_protected 	= 200000
cycleup              	= 1000
cycledown            	= 1000

[voodoo]
voodoo				= false

[mouse]
dos_mouse_immediate	= true

[mixer]
reverb     			= medium
chorus     			= normal

[joystick]
joysticktype			= 4axis
timed				= false
swap34				= true
deadzone				= 0

[autoexec]
@echo off
mount c "D:\Games\Dos\Hind\hdd"
imgmount d "D:\Games\Dos\Hind\cd\Hind[SOS].iso" -t cdrom

c:
# cd di\hind
# hind
# exit

The [sdl], [dosbox] and [mouse] settings are suitable for high frame rate gaming as described in this article by Omniclyde. These settings aren't strictly required and can be omitted to use the default settings.

The [dosbox] memsize and [cpu] cpu_cycles_protected settings are identical to the preceding Apache (Longbow).

The cyclesup/cyclesdown settings are changed to an appropriate increment. The cpu_cycles_protected is set to a suitably high 200000.

Voodoo emulation isn't required and can be disabled.

The [mixer] settings enhance the music and audio. They are a personal preference and can be adjusted as desired.

In the [joystick] section, the [joysticktype], [timed] and [swap34] are suitable settings for my HOTAS (TM Warthog), however you may need to adjust these for your own joystick or HOTAS. [deadzone] is a personal preference and should be adjusted as desired.

The [autoexec] section mounts the hdd folder as the c: drive. The imgmount command mounts a cd-rom image as the d: drive. The disabled commands will change to the appropriate folder and run the game. The exit command will close DOSBox when the game is quit. Once installation and patching is complete these commands can be enabled.

Installation

All DOS versions should be installed from within DOSBox using the DOS installer app (install.exe) from the cd.

The only installation option is the install size which should be set to large/maximum. There are no graphics or sound options to set. The installer should complete without issue.

Patching

Depending on your version there may one or more patches to run. The DOS patches are file replacement patches can be extracted and files replaced in Win10 (which may be easier) than using DOSBox.

Once installation/patching is complete, the disabled [autoexec] commands in the DOSBox config can be enabled.

If the game fails to run after patching, it is recommended to delete the prefs.cfg file and then run the game. Graphics, sound and control preferences will need to be configured again in the Preferences menu.

Win95 version

The Win95 version is available with all releases except the digital release. At present there are no patches or mods to add Win95 support to DOS releases.

The cd or cd image needs to be mounted under Win10. The .iso image format is supported natively by Win10, but cue/bin image pairs may require 3rd party tools like DAEMON Tools or WinCDEmu to mount the image.

Each Hind release uses a 32-bit installer app, (setup.exe) on the cd/cd image. The installer should run without issue under Win10.

However, when asked to install DirectX components reply 'No'. DirectX components should not be installed.

Sold Out Software installation

The Sold Out Software release uses an earlier 16-bit installer app which is not supported by Win10. A recommended solution is to use winevdm/otvdm a tool to provide 16-bit app support on 64-bit Windows.

The winevdm/otvdm utilities are available at the winevdm GitHub repository, with the latest version (v.0.9.0 at time of writing) available on the releases page. The process is to:

Download the latest version (otvdm-v0.9.0.zip) and extract to a folder, (maybe a sub-folder under the Hind setup folder if you have one, see Game management).

Mount the cd image under Win10.

Run the otvdmw.exe utility and navigate to your mounted cd image and open the setup.exe installer app. Note: there is a Setup95.exe app, but this is a Sold Out Software app which allows Acrobat reader to be installed before running setup.exe.

Installation should run successfully, select no or cancel the installation when asked to install DirectX components.This occurs after files have been copied, which is the important part of the install.

Patching

This section covers patching with the v1.2 patch and the two 3Dfx Voodoo patches.

HIND v1.2: Win95 version patch

Only the original retail release should require this patch. This is a file replacement patch, replacing the hind95.exe file. The file can be extracted from the patch archive and replaced in Win10.

Win95 3Dfx version patch

Applying this patch is a bit involved as it uses a 32-bit installer and can run in Win10 but not successfully. Tests with various compatibility options have also failed.

Therefore the rather involved approach is to create a PCem virtual machine, copy the Hind installation and patches folders to the virtual machine, apply the patch and then copy the Hind installation folder back into Win10.

It has been suggested in other articles to keep a copy of a newly created PCem or 86Box virtual machine (VM), so it can be reused for other games or purposes and this is a scenario where having a VM can save huge amounts of time and effort.

As long as you have a PCem or 86Box virtual machine with a .vhd virtual hard disk image and running Win95, Win98 or Win98SE then it should patch without issue.

If you don't have a suitable PCem or 86Box virtual machine then I can highly recommend this YouTube video, 'PCem Windows 98 Setup (Pentium II +Voodoo 3, all files provided)' from PhilsComputerLab.

Once created, keep a copy, you never know when it may be useful to have a Win98 virtual machine for retro games!

To apply the patch:

Download and extract the patch (Hind_3dfx.zip) to a new folder (maybe a new subfolder under the Hind setup folder if you have one, see Game management).

Download and extract the common files (common_files.zip) to the same folder.

Shutdown the PCem/86Box virtual machine, if it is running. Mount the virtual hard disk (.vhd) file in Win10.

Copy the Hind installation folder and patch folder to the virtual hard disk.

Eject the virtual hard disk and run up the PCem/86Box virtual machine.

Run the patch installer (setup.exe) from the patch folder. The installer should search for and find the Hind installation folder and apply the patch. Once complete there should be a new hind_3dfx.exe file in the Hind installation folder.

Shutdown the virtual machine and mount the virtual hard disk (.vhd) file in Win10.

Replace the Hind installation folder in Win10 with the installation folder from the virtual hard disk, overwriting any files as required.

That concludes applying the 3Dfx Voodoo 1 patch.

3Dfx/Voodoo2 upgrade patch

As this patch is a file replacement patch the process is far simpler. To apply the patch:

Download and extract the patch (Hind_3dfxV2.zip) to a new folder (maybe a new subfolder under the Hind setup folder if you have one, see Game management).

Replace the hind95.exe file in the Hind installation folder with this new patch version.

That concludes applying the 3Dfx Voodoo 2 upgrade patch.

Wrapper configuration

Getting the Win95 version of Hind requires the use of graphics and sound wrappers for both DirectX and Glide.

DxWrapper

DxWrapper is used to wrap the DirectSound components. This is particularly important given the issues the game has with sound.

The latest version (v1.4.7900.25) should be used and is available from the DxWrapper GitHub releases. To install:

Download and extract DxWrapper (dxwrapper.zip) to a new folder.

Copy the following DxWrapper files to the Hind installation folder. Note: the Stub path is not important you just need to add the dsound.dll file:

Stub\dsound.dll
dxwrapper.dll

Download and extract the dxwrapper.ini in the below zip file, to the Hind installation folder:

This concludes the DxWrapper config.

dgVoodoo2

The dgVoodoo2 wrapper is used to wrap both DirectX and Glide components. The version used is dgVoodoo v2.86.4. It is available from the dgVoodoo2 GitHub releases. To install:

Download dgVoodoo2 (dgVoodoo2_86_4.zip) and extract to a new folder.

Copy the following dgVoodoo2 files to the Hind installation folder. Note: the paths are not important you just need to add the files:

dgVoodooCpl.exe
3Dfx\x86\Glide.dll
3Dfx\x86\Glide2x.dll
3Dfx\x86\Glide3x.dll
MS\x86\D3D8.dll
MS\x86\D3D9.dll
MS\x86\D3DImm.dll
MS\x86\DDraw.dll

Download and extract the dgVoodoo.conf in the below zip file, to the Hind installation folder:

Note: you will probably need to open dgVoodooCpl.exe and:

In the General section change the adapters to use.
In the Glide section change the resolution to a suitable setting for your setup.
In the Glide section the watermark is turned on for testing purposes, once confirmed working it can be turned off.

The following screenshot shows the dgVoodoo2 settings:

This concludes the dgVoodoo2 config.

Game configuration

The final step is the in-game configuration accessed from the Preferences menu option on the initial menu screen. The configuration options and suggested settings are slightly different for DOS and Win95 versions.

DOS version

The DOS preferences have a full set of configuration options as shown in the screenshot. Here are some points to note:

The Visual Detail can be increased to maximum.
Speech and Music can be enabled and Effects can be set to Full.

If the DOSBox config uses the default Sound Blaster 16 settings then the sound card should be auto-detected and sound/music should work. The Address, Interrupt and DMA will not be shown on the Preferences page (see screenshot).
The sound card settings in the prefs.cfg file, are shown below in bold:

...
Visual Detail=9
Sound DMA=-1
Sound Address=-1
Sound IRQ=-1
Sound Card=4
Sound effects level=0
Sound Speech=1
Sound effects=1
Sound music=1
UI Continuous Move=1
...

The control settings are appropriate for my 4-axis virtual controller, combining stick, throttle and pedals. This means the hat is not enabled (I set the hat with the HOTAS profiling software).

If you don't have pedals you may wish to experiment with a DOSBox joysticktype of fcs or ch, both of which are supported by Hind as the Thrustmaster FCS and Flightstick Pro options.
After making a control change, re-calibrate each axis by moving it to the extremes.

Win95 version

The Win85 preferences have a limited set of configuration options as shown in the screenshot. Here are some points to note:

With the 3D accelerated version visual detail is maximised and settings are not required.

Sound card settings are not required.

The control settings are appropriate for my 4-axis virtual controller, combining stick, throttle and pedals. The Flightstick Pro option allows the use of hat with my HOTAS, you may wish to test options to find the optimum setting.
After making a control change, re-calibrate each axis by moving it to the extremes.

Running

Before starting the Win95 version of Hind, make sure the cd/cd image is mounted otherwise you'll be taken to the head-to-head setup menu.

When run for the first time, the Preferences menu will be presented immediately. When leaving the Preferences menu you'll be taken straight to the Quickstart mission allowing the controller options to be tested.

Documentation

The Sold Out Software re-release has a copy of the manual in pdf format. It can be found on the cd in the manparts folder.

In-game manual

A rather useful facility offered by Hindis the ability to bring up a copy of the manual at any time, on menu screens or during flight, with <Shift> + <F1>. This includes a key reference!

Example videos

DOS v1.2 version running in DOSBox Staging

Win95 3Dfx version running in Win10

Finally

Credit and thanks go to the following:

dege for dgVoodoo2.
Elisha for DxWrapper.
Omniclyde for the DOSBox Staging high framerate gaming settings.
soggi for hosting the 3Dfx patches.
ataribaby for the GOG digital release v1.2 patch.

Udachnoy okhoty!