Jane's Longbow 2 Demo

The official demo version of Jane's Combat Simulations: Longbow 2. Read the readme.doc file for instructions.


Do not refresh or leave this page!

File Description

The official demo version of Jane's Combat Simulations: Longbow 2.

Read the readme.doc file for instructions.

Read More

Download 'lb2demo.exe' (28.05MB)

Longbow 2 Demo

Longbow 2
Welcome to the Longbow 2 demo.  Longbow 2 is the ground-breaking sequel to Jane’s AH-64D Longbow, 1996’s unanimous Flight Sim of the Year, putting you in the cockpit of the worlds most deadly attack helicopter.  Sporting the painstakingly accurate avionics and flight modeling of the original AH-64D Longbow, Longbow 2 adds the ability to fly the OH-58D Kiowa Warrior recon helicopter and the UH-60 Black Hawk utility helicopter (you can even man the Black Hawk’s door gunner position), as well as ground breaking visual technology including native support for 3DFX-Voodoo based accelerators, a dynamic campaign generator, and comprehensive cooperative and head to head multiplayer support via tcp/ip, lan or modem. This instant action demo will give you a taste of Longbow 2's award-winning combat with a host of user-definable options that let you tailor the experience to your personal gameplay preference.  See for yourself why Longbow 2 has been awarded "Flight Sim of the Year" honors from every major source in the industry.  If you like what you find in the demo, you'll be in for a real treat when you get your hands on the full version, which includes fully interactive tutorial missions, customizable single mission scenarios, unlimited instant action and two dynamic campaign environments.  Good Hunting!


Minimum System Requirements
Windows 95
Pentium 133mhz or faster (with or without 3DFX accelerators)
16 MB ram
170 MB of free, uncompressed hard drive space plus 30 MB free hard drive space for Windows swap file. (Minimum installation size)
4X CD-ROM drive
DirectX 5 compatible 2 MB PCI bus video card
MS compatible mouse
Microsoft DirectX compatible sound card

Recommended System Requirements
Pentium 200mhz or faster
32 MB ram
370 MB hard drive space
Windows95 compatible joystick, rudder, and throttle
3DFX Voodoo chipset based accelerator card

1. 	Copy the Longbow 2 demo file to its own directory (ie: C:\Lb2demo)
2.   Double click on lb2demo.exe.  The Longbow 2 demo is contained in a self-extracting zip file and will install all necessary files.

You must have DirectX version 5.0 installed to run the Longbow 2 demo.
1. 	In the folder in which the demo was installed, double-click on the file “demo.exe”

Direct3D Configuration
The Beta Longbow 2 Direct3D graphics engine makes use of an optional configuration file, d3d.cfg.  This configuration file must be placed in the same directory as the main directory containing lb2.exe.  This file contains several user-configurable options, some of which are required for certain cards Comments regarding the use of specific options is listed in the configuration text file.

The Beta Direct3D patch contains several files with the ".cfg" extension.  Each of these files corresponds to decent d3d.cfg settings for a given card.  The following table lists the chipset and the config file name for that chipset.  The config file will need to be copied to the d3d.cfg filename.

Chipset:			Config file name:
Riva 128		riva128.cfg
Rendition V2x00		rndv2x00.cfg
Permedia 2		perm2.cfg
ATI 3D Rage Pro		ragepro.cfg

Note that you are not required to use a config file, nor are you required to include a given option in a config file.  The config file is a text file containing simple <variable>=<value> statements.  Lines beginning with the pound sign, "#", will be considered comments.  The config file used by the Direct3D engine must be named "d3d.cfg".  You may copy the config file for your chipset to d3d.cfg with the following instruction:

copy <config file name> d3d.cfg

III.  CARD-SPECIFIC INFORMATION (including information on cards not supported)

The following lists additional information regarding operation on specific chipsets:

Riva 128:
The Riva 128 chipset does not support Gouraud-shaded transparency.  It emulates this feature through a method that does not look appealing in some circumstances.  Within the Virtual Cockpit, the emulated transparency makes the rotor blades look less than realistic.  Furthermore, the STB Velocity 128 apparently does not support the early DirectDraw interfaces correctly.  The on-base portion of the game does not draw fullscreen correctly, rendering it nearly unplayable.  Hopefully STB corrects their drivers to fix this.

Permedia 2:
Permedia 2 does not support a feature used by Longbow 2 to create the Pilot Night Vision System (PNVS).  If the PNVS is used at night, the terrain will look brighter, but will not be green-shaded.

ATI 3D Rage Pro:
The drivers for this chipset are in a state of flux that may or may not be compatible with the Beta release of Longbow 2 Direct3D.  Currently, certain operations are failing, leading to the drop-out of certain special effects.  Beta 3D Rage Pro drivers I have been working with render the game unplayable.  Hopefully the drivers settle out in such a way that the 3D Rage Pro will work just fine; however, no promises can be made at this time regarding the results you will achieve.

PowerVR PCX2:
Although there are some benefits to the architecture supported by this card, the PowerVR architecture places restrictions on texture usage that are incompatible with the Longbow 2 render pipeline.  You may be able to get it to run partially; however, no promises are made over the results you will achieve.


The following is a list of option settings recommended to improve your gaming experience while running under Direct3D.  These options are located by selecting the options menu, choosing "Graphics", then choosing "Custom Detail..."

A.  Horizon Distance:  Select third notch from left.  This will significantly improve frame rate.

B.  Deselect Sky Texture.  With the horizon distance set near, fogging gives the appearance of a perpetual cloudy day.  Deselecting sky texture provides a blended blue sky.  This doesn't provide any performance gains.

For the best performance, select "Low" on the main graphics options page.  This automatically adjusts option settings in order to achieve optimal frame rate.


The following is a list of bugs you may experience.  The development team is aware of these bugs, so there is no need to report them if you experience one of them during gameplay.

A.  FLIR terrain/object color incorrect:

In some situations on some cards, the terrain color will show up incorrectly in the FLIR camera mode for the TADS.  The problem may only show up when switching between white-hot and black-hot mode.

B.  Tutorial palette colors incorrect:

On some cards during tutorial exercises, the colors shown in the cockpit may not be correct (noticeably for the IHADSS symbology).  The problem becomes worse if you return from the options menu or select cancel from the quit or exit dialog.  The colors will revert to normal if you fire your cannon (note: the tutorial doesn't always let you fire the cannon when the instructor is talking).

C.  In-flight mouse cursor colors incorrect:

In some instances, the mouse cursor for the in-flight systems may be set to incorrect colors.

Read More

Comments on this File

There are no comments yet. Be the first!

Share This File
Embed File