**********************************************
 *                                            *
 *  How to install this FS2004 Dornier 128-6  *
 *                                            *
 **********************************************


The package "do1286V5.zip" you downloaded is a substantial reprogramming, 
expansion and completely GMax-rebuilt model of previous versions intended 
for use solely in FS2004.
The first FS98 version I made of this aircraft registered as "D-IBUF" was as
it is used by the TU (Technical University) Braunschweig, 
Germany ("do1286V1.zip" and update "do1286u1.zip" at www.flightsim.com) 
and the same aircraft as it was in its original Dornier roll-out livery 
and state ("do1286V2.zip").
For FS2000 pro ("do1286V3.zip") and for FS2002 pro ("do1286V4.zip") 
both liveries are contained in one pack.
This Version 5 is again only as it is currently used by the 
TU (Technical University) Braunschweig.


Installation of this aircraft package 
========================================

Expand the complete content of this archive with Windows Explorer, 
Winzip, ZIP-it or another 32 bit unzipper with the option "restore to 
original directories" (or something similar) into your main 
Flight Simulator 9
directory or to any other folder you use for unzipping. In Windows Vista 
it may be necessary to answer the query that goes something like 
"integrate new folder "Aircraft" with current folder "Aircraft"? 
with "yes", same witht the other folders.

This will create the directory

DO_128-6

in your 
Flight Simulator 9/Aircraft
directory. It is filled with the following files and sub-directories:

Files:

Aircraft.cfg
DO 128-6_FS2004.air
DO 128-6 D-IBUF TU BS FS2K2 V1_notes.txt
DO_128-6_WHEELS_CHECK.htm
DO_128-6_WHEELS_REF.htm
do128-6P5.gif and do1286V5.gif
FILE_ID.DIZ
INSTALL.txt (this file)
INSTALLATION_Deutsch.txt (this file in German)

Sub-directories:

Documentation
 with the important documentation of this aircraft and its systems,
 "Do128-6_D-IBUF_Documentation.htm" (read it!) 
 and the following documents accompanying Glen Copeland's Radar System
 "F16 Air Show Tour Panel_V2 Instructions.pdf" 
 "Info.txt"
 "Legal Notice.txt"
 "RadarApproaches.doc"

Documentation\files
 contains all files used in the documentation, ending in "htm", "gif",
 "jpg" and "bmp"

model
 with "DO 128-6 D-IBUF FS2K2 v1.mdl" and "model.cfg"

panel
 with initially 9 files ending in ".gau"  as well as 3 in ".cab" 
 (keep them in there and do not decompress the cab files!)
 plus 12 bmp files, "hghb.txt" and "panel.cfg". After first loading the
 plane the .gau files will multiply into 19 gauges due to multiple usage
 in 2D- and VC-panels.

sound
 with 27 wav files plus "sound.cfg" and "Readme_LM_KASndEnhPck_v31.txt" 

texture
 with 27 bmp textures of various formats, mostly in DXT3 format


Additionally all wav files necessary for the gauges (1000Hz.wav, click.wav, 
Click3.wav, Click4.wav, HGHB_Click2.wav, HGHB_Click3.wav, hghb_rsw_cl1.wav,
hghb_rsw_cl2.wav, dfd_audiopanel.wav) 
should now reside in the main 
Flight Simulator 9/Sound 
directory. There is no need to overwrite these files if you should already 
have them.

In the main 
Flight Simulator 9/Effect 
folder the effect file "fx_CII_wing.fx" should reside.

The fueltotalizer gauge will create its own memory file 
"fueltotalizer.dat" in the root directory Flight Simulator 9 when first 
initialized by the panel. The same goes for a file called 
"do128-6_toebrakes.dat". By opening this file in Notepad you can 
change and save the toebrake exponent stored in there from the default of 
0.800000 (slightly progressive toebrake reaction relative to rudder 
or aileron input) more towards 1 which would be a completely linear 
toebrake response, or to a smaller value to yield finer toebrake 
reaction around the center - at the cost of more extreme 
progressiveness towards the edges of rudder or aileron input. Values 
greater than 1 mean a digressive response - strong toebrake reaction 
around the center with little to add at greater input. I humbly recommend 
the default value...


Aircraft operation 
====================

- Open/close main exit: press SHIFT + E
- Open/close cockpit doors: press SHIFT + E, let go of both and 
  immediately after press 2 (default cargo door key command)

One little but gravely important hint: BEFORE you attempt to start up
the aircraft READ and enjoy the documentation provided in
"Do128-6_D-IBUF_Documentation.htm", otherwise you may well feel
sorry for not having done so FAST!!! This is a rather realistic
turboprop simulation which is still unique in FS2004 and in some points 
fundamentally different from the default King Air 350, so make sure you
familiarize yourself with the few peculiarities of older turboprops
BEFRORE you ruin your engines with a hot start and possibly even set
them afire. After having read and understood the basic principles you
should be able to enjoy this aircraft and panel far more than by trial
and error (which is sure to come...).

Here a brief summary of what trouble you can get yourself into:
- Hot starts may fail the engines, possibly including a fire alarm.
- Overtorqueing the reduction gearbox of the propeller will eventually 
  result in catastrophic gearbox collapse and thus engine failure.
- Extending flaps while main exit is open or opening main exit while 
  flaps are extended will ruin the flaps, render them inoperable and 
  result in asymmetric lift and drag. Main Exit accidentally left 
  open during takeoff will also cause asymmetric drag and slam shut 
  at airspeeds exceeding 100 KIAS.
- A hard landing will not necessarily result in crash but may cause
  the landing gear to collapse (the model will stay intact,
  but the plane will scrape over the runway on it's belly).
- Hard breaking with insufficient backpressure on the elevator can 
  actually cause the plane to flip on it's back without causing a 
  crash, but only with a VERY small margin.
- Carefully flown it is possible to make an emergency water landing 
  with crash detection on, with enough time to spare to give you and 
  your virtual passengers a chance to get out before the plane sinks 
  and triggers a crash.

Most of these failures will require you to reload the plane in order 
to fix it again. Did I just say "most"? Should have been "all" :-)


Enjoy !


Mathias Elsaesser
***************************
Any comments (questions unanswered in the documentation, constructive 
criticism, praise?) please mail to (replace the typical words and their
surrounding blanks with the appropriate symbols, thanks to spam...)

dornier1286 at aol dot com

Released into the wild wild web on 25 August 2008