~ FLIGHT031.A[ FLIGHT031.A]BACKUP $SRC:KITINSTAL.COM,$SRC:NOTIFY_DEVELOPMENT.COM,$HANGAR:HANGARS_MIN.DAT,$HANGAR:HANGARS_FULL.DAT,$WORLD:WORLDS_MIN.DAT,$WORLD:WORLDS_FULL.DAT,$DOC:[031]FLIGHT031.RELEASE_NOTES,$DOC:[031]FLIGHT031.INSTALLATION_NOTES,$SRC:FLIGHT.CLD,$KIT:FLT$UID.UID,$DOC:[DECWINDOWS-HELP]FLT$HELP.HLB,$DOC:[DCL-HELP]FLIGHT.HLP $KIT:FLIGHT031.A/SAVE/NOLOG/VERIFY FLIGHT  x`sA5.5 _LHOTSE::  _LHOTSE$DKB0: V5.5-2 ~  )*[FLIGHT.FLIGHT.REFERENCE]KITINSTAL.COM;11+, .E/ 4EC(- 0123KPWOF560^7 fw`s89@)x sGHJx$ !6$ ! Installation procedure (VMSINSTAL) for FLIGHT V3.1$ !$ on warning then continue$ on error then exit*$ on control_y then vmi$callback control_y$ ! $ true = 1 $ false = 0$ authorize = "$authorize"$ ncp = "$ncp"$ ncl = "$ncl"$ !,$ ! If network present, turn on network flag$ !$ network = "ON"7$ if f$trnlnm("SYS$NODE") .eqs. "" then network = "OFF"$ !5$ ! Test to see if we're running DECnet/OSI (Phase V)$ !$ osi = "FALSE">$ if f$search("SYS$SYSTEM:NCL.EXE") .nes. "" then osi = "TRUE"$ !4$ ! Check the parameters for VMSINSTAL functions....$ !5$ if p1 .eqs. "VMI$_INSTALL" then goto FLIGHT_INSTALL$ exit vmi$_unsupported$ !$FLIGHT_INSTALL:$ !8$ ! find out which architecture (VAX, ALPHA) we're on... $ arch == ""/$ set message/notext/noseverity/noident/nofacil$ arch == f$getsyi("arch_name")%$ set message/text/severity/ident/facO$ ! If the version of VMS is too old to have implemented f$getsyi("arch_name"),,$ ! then it can't possibly be an AXP system.$ !%$ if arch .eqs. "" then arch == "VAX"<$ write sys$output "***************************************"H$ write sys$output "FLIGHT V3.1 being installed on ''arch' architecture"<$ write sys$output "***************************************"$!$ install_simulator == false$ install_server == false$ install_examples == false$ install_developer == false$ install_hangars == false$ install_worlds == false$ install_full_hangars == false$ install_min_hangars == false$ install_full_worlds == false$ install_min_worlds == false$ !;$ ! Set up query/install environment for hangars and worlds$ !=$ default_hangar = "SYS$LIBRARY:FLT$CIVILIAN_AIRCRAFT.HANGAR"/$ open/read hangarfile vmi$kwd:hangars_full.dat$read_another_full_hangar:@$ read/end=fullhangars_done/err=fullhangars_done hangarfile lineH$ if f$elem(0," ",line) .nes. "Total" then goto read_another_full_hangar*$ hangars_full_blocks = f$elem(4," ",line)$fullhangars_done:$ close hangarfile$.$ open/read hangarfile vmi$kwd:hangars_min.dat$read_another_min_hangar:>$ read/end=minhangars_done/err=minhangars_done hangarfile lineG$ if f$elem(0," ",line) .nes. "Total" then goto read_another_min_hangar)$ hangars_min_blocks = f$elem(4," ",line)$minhangars_done:$ close hangarfile$!$! Now setup info for worlds$!1$ default_world = "SYS$LIBRARY:FLT$PACIFIC.WORLD"-$ open/read worldfile vmi$kwd:worlds_full.dat$read_another_full_world:=$ read/end=fullworlds_done/err=fullworlds_done worldfile lineG$ if f$elem(0," ",line) .nes. "Total" then goto read_another_full_world)$ worlds_full_blocks = f$elem(4," ",line)$fullworlds_done:$ close worldfile$,$ open/read worldfile vmi$kwd:worlds_min.dat$read_another_min_world:;$ read/end=minworlds_done/err=minworlds_done worldfile lineF$ if f$elem(0," ",line) .nes. "Total" then goto read_another_min_world($ worlds_min_blocks = f$elem(4," ",line)$minworlds_done:$ close worldfile($ worlds_min_blocks = f$elem(4," ",line)$ !Y$ ! A full-worlds installation is really a superset of the worlds_full and the worlds_min7$ ! installations, so we need to add these two numbers.$ !*$ full_int = f$integer(worlds_full_blocks)($ min_int = f$integer(worlds_min_blocks)3$ worlds_full_blocks = f$string(full_int + min_int)$ !$ !$ !>$ ! Must be VMS V5.4 or later for VAX, 1.5 or later for Alpha.$ !$ if arch .eqs. "VAX"$ then<$ vmi$callback check_vms_version flight$vms_version 054$ else<$ vmi$callback check_vms_version flight$vms_version 015$ endifd$ if .not. flight$vms_version then vmi$callback message e badvms "This kit requires VMS Version 5.4"4$ if .not. flight$vms_version then exit vmi$_failure$H$ ! Now that we know that the arch and version are OK, we need to check I$ ! for a prerequisite: On Alpha systems, we need PAS$RTL. V1.5 systems8$ ! do not come with it by default, so we need to check.$ if arch .eqs. "Alpha" $ then0$ pasrtl = f$search("SYS$LIBRARY:PAS$RTL.EXE")$ if pasrtl .eqs. ""$ thenN$ write sys$output "This kit requires sys$library:pas$rtl.exe in order to"J$ write sys$output "function properly. This component is part of the"O$ write sys$output "Pascal compiler for AXP. You need to install at least"U$ write sys$output "the RTL portion of that kit for FLIGHT to function properly."a$ vmi$callback ask install_anyway "Do you want to continue installing FLIGHT anyway?" "YES" B4$ if .not. install_anyway then exit vmi$_failure $ endif$ endif$ !$ ! Purging files okay ?$ !$ vmi$callback set purge ask$ !$BEGIN_INSTALLATION:$ !$ type sys$input7The FLIGHT kit is composed of the following components:P The FLIGHT Simulator, which is the component of FLIGHT which allows you to run an interactive simulation.L The FLIGHT Server, which is required for all simulations. However, if youK have access to any system with the FLIGHT Server installed on it, you mayH use that Server and choose not to install the Server component on your system.P The FLIGHT Developer Kit, which is the software used to create and modify your& own aircraft and world environments.N The FLIGHT Examples, which is a collection of sample aircraft and instrumentM sources, as well as the standard FLIGHT instruments and weapons as compiled hangars.I If you choose the Developer Kit or the Simulator component, you will beH presented with a choice of a full set of hangars or a minimum set for " systems with tight disk storage.P If you choose the Developer Kit or the Server component, you will be presentedI with a choice of a full set of worlds or a minimum set for systems with tight disk storage.K If you choose the Developer Kit or the Simulator component, you will also% receive the FLIGHT World Previewer.R$ vmi$callback ask install_full_kit "Do you want to install the entire kit" "NO" B$ !5$ if .not. install_full_kit then goto ASK_EACH_OPTION$ !$ install_simulator == true$ install_server == true$ install_examples == true$ install_developer == true$ install_hangars == true$ install_worlds == true$ install_full_hangars == true$ install_full_worlds == true$ install_min_worlds == true$ ! $ goto HAVE_INSTALLATION_OPTIONS$ !$ASK_EACH_OPTION:$ !$ write sys$output " "S$ vmi$callback ask install_simulator "Do you want to install the simulator" "YES" BP$ vmi$callback ask install_server "Do you want to install the server" "YES" BX$ vmi$callback ask install_examples "Do you want to install the source examples" "NO" BV$ vmi$callback ask install_developer "Do you want to install the developer kit" "NO" B$ !n$ if install_simulator .or. install_server .or. install_examples .or. install_developer then goto SHOW_OPTIONS$ !T$ vmi$callback message w nooptions "You have not selected any components of the kit"\$ vmi$callback ask ask_separate "Do you want to respecify the options that you want" "YES" B+$ if ask_separate then goto ASK_EACH_OPTION$ !$ exit vmi$_failure$ !$SHOW_OPTIONS:$ !$ write sys$output " "?$ write sys$output "You have selected the following components"$ write sys$output " "9$ if install_simulator then write sys$output " Simulator"6$ if install_server then write sys$output " Server"?$ if install_examples then write sys$output " Source Examples"?$ if install_developer then write sys$output " Developer's Kit"$ write sys$output " "$ !4$ vmi$callback ask selection_ok "Is this OK" "YES" B$ !4$ if .not. selection_ok then goto BEGIN_INSTALLATION$ !$ !^$ if .not. install_simulator .and. .not. install_developer then goto HANGAR_SELECTION_COMPLETE$ !&$ ! Find out which hangars are wanted$ !=$ if install_full_hangars then goto HANGAR_SELECTION_COMPLETE$ !$ type sys$inputPPre-compiled hangars are provided with FLIGHT. Hangars contain the objects withOwhich you perform a simulation. They are the aircraft, vehicles, weapons, etc.BYou have a choice of a full complement of hangars, which takes up $ write sys$output f$fao(-A"!AS blocks, or a minimum set, which would take up !AS blocks.",-'hangars_full_blocks,hangars_min_blocks)$ !$HANGAR_ASK_LOOP:$ !$ install_hangars == false$ install_full_hangars == false$ !$ write sys$output " "m$ vmi$callback ask install_full_hangars "Do you want all the hangars (''hangars_full_blocks' blocks)" "YES" B9$ if .not. install_full_hangars then goto ASK_MIN_HANGARS$ !$ install_full_hangars == true$ !$ goto VERIFY_HANGAR_SELECTION$ !$ASK_MIN_HANGARS:$ !o$ vmi$callback ask install_min_hangars "Do you want the minimum hangars (''hangars_min_blocks' blocks)" "YES" B$VERIFY_HANGAR_SELECTION:$ !]$ if .not. install_min_hangars .and. .not. install_full_hangars then goto NO_HANGARS_SELECTED$ !$ install_hangars == true$ ! $ goto HANGAR_SELECTION_COMPLETE$ !$NO_HANGARS_SELECTED:$ !k$ vmi$callback message w hangarwarning "some components of FLIGHT cannot be run without access to a hangar"_$ vmi$callback ask retry "Do you want to respecify the hangars to place on your system" "YES" b$$ if retry then goto HANGAR_ASK_LOOPM$ vmi$callback message i nohangars "no hangars will be placed on your system" $ goto HANGAR_SELECTION_COMPLETE$ !$HANGAR_SELECTION_COMPLETE:$ !Z$ if .not. install_server .and. .not. install_developer then goto WORLD_SELECTION_COMPLETE$ !$ !%$ ! Find out which worlds are wanted$ !;$ if install_full_worlds then goto WORLD_SELECTION_COMPLETE$ !$ type sys$inputOPre-compiled worlds are provided with FLIGHT. Worlds define the environment inPwhich you may perform a simulation. You may install a full complement of worlds$ write sys$output F$FAO(-O"which would take !AS blocks, or a minimum set, which would take !AS blocks.",-%worlds_full_blocks,worlds_min_blocks)$ !$WORLD_ASK_LOOP:$ !$ install_worlds == false$ install_full_worlds == false$ install_min_worlds == false$ !$ write sys$output " "j$ vmi$callback ask install_full_worlds "Do you want all the worlds (''worlds_full_blocks' blocks)" "YES" B7$ if .not. install_full_worlds then goto ASK_MIN_WORLDS $ !$ install_full_worlds == truek$ install_min_worlds == true$ !s$ goto VERIFY_WORLD_SELECTIONz$ ! $ASK_MIN_WORLDS:$ !$$ write sys$output " "l$ vmi$callback ask install_min_worlds "Do you want the minimum worlds (''worlds_min_blocks' blocks)" "YES" B$ !$VERIFY_WORLD_SELECTION:$ !rZ$ if .not. install_min_worlds .and. .not. install_full_worlds then goto NO_WORLDS_SELECTED$ !"$ install_worlds == true$ !h$ goto WORLD_SELECTION_COMPLETEf$ !o$NO_WORLDS_SELECTED:$ ! i$ vmi$callback message w worldwarning "some components of FLIGHT cannot be run without access to a world"o^$ vmi$callback ask retry "Do you want to respecify the worlds to place on your system" "YES" b#$ if retry then goto WORLD_ASK_LOOPrK$ vmi$callback message i noworlds "no worlds will be placed on your system" $ goto WORLD_SELECTION_COMPLETEg$ !($WORLD_SELECTION_COMPLETE:$ ! $HAVE_INSTALLATION_OPTIONS: $ ! 9$ if .not. install_simulator then goto NO_SIMULATOR_CHECK*$ !*/$ if install_server then goto NO_DEFAULT_SERVERp$ !L$ type sys$inputF Because you have decided to install the simulator but not the FLIGHTFserver, you must always specify a remote node as the FLIGHT server forEany given simulation run. If you attempt to use the local machine as:the FLIGHT server, you will receive the following message:?"%SYSTEM-F-NOSUCHOBJ, network object is unknown at remote node"t$ASK_FOR_DEFAULT_SERVER:f$ vmi$callback ask server "What node do you want to be the default FLIGHT server for your system" "" s5$ if server .eqs. "" then goto ASK_FOR_DEFAULT_SERVERA$ !$NO_DEFAULT_SERVER:i$ !i$NO_SIMULATOR_CHECK:$ !a$ !t$ !u3$ if .not. install_server then goto NO_SERVER_CHECKr$ !e$ server_account_exists = false $ server_object_exists = false$ server_account_uic == ""$ !r4$ password1 = f$cvtime(f$time(),,"TIME")-":"-":"-"."$ !l0$ ! See if the FLT$SERVER account already exists$ !a $ set noon$ vmi$no_error($ define/user sys$output vmi$kwd:uic.tmpm$ if f$trnlnm("sysuaf") .eqs. "" then define/user sysuaf 'f$parse("sysuaf","sys$system:.dat",,,"SYNTAX_ONLY")as$ if f$trnlnm("netproxy") .eqs. "" then define/user netproxy 'f$parse("netproxy","sys$system:.dat",,,"SYNTAX_ONLY")!$ authorize show/brief flt$serverP$ set on$ !=$ open/read/error=NO_SERVER_ACCOUNT temp_file vmi$kwd:uic.tmpu+$ read/end=NO_SERVER_ACCOUNT temp_file linel+$ read/end=NO_SERVER_ACCOUNT temp_file line +$ read/end=NO_SERVER_ACCOUNT temp_file linef@$ server_account_uic == f$edit(f$extract(37,13,line),"COLLAPSE")$ server_account_exists = true$ !p$NO_SERVER_ACCOUNT:$$ close/nolog temp_file_ $ delete/nolog vmi$kwd:uic.tmp;*$ !s4$ password2 = f$cvtime(f$time(),,"time")-":"-":"-"."W$ server_account_password = "''password2'" + "''f$getjpi("","CPUTIM")'"+ "''password1'"4$ !l6$ if server_account_exists then goto ACCOUNT_COMPLETED$ !kV$ ! No server account exists. Get a UIC from the user so we can create a new account.$ !d$ type sys$inputP In order to make sure that the FLIGHT server runs correctly, this installationPprocedure will create an account for the server. This FLT$SERVER account has noMspecial privileges and is set up only for the operation of the FLIGHT server.M$ !o $ASK_FOR_UIC:,$ !oe$ vmi$callback ask server_account_uic "Enter UIC for server account (include brackets)" "[376,366]" sv$ !r $ set noon$ vmi$no_error($ define/user sys$output vmi$kwd:uic.tmpm$ if f$trnlnm("sysuaf") .eqs. "" then define/user sysuaf 'f$parse("sysuaf","sys$system:.dat",,,"SYNTAX_ONLY")ss$ if f$trnlnm("netproxy") .eqs. "" then define/user netproxy 'f$parse("netproxy","sys$system:.dat",,,"SYNTAX_ONLY")e*$ authorize show/brief 'server_account_uic$ set on$ !y8$ open/read/error=UIC_NOT_USED temp_file vmi$kwd:uic.tmp&$ read/end=UIC_NOT_USED temp_file lineP$ vmi$callback message w uisinuse "''server_account_uic'" + " is already in use"$ server_account_uic == ""$ !n$UIC_NOT_USED:$ close/nolog temp_filee $ delete/nolog vmi$kwd:uic.tmp;*6$ if server_account_uic .eqs. "" then goto ASK_FOR_UIC$ !e$ACCOUNT_COMPLETED: $ !r-$ ! Check to see if FLT$SERVER object existse$ ! $ set noon$ vmi$no_error($ define/user sys$output vmi$kwd:ncp.tmp$ if osi$ then>$ NCL SHOW NODE 0 SESSION CONTROL APPLICATION "FLT$SERVER" $ else$ ncp list object flt$server $ endif$ set on$ !.A$ open/read/error=OBJECT_CHECK_COMPLETE temp_file vmi$kwd:ncp.tmp $ ! $READ_LOOP:e$ !y/$ read/end=OBJECT_CHECK_COMPLETE temp_file lineGI$ if f$locate("FLT$SERVER", line) .eq. f$length(line) then goto READ_LOOPh$ server_object_exists = trueh$ !G$OBJECT_CHECK_COMPLETE:e$ !o$ close/nolog temp_filew$ ! $NO_SERVER_CHECK:c$ !s$ !t7$ if .not. install_examples then goto NO_EXAMPLES_CHECKm$ !oI$ examples_directory == f$trnlnm("VMI$ROOT") + "[SYSHLP.EXAMPLES.FLIGHT]"sZ$ if f$trnlnm("FLT$EXAMPLES") .nes. "" then examples_directory == f$trnlnm("FLT$EXAMPLES")$ !$ type sys$inputI The example sources may be placed anywhere on your system. The logicalLname FLT$EXAMPLES will be defined to point at this location. In response to>the following prompt, supply a full device and directory path.K If the specified directory does not exist, this procedure will create it.yl$ vmi$callback ask examples_directory "Where should the example sources be placed" "''examples_directory'" s$ !a$NO_EXAMPLES_CHECK:o$ ! $ !m$ !h$ type sys$inputG All questions required for installation of FLIGHT have been answered.eFInstallation will take up to 30 more minutes based on the installationoptions you have selected.$ !e$ !$DEFAULT_SELECTION_COMPLETE:$ !r]$ ! Find out how much disk space we need to put the necessary save sets on this system. ThataX$ ! should be the maximum space we need. Initializing disk_space to 50 is just a hedge.$ !l$ disk_space = 50 $ !A_$ if install_simulator .or. install_developer then disk_space = disk_space + 1512 ! Saveset Br_$ if install_simulator then disk_space = disk_space + 2457 ! Saveset C__$ if install_server then disk_space = disk_space + 411 ! Saveset DH_$ if install_developer then disk_space = disk_space + 3087 ! Saveset Ia$ if install_full_hangars R$ then disk_space = disk_space + f$integer(hangars_full_blocks) ! Saveset Gm$ else if install_min_hangars then disk_space = disk_space + f$integer(hangars_min_blocks) ! Saveset E $ endif $ if install_full_worlds iS$ then disk_space = disk_space + f$integer(worlds_full_blocks) ! Saveset Hlm$ else if install_min_worlds then disk_space = disk_space + f$integer(worlds_min_blocks) ! Saveset F$$ endifm_$ if install_examples then disk_space = disk_space + 3024 ! Saveset Jr$ !DD$ vmi$callback check_net_utilization flight$enough_room 'disk_space'$ !t$ if .not. flight$enough_room then vmi$callback message e noroom "The components you have selected require ''disk_space' free disk blocks"4$ if .not. flight$enough_room then exit vmi$_failure$ !$ ! Start installing thingsr$ !yN$ if .not. install_simulator .and. .not. install_developer then goto NO_COMMON$ !i[$ vmi$callback provide_file flight$ flt$uid.uid vmi$root:[decw$defaults.user] ;$ vmi$callback provide_dcl_command flight.cld;$ vmi$callback provide_dcl_help flight.hlp $ !o $ vmi$callback restore_saveset B$ !A.$ archfile = arch + "_flt$world_previewer.exe"<$ rename vmi$kwd:'archfile vmi$kwd:flt$world_previewer.exe[$ vmi$callback provide_image flight$ flt$world_previewer.exe vmi$root:[sysexe]A[$ vmi$callback provide_file flight$ flt$previewer_keymap.dat vmi$root:[syslib]I$ ! $NO_COMMON:i$ ! 3$ if .not. install_simulator then goto NO_SIMULATORr$ ! $ vmi$callback restore_saveset C$ ! 4$ if install_server then goto NO_ADDITION_TO_STARTUP=$ open/append simulator_startup vmi$kwd:simulator_startup.com `$ write simulator_startup "$ ! Define the logical stating the server node to use as a fallback"$ write simulator_startup "$ !"rT$ write simulator_startup "$ define/system flt$server " + f$edit(server,"LOWERCASE")$ write simulator_startup "$ !" $ close simulator_startup'$ !r$NO_ADDITION_TO_STARTUP:$ !P$ vmi$callback message i simulator "simulator files being placed on your system"$ !a($ archfile = arch + "_flt$simulator.exe"7$ rename vmi$kwd:'archfile vmi$kwd:flt$simulator.exe;k[$ vmi$callback provide_image flight$ flt$simulator.exe vmi$root:[sysexe][$ vmi$callback provide_file flight$ flt$keymap.dat vmi$root:[syslib]a[$ vmi$callback provide_file flight$ flt$keymap.ps vmi$root:[syshlp]E$ !O$NO_SIMULATOR:$ !_$ !R$ !E-$ if .not. install_server then goto NO_SERVERr$ !" $ vmi$callback restore_saveset D$ ! J$ vmi$callback message i server "server files being placed on your system"$ !t%$ archfile = arch + "_flt$server.exe"S3$ rename vmi$kwd:'archfile vmi$kwd:flt$server.exe;lQ$ vmi$callback provide_image flight$ flt$server.exe vmi$root:[sysexe]_[$ vmi$callback provide_file flight$ flt$server.com vmi$root:[sysexe] $ ! 6$ if server_account_exists then goto NO_ACCOUNT_CREATE$ ! S$ vmi$callback message i creacc "creating account FLT$SERVER for the FLIGHT server"Wj$ vmi$callback create_account FLT$SERVER "/own=""FLIGHT server""/uic=''server_account_uic'/account=decnet"O$ vmi$callback update_account FLT$SERVER "/password=''server_account_password'"fe$ vmi$callback update_account FLT$SERVER "/pwdminimum=''f$string(f$length(server_account_password))'"hc$ vmi$callback update_account FLT$SERVER "/lgicmd=nl:/device=sys$sysdevice:/directory=[flt$server]"f$ vmi$callback update_account FLT$SERVER "/privilege=(noall,tmpmbx,netmbx)/defp=(noall,tmpmbx,netmbx)"9$ vmi$callback update_account FLT$SERVER "/pgflquo=15000"ov$ vmi$callback update_account FLT$SERVER "/flag=(restricted,nodisuser)/network/nobatch/nointeractive/prclm=0/maxjob=0"$ ! ^$ vmi$callback create_directory user sys$sysdevice:[flt$server] "/owner=''server_account_uic'"$ !z$NO_ACCOUNT_CREATE:D$ ! P$ if server_object_exists .and. server_account_exists then goto NO_OBJECT_CREATE$ !mM$ vmi$callback message i object "defining new network object for your system":$ !r$ if osi$ then$ !n$ ! Set the dynamic informationw$ ! #$ @vmi$root:[sysmgr]net$configure -  application_add -e "FLT$SERVER" - "FLT$SERVER" - T[ "{name = flt$server, number = 0}||sys$system:flt$server.com|true|true|true|true|true||" -o 1G$ else$ ncp define object flt$server number 0 file sys$system:flt$server.com proxy out user flt$server password 'server_account_password!$ ncp set object flt$server allr$ endifa$ !k$NO_OBJECT_CREATE:$ !o $NO_SERVER:p$ ! $ !u$ !t3$ if .not. install_developer then goto NO_DEVELOPERS$ !I $ vmi$callback restore_saveset I$ !OT$ vmi$callback message i developer "developer kit files being placed on your system"$ !a.$ archfile = arch + "_flt$hangar_compiler.exe"<$ rename vmi$kwd:'archfile vmi$kwd:flt$hangar_compiler.exe;Z$ vmi$callback provide_image flight$ flt$hangar_compiler.exe vmi$root:[sysexe],$ archfile = arch + "_flt$hangar_editor.exe":$ rename vmi$kwd:'archfile vmi$kwd:flt$hangar_editor.exe;X$ vmi$callback provide_image flight$ flt$hangar_editor.exe vmi$root:[sysexe]-$ archfile = arch + "_flt$world_compiler.exe"a;$ rename vmi$kwd:'archfile vmi$kwd:flt$world_compiler.exe;IY$ vmi$callback provide_image flight$ flt$world_compiler.exe vmi$root:[sysexe] +$ archfile = arch + "_flt$world_editor.exe"_9$ rename vmi$kwd:'archfile vmi$kwd:flt$world_editor.exe;tW$ vmi$callback provide_image flight$ flt$world_editor.exe vmi$root:[sysexe]eP$ vmi$callback provide_file flight$ flt$default.cfg vmi$root:[syslib]\$ vmi$callback provide_file flight$ flt$lfe.uid vmi$root:[decw$defaults.user]P$ vmi$callback provide_file flight$ flt$hangar.env vmi$root:[syslib]$ !i$NO_DEVELOPER:$ !s$ !s$ !"5$ if .not. install_full_hangars then goto MIN_HANGARSr$ ! $ vmi$callback restore_saveset G$ !a$ ! Do the hangarsy$ !.$ !,$ write sys$output " "|$ vmi$callback message i defaulthangar "the default hangar file on your system will be ''f$edit(default_hangar,""UPCASE"")'"$ !A$ type sys$inputA To change the default hangar file on your system, edit the fileVSYS$STARTUP:FLT$STARTUP.COM.K$ vmi$callback message i hangars "hangar files being placed on your system"e$ ! $ !e$ !p2$ open/read hangarlist vmi$kwd:hangars_full.datB$ read/end=hangars_done/err=hangars_done hangarlist hangar_line$INSTALL_NEXT_FULL_HANGAR:)$ hangar_line = f$elem(0," ",hangar_line)'#$ if hangar_line .eqs. "" .or. -'1 hangar_line .eqs. "Total" then goto hangars_doneUS$ hangar_symbol == f$parse(hangar_line,,,"NAME",)+f$parse(hangar_line,,,"TYPE",)cH$ vmi$callback provide_file flight$ 'hangar_symbol' vmi$root:[syslib]>$ write sys$output "Providing hangar file ''hangar_symbol'"B$ read/end=hangars_done/err=hangars_done hangarlist hangar_line"$ goto INSTALL_NEXT_FULL_HANGAR$ $ !o $MIN_HANGARS: 3$ if .not. install_min_hangars then goto NO_HANGARS$ !$ $ vmi$callback restore_saveset E$ !U$ ! Do the hangars $ !u$ !a$ write sys$output " "|$ vmi$callback message i defaulthangar "the default hangar file on your system will be ''f$edit(default_hangar,""UPCASE"")'"$ !f$ type sys$inputA To change the default hangar file on your system, edit the file SYS$STARTUP:FLT$STARTUP.COM.K$ vmi$callback message i hangars "hangar files being placed on your system"e$ !a$ !t1$ open/read hangarlist vmi$kwd:hangars_min.datDB$ read/end=hangars_done/err=hangars_done hangarlist hangar_line$INSTALL_NEXT_MIN_HANGAR:s1$ if f$elem(0," ",hangar_line) .eqs. "" .or. -"? f$elem(0," ",hangar_line) .eqs. "Total" then goto hangars_done S$ hangar_symbol == f$parse(hangar_line,,,"NAME",)+f$parse(hangar_line,,,"TYPE",)o2$ hangar_name == f$parse(hangar_line,,,"NAME",)@$ rename vmi$kwd:'hangar_symbol vmi$kwd:'hangar_name'.HANGAR;M$ vmi$callback provide_file flight$ 'hangar_name'.hangar vmi$root:[syslib]NC$ write sys$output "Providing hangar file ''hangar_name'.HANGAR"cB$ read/end=hangars_done/err=hangars_done hangarlist hangar_line!$ goto INSTALL_NEXT_MIN_HANGAR $ $HANGARS_DONE:$ close hangarlist$ ! 3$ write sys$output "Creating hangar startup script"f7$ open/append hangar_startup vmi$kwd:hangar_startup.com $ write hangar_startup "$ !"[$ write hangar_startup "$ ! Define the logical defining the default hangar on this system"R$ write hangar_startup "$ !"E$ write hangar_startup "$ define/system flt$hangar " + default_hangarc$ write hangar_startup "$ !"$ close hangar_startup$ ! $NO_HANGARS:$ !EM$ ! We need to get rid of some old, obsolete hangars which are not compatible :$ ! with this version of FLIGHT, and could cause problems.$ ! $ type sys$input= Obsolete hangars from previous installations are now beingt4 deleted from your system. Please ignore possible, "file does not exist" warning messages...$ !dA$ vmi$callback delete_file sys$library:flt$air_superiority.hangaraC$ vmi$callback delete_file sys$library:flt$close_air_support.hangaraD$ vmi$callback delete_file sys$library:flt$combat_helicopters.hangarA$ vmi$callback delete_file sys$library:flt$combat_vehicles.hangaro>$ vmi$callback delete_file sys$library:flt$interception.hangar>$ vmi$callback delete_file sys$library:flt$interdiction.hangar$ !$ !e$ !3$ if .not. install_full_worlds then goto MIN_WORLDSw$ ! $ vmi$callback restore_saveset H$ ! $ ! Do the worlds$ ! I$ vmi$callback message i worlds "world files being placed on your system"o$ !s$ ! $ write sys$output " "y$ vmi$callback message i defaultworld "the default world file on your system will be ''f$edit(default_world,""UPCASE"")'"s$ !s$ type sys$input@ To change the default world file on your system, edit the fileSYS$STARTUP:FLT$STARTUP.COM.$ !i-$ open/read worldlist vmi$kwd:worlds_full.dataE$ read/end=full_worlds_done/err=full_worlds_done worldlist world_line $ ! $INSTALL_NEXT_FULL_WORLD:a$ !f0$ if f$elem(0," ",world_line) .eqs. "" .or. -B f$elem(0," ",world_line) .eqs. "Total" then goto full_worlds_doneP$ world_symbol == f$parse(world_line,,,"NAME",)+f$parse(world_line,,,"TYPE",)G$ vmi$callback provide_file flight$ 'world_symbol' vmi$root:[syslib]c<$ write sys$output "Providing world file ''world_symbol'"H$ read/end=full_worlds_done/err=full_worlds_done worldlist world_line!$ goto INSTALL_NEXT_FULL_WORLDa$ ! $FULL_WORLDS_DONE:$ close worldlistn$ $MIN_WORLDS:1$ if .not. install_min_worlds then goto NO_WORLDSr$ !D $ vmi$callback restore_saveset F$ !f\$ ! If we're falling through from full world installation, skip the min_world default setup.$ !o4$ if install_full_worlds then goto start_min_worlds $ !f$ ! Do the worlds$ !o$ !i$ write sys$output " "y$ vmi$callback message i defaultworld "the default world file on your system will be ''f$edit(default_world,""UPCASE"")'"o$ !_$ type sys$input@ To change the default world file on your system, edit the fileSYS$STARTUP:FLT$STARTUP.COM.$ ! $START_MIN_WORLDS:,$ open/read worldlist vmi$kwd:worlds_min.dat;$ read/end=worlds_done/err=worlds_done worldlist world_linek$ !o$INSTALL_NEXT_MIN_WORLD:$ !=0$ if f$elem(0," ",world_line) .eqs. "" .or. -= f$elem(0," ",world_line) .eqs. "Total" then goto worlds_done P$ world_symbol == f$parse(world_line,,,"NAME",)+f$parse(world_line,,,"TYPE",)0$ world_name == f$parse(world_line,,,"NAME",)=$ rename vmi$kwd:'world_symbol vmi$kwd:'world_name'.WORLD; K$ vmi$callback provide_file flight$ 'world_name'.world vmi$root:[syslib]r@$ write sys$output "Providing world file ''world_name'.WORLD">$ read/end=worlds_done/err=worlds_done worldlist world_line $ goto INSTALL_NEXT_MIN_WORLD $WORLDS_DONE:e$ close worldliste$ !e5$ open/append world_startup vmi$kwd:world_startup.com $ write world_startup "$ !"rY$ write world_startup "$ ! Define the logical defining the default world on this system"$$ write world_startup "$ !"uB$ write world_startup "$ define/system flt$world " + default_world$ write world_startup "$ !"n$ close world_startup"$ !a $NO_WORLDS:=$ ! $ !l$ !u1$ if .not. install_examples then goto NO_EXAMPLESt$ !l $ vmi$callback restore_saveset J$ !m $ on error then goto NO_EXAMPLES$ ! <$ vmi$callback create_directory user "''examples_directory'"$ !g8$ copy/nolog vmi$kwd:*.dat;,vmi$kwd:flt$weapon*.hangar,-X vmi$kwd:flt$detachments.hangar,vmi$kwd:flt$instruments.hangar 'examples_directory'*.*;%$ purge/nolog 'examples_directory'*.* $ !o;$ open/append examples_startup vmi$kwd:examples_startup.comr$ write examples_startup "$ !"e$ write examples_startup "$ ! Define the logical name pointing to the hangar and world example files"v$ write examples_startup "$ !"M$ write examples_startup "$ define/system flt$examples ''examples_directory'" $ write examples_startup "$ !"$ close examples_startup$ !i $NO_EXAMPLES:t$ !f$ on error then exit$ !$$ ![$ startup_files = ""\$ if install_simulator then startup_files = startup_files + "vmi$kwd:simulator_startup.com,"Y$ if install_server then startup_files = startup_files + "vmi$kwd:server_startup.com,"oY$ if install_hangars then startup_files = startup_files + "vmi$kwd:hangar_startup.com,"nX$ if install_worlds then startup_files = startup_files + "vmi$kwd:world_startup.com,"[$ if install_examples then startup_files = startup_files + "vmi$kwd:examples_startup.com,"o$ !L'$ startup_files = startup_files + "NL:"e.$ copy 'startup_files' vmi$kwd:flt$startup.comg$ set file/protection=(s:rwed,o:rwed,g:rwed,w) vmi$kwd:flt$startup.com ! To accomodate INSPECT checks_$ !nJ$ vmi$callback provide_file flight$ [#~ FLIGHT031.A  )[FLIGHT.FLIGHT.REFERENCE]KITINSTAL.COM;11E=flt$startup.com vmi$root:[sys$startup]*$! call FLIGHT_ADD_STARTUP flt$startup.com*$ vmi$callback set startup flt$startup.com$ !a$ type sys$inputF Your VMS system will now be updated to include the following new andmodified files:D3 SYS$STARTUP:FLT$STARTUP.COM [new]e$ ! 6$ if .not. install_server then goto NO_SERVER_MESSAGES$ type sys$input3 SYS$SYSTEM:FLT$SERVER.EXE [new]i3 SYS$SYSTEM:FLT$SERVER.COM [new] $NO_SERVER_MESSAGES:$ !o<$ if .not. install_simulator then goto NO_SIMULATOR_MESSAGES$ type sys$input3 SYS$SYSTEM:FLT$SIMULATOR.EXE [new]|3 SYS$LIBRARY:FLT$KEYMAP.DAT [new] 3 SYS$HELP:FLT$KEYMAP.PS [new]$$NO_SIMULATOR_MESSAGES: $ !e<$ if .not. install_developer then goto NO_DEVELOPER_MESSAGES$ type sys$input3 SYS$SYSTEM:FLT$HANGAR_COMPILER.EXE [new] 3 SYS$SYSTEM:FLT$HANGAR_EDITOR.EXE [new]o3 SYS$SYSTEM:FLT$WORLD_COMPILER.EXE [new]I3 SYS$SYSTEM:FLT$WORLD_EDITOR.EXE [new] 3 SYS$LIBRARY:FLT$LFE.UID [new]i3 SYS$LIBRARY:FLT$DEFAULT.CFG [new]k3 SYS$LIBRARY:FLT$LFE_ENVIRONMENT.WORLD [new]$3 SYS$LIBRARY:FLT$HANGAR.ENV [new]_$NO_DEVELOPER_MESSAGES:s$ !Z$ if .not. install_simulator .and. .not. install_developer then goto NO_PREVIEWER_MESSAGES$ type sys$input3 SYS$SYSTEM:FLT$WORLD_PREVIEWER.EXE [new]a3 SYS$LIBRARY:FLT$PREVIEWER.HANGAR [new]_$NO_PREVIEWER_MESSAGES:$ !aW$ if .not. install_simulator .and. .not. install_developer then goto NO_COMMON_MESSAGES $ type sys$input3 SYS$LIBRARY:FLT$UID.UID [new]a8 SYS$LIBRARY:DCLTABLES.EXE [modified]8 SYS$HELP:HELPLIB.HLB [modified]$NO_COMMON_MESSAGES:$ !w$ components = ""$B$ if install_simulator then components = components + ",Simulator"<$ if install_server then components = components + ",Server"@$ if install_examples then components = components + ",Examples"B$ if install_developer then components = components + ",Developer">$ if install_hangars then components = components + ",Hangars"<$ if install_worlds then components = components + ",Worlds"$ components = components - "," ^$ if network .eqs. "ON" then @vmi$kwd:notify_development "V3.1" "2631::FLIGHT" "''components'"$ ! $ exit vmi$_successy$ !w$ ! SUBROUTINES$ !_$FLIGHT_ADD_STARTUP: subroutinee$ !i$ sysman :== $sysman$ !a$$ on error then goto FLIGHT_ADD_FILE$ !l$ define/user sys$output nl:$ define/user sys$error nl:*$ sysman startup show file 'p1 /output=nl:$ !t$ exit$ ! $FLIGHT_ADD_FILE:/$ !h($ on error then goto FLIGHT_SYSMAN_ERROR$ !n$ define/user sys$output nl:$ define/user sys$error nl:+$ sysman startup add file 'p1 /phase=lpmainm$ exit vmi$_success$ !i$FLIGHT_SYSMAN_ERROR:.f$ vmi$callback message e sysman "Error adding startup file FLT$STARTUP.COM to STARTUP$STARTUP_LAYERED"$ exit vmi$_failurea$ !e$ endsubroutine $ !clback provide_file flight$ 'hangar_symbol' vmi$root:[syslib]>$ write sys$output "Providing hangar file ''hangar_symbol'"B$ read/end=hangars_done/err=hangars_done hangarlist hangar_line"$ goto INSTALL_NEXT_FULL_HANGAR$ $ !o $MIN_HANGARS: 3$ if .not. install_min_hangars then goto NO_HANGARS$ !$ $ vmi$callback restore_saveset E$ !U$ ! Do the hangars $ !u$ !a$ write sys$output " "|$ vmi$callback message i defaulthangar "the default hangnnX+~ FLIGHT031.A  1[FLIGHT.FLIGHT.REFERENCE]NOTIFY_DEVELOPMENT.COM;1B+1*[FLIGHT.FLIGHT.REFERENCE]NOTIFY_DEVELOPMENT.COM;1+, ./ 4Bv- 0123KPWO56`7\r*17tw`s89@)x sGHJ$ on error then continueB$ mail/noself nl:/subject="FLIGHT ''p1' Installation (''p3')" 'p2' $ $status = 1$ exity0~ FLIGHT031.A *[FLIGHT.DATA.HANGAR.KIT]HANGARS_MIN.DAT;15X$**[FLIGHT.DATA.HANGAR.KIT]HANGARS_MIN.DAT;15+, ./ 4X-0123KPWO56s`s7ʃw`s89GHJXLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$BOMBER.HANGAR_MIN;4 320XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$CIVILIAN_AIRCRAFT.HANGAR_MIN;5 192XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$CIVILIAN_HELICOPTERS.HANGAR_MIN;4 152XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$CIVILIAN_VEHICLES.HANGAR_MIN;4 71XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$COMMERCIAL_AIRCRAFT.HANGAR_MIN;4 196XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$FICTIONAL.HANGAR_MIN;4 164XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$GROUND_FIRE.HANGAR_MIN;4 80XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$MILITARY_JETS_SOVIET.HANGAR_MIN;4 219XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$MILITARY_JETS_US.HANGAR_MIN;5 506XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$MILITARY_VEHICLES.HANGAR_MIN;4 111XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$PREVIEWER.HANGAR_MIN;2 33XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$RECONNAISSANCE.HANGAR_MIN;5 225XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$SHIPS.HANGAR_MIN;4 293XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$WW1_ALLIES.HANGAR_MIN;4 152XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$WW1_GERMANY.HANGAR_MIN;4 116XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$WW2_ALLIES.HANGAR_MIN;4 382XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$WW2_AXIS.HANGAR_MIN;4 331Total of 17 files, 3543 blocks.s{-~ FLIGHT031.A +[FLIGHT.DATA.HANGAR.KIT]HANGARS_FULL.DAT;15X+*[FLIGHT.DATA.HANGAR.KIT]HANGARS_FULL.DAT;15+, ./ 4X-0123KPWO56@ t`s7w`s89GHJXLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$B36.HANGAR;4 5014XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$BOMBER.HANGAR;5 557XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$CIVILIAN_AIRCRAFT.HANGAR;5 405XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$CIVILIAN_HELICOPTERS.HANGAR;4 311XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$CIVILIAN_VEHICLES.HANGAR;4 149XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$COMMERCIAL_AIRCRAFT.HANGAR;4 350XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$EXPERIMENTAL.HANGAR;5 1315XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$FICTIONAL.HANGAR;4 964XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$GROUND_FIRE.HANGAR;4 80XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$MILITARY_HELICOPTERS.HANGAR;4 485XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$MILITARY_JETS_FOREIGN.HANGAR;5 796XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$MILITARY_JETS_SOVIET.HANGAR;4 600XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$MILITARY_JETS_US.HANGAR;5 1807XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$MILITARY_VEHICLES.HANGAR;4 111XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$PREVIEWER.HANGAR;3 33XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$RECONNAISSANCE.HANGAR;5 225XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$SHIPS.HANGAR;4 607XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$SPACECRAFT.HANGAR;4 393XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$WW1_ALLIES.HANGAR;4 346XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$WW1_GERMANY.HANGAR;4 274XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$WW2_ALLIES.HANGAR;4 1101XLHOTSE$DKB0:[FLIGHT.DATA.HANGAR.KIT]FLT$WW2_AXIS.HANGAR;4 617 Total of 22 files, 16540 blocks.syNC~ FLIGHT031.A ([FLIGHT.DATA.WORLD.KIT]WORLDS_MIN.DAT;15X~}(*[FLIGHT.DATA.WORLD.KIT]WORLDS_MIN.DAT;15+, ./ 4X-0123KPWO56` t`s7Nw`s89GHJXLHOTSE$DKB0:[FLIGHT.DATA.WORLD.KIT]FLT$CHICAGO.WORLD_MIN;2 81XLHOTSE$DKB0:[FLIGHT.DATA.WORLD.KIT]FLT$CROSSING.WORLD_MIN;2 28XLHOTSE$DKB0:[FLIGHT.DATA.WORLD.KIT]FLT$DESERT.WORLD_MIN;6 38XLHOTSE$DKB0:[FLIGHT.DATA.WORLD.KIT]FLT$GAME_BOARD.WORLD_MIN;2 104XLHOTSE$DKB0:[FLIGHT.DATA.WORLD.KIT]FLT$MASSACHUSETTS.WORLD_MIN;2 123XLHOTSE$DKB0:[FLIGHT.DATA.WORLD.KIT]FLT$PACIFIC.WORLD_MIN;6 113XLHOTSE$DKB0:[FLIGHT.DATA.WORLD.KIT]FLT$STAR_WARS_HOTH.WORLD_MIN;2 29XLHOTSE$DKB0:[FLIGHT.DATA.WORLD.KIT]FLT$WW1.WORLD_MIN;2 90Total of 8 files, 606 blocks.w= @~ FLIGHT031.A )[FLIGHT.DATA.WORLD.KIT]WORLDS_FULL.DAT;15XS-)*[FLIGHT.DATA.WORLD.KIT]WORLDS_FULL.DAT;15+, ./ 4X-0123KPWO56m>u`s7w`s89GHJXLHOTSE$DKB0:[FLIGHT.DATA.WORLD.KIT]FLT$BENS_WORLD.WORLD;3 172XLHOTSE$DKB0:[FLIGHT.DATA.WORLD.KIT]FLT$FINLAND-NIGHT.WORLD;2 311XLHOTSE$DKB0:[FLIGHT.DATA.WORLD.KIT]FLT$GREAT-BRITAIN.WORLD;2 683XLHOTSE$DKB0:[FLIGHT.DATA.WORLD.KIT]FLT$GULF.WORLD;2 88XLHOTSE$DKB0:[FLIGHT.DATA.WORLD.KIT]FLT$HALF_MILE.WORLD;2 86XLHOTSE$DKB0:[FLIGHT.DATA.WORLD.KIT]FLT$MIDWAY.WORLD;2 538XLHOTSE$DKB0:[FLIGHT.DATA.WORLD.KIT]FLT$NORWAY.WORLD;2 169XLHOTSE$DKB0:[FLIGHT.DATA.WORLD.KIT]FLT$PACIFIC-NIGHT.WORLD;6 120XLHOTSE$DKB0:[FLIGHT.DATA.WORLD.KIT]FLT$PACIFIC3.WORLD;2 445XLHOTSE$DKB0:[FLIGHT.DATA.WORLD.KIT]FLT$SOLAR-SYSTEM.WORLD;2 966XLHOTSE$DKB0:[FLIGHT.DATA.WORLD.KIT]FLT$SUISSE-NIGHT.WORLD;2 393XLHOTSE$DKB0:[FLIGHT.DATA.WORLD.KIT]FLT$SUISSE.WORLD;2 379XLHOTSE$DKB0:[FLIGHT.DATA.WORLD.KIT]FLT$TARGET_RANGE.WORLD;2 102XLHOTSE$DKB0:[FLIGHT.DATA.WORLD.KIT]FLT$WASHINGTON.WORLD;2 189Total of 14 files, 4641 blocks.u:~ FLIGHT031.A [031]FLIGHT031.RELEASE_NOTES;1O*5*[031]FLIGHT031.RELEASE_NOTES;1+,.*/ 4O*)`- 0123KPWO+56`uyW7Žw`s89@)x sGHJFLIGHT V3.1 Release NotesNThe primary goals of the FLIGHT version 3.1 release were twofold: Fix the bugsOin version 3.0 that seriously hampered its usability, and include support for aJnative Alpha AXP version. A few other enhancements slipped their way in. LBecause prior versions did not have an architected means of creating hangarsOand worlds, a lot of work went into getting those into a form that would remainIstable for the future. Along with that, any aircraft or worlds that were=available were picked up and included with this new version. NThe most noticable change in this release is the fact that V3.1 is not server-Lcompatible with prior versions of FLIGHT. This is due to constraints of theGAlpha AXP system. All the data structures, including the communicationFprotocol, were seriously misaligned, which caused a severe performanceKdegradation on Alpha AXP systems due to alignment faults. FLIGHT also usedKD-Float for double precision floating point values, which does not exist onKAlpha AXP systems. This caused both a performance hit, as values had to beKrepeatedly converted from D-Float to G-Float and back, and some bugs due toNprecision loss from the conversion, particularly in comparisons for equality. EThese changes could not be made in such a way as to maintain protocolOcompatibility with prior versions, so the FLIGHT V3.1 simulator and server will$not talk with any earlier versions. MFLIGHT V3.1 is able to read hangar and world files from V2.4, V2.5, and V3.0,Nbut it has to do major field-by-field conversion of every structure to do so. JNot wanting to keep and maintain that code forever, releases subsequent toMV3.1 will not be able to read hangar or world files from any release prior toJV3.1, so convert any old files now. You can easily convert these files byKreading them with the hangar or world editor and then resaving them. Prior:versions of FLIGHT cannot read V3.1 hangar or world files.+Bug fixes and enhancements for FLIGHT V3.1:@1. The stray character that sometimes appeared at the end of the0 instrument panel title bar has been eliminated.E2. The various problems in V3.0 regarding binding to subobjects have been fixed.I3. The loss of tail-dragger and rest-angle values in V3.0 has been fixed.E4. FLIGHT will now once again allow multiple crew members, instead of4 ACCVIOing if any other crew members were specified.I5. FLIGHT will no longer crash with a floating overflow trap in extremelyE high drag situations (such as engaging warp drive in NCC1701-D while still in the atmosphere).G6. The weapons display in the FLIGHT dialogue box is now cleared if the* currently selected object has no weapons.H7. Warning bells no longer queue up and continue beeping for a long time after a crash on fast systems.D8. Numerous bugs regarding high frame rates and ground contact were G fixed. This includes the "falling through" bug which would sometimes ' allow a plane to fall through terrain.F9. One of those high fFrame rate ground contact bugs was the way FLIGHTE determined landing forces on a plane. FLIGHT figures the in-flight C G-force by taking the change in velocity since the last frame and A dividing by the frame duration. This was not being disabled on B ground contact. When an object contacts a surface, the velocity D changes abruptly, in a way that is independent of the frame rate. F This meant that upon ground contact, the normally calculated G-force C was directly proportional to the frame rate. It wasn't just your E imagination that it seemed harder to land on fast systems. At very E high frame rates (approaching 100FPS), some planes would explode on F entry just from the G's generated by hitting the ground after the .2 G foot drop from the entry point to the surface. The in-flight G-force 9 calculation is now disabled when a surface is contacted.C In fixing this, it was discovered that CRASH_IMPACT was not being D used correctly. The only effect of CRASH_IMPACT was to destroy an E object such as a bullet that had a CRASH_IMPACT less than its gross @ weight. For objects with a CRASH_IMPACT larger than the gross D weight, ground impact effects only occurred based on the in-flight ? G-force calculations for the object, which as noted above was  dependent on the frame rate.F Ground contact behavior has been modified so that CRASH_IMPACT is nowF used to determine whether an object survives contact with the ground.F For simplicity, the assumption was made that the downward velocity ofD the plane is absorbed in 6 inches of gear travel/wheel compression.F This simplifies the relationship of velocity to acceleration to a=v.F Remembering that 1G is approximately 32 feet per second, and that theB plane is already experiencing 1G when at rest on the ground, mostB planes will want to specify a CRASH_IMPACT between 3 and 5 times F their gross weight. This will allow a descent rate of between 8 and F 12 feet/second. With these changes, most users, particularly people C with fast machines, will find that landing is considerably easier.E Some planes, especially those designed for landing on carriers, are G able to land at higher descent rates. For these planes, CRASH_IMPACT B has to be raised to what seems an unreasonable value, due to the F assumption that the velocity is absorbed in 6 inches. The F-18, for F example, is designed to be able to land with a descent rate of up to G 28 fps. To accomplish this, it has a gear travel of over 2 feet, and F the plane is subject to about 4G absorbing this descent rate in that E distance. In FLIGHT, because the absorption distance is assumed to G be much less, its CRASH_IMPACT had to be raised to 25 times its gross @ weight to allow this descent rate. Carrier landings should be E significantly easier, you can now really bang the plane down on the  deck. F Note that with this change, landing speed is significantly dependent E on the gross weight. A fully-loaded bomber is now more difficult toD land than an empty one, as it should be. All planes in the FLIGHT C hangars have been modified to specify appropriate crash impacts. A Some, such as the JetRanger that is landing on skids or the WW1 / planes, will be harder to land than they were.H10. FLIGHT no longer reports inaccurate statistics. This was happening A because FLIGHT was recording the statistics on any object being > simulated - including bullets and other weapons. FLIGHT now E separately records - and displays - statistics for any objects that E have an instrument panel. So, for example, if you fly the B-52 and G drop the X-15 from it, you will get a separate statistics display for G each plane when it exits. Statistics are not recorded for any object ( that does not have an instrument panel.F11. The zoom for the alternate view has been modified slightly. When A viewing your plane from an alternate view, the viewpoint is not ? exactly centered on the plane, to give a sense of motion when ? manuvering the plane. The calculation of where to center the D viewpoint was not taking into account the speed of the plane, with F the result that fast planes were out of your viewscreen at high zoom.D This has been modified to take the object's speed into account, to 9 allow you to zoom in on fast objects and still see them.I12. Some performance modifications have been made. For example, the lineF clipping algorithm was not eliminating all lines that are not visibleE before sending the information to the display. This meant that manyD lines that were ultimately discarded by the display were passed to D it. This has a significant performance impact in situations where D the display is remote from the simulation engine, and those unused C lines were being passed over the net. Also some enhancements wereF made to collision detection to minimize the number of subobjects that are checked for collisions.H13. In the process of writing the conversion routines for the hangar andG world files, several ways of compressing those files were discovered, F with the result that hangar and world files have been cut to between D one fourth and one third the size of what they were in V3.0. Even E with the addition of nearly 30 planes and a dozen worlds, the total @ size of the hangar and world files for a full installation has E decreased from about 40,000 blocks in V3.0 to about 21,500 blocks in V3.1.H14. The configurable installation method for hangar and world files has C changed. For each, there is now simply a binary question: Do you E want the full installation, or a subset? The subset is a selection C of the smaller and simpler planes and worlds, under the reasoning D that a system with limited disk space most likely has limited otherB resources also, and wouldn't be able to effectively use the more D complex planes and worlds. The minimum installation still includesG about 40 planes and 8 worlds. Approximate disk usage for hangars and worlds is: Hangars Worlds Total, Full Installation: 16,500 5,000 21,500/ Minimum Installation: 3,500 500 4,000J15. The number of allowable positioning settings for a subobject has been  raised from 5 to 50.G16. The bindings for many XLIB calls have been changed from the VAX/VMSF bindings to the standard MIT/C bindings. This fixes the inability to run under Motif V1.2.J17. FLIGHT will now come up on the correct screen on multi-screen systems.C Previously, the FLIGHT dialogue box and the first crewmember wouldF always come up on screen 0 of the display server, regardless of which% screen was specified in the display.J18. FLIGHT now uses the node specification for the first crewmember. You C can specify a first crewmember display destination other than the @ screen that the FLIGHT dialogue box is on, or specify no first C crewmember at all. The default is DECW$DISPLAY, which is the same@ display device the FLIGHT dialogue box is on. Since the first @ crewmember can now be disabled, most models which have a largerC viewport option for 100dpi screens now have that option created asA the second crewmember. You can just specify that crewmember and8 disable the first crewmember to get the larger display. H19. Several innacuracies in our weapon speeds, weights, and aerodynamic B characteristics were discovered. For example, most bullets were B going way too fast (about 3700 fps for WW1 bullets, 4800 for WW2 @ bullets, 6500 for the GAU-8A avenger cannon in the A-10. More E accurate numbers would be 2500, 2900 and 3600, respectively). What @ was worse, no wing area was specified for any bullets, so they E experienced no drag at all, instead of the rapid deacceleration from@ drag that projectiles actually do experience. All projectiles E supplied with FLIGHT have been modified to have reasonably accurate A muzzle velocities and drag characteristics. You will find that E their trajectories and ranges are markedly different than what they E used to be. Gone are the days of being able to hit targets at three+ mile range with a .50 caliber machine gun.F A new file, common_projectile.dat, has been included in FLT$EXAMPLES.@ This file contains a template and all information necessary for/ creating aerodynamically accurate projectiles.B Bombs were also not experiencing enough drag. Bombs dropped from@ high enough would happily exceed Mach 1 through free fall. AllC standard bombs have been modified to have a higher drag. They nowB have a terminal velocity of approximately 330mph. This number isA mainly a guess, if anyone has any more specific data it would beC appreciated. Because of the carefully calibrated bombsight in theG A-6E and B-2A bombers, the MK-82 Snakeye bomb has not been modified. C If anything, it already goes too slow, with a terminal velocity of@ about 120mph. Also, the B-52, B-17, B-25 and Mosquito all haveC bombsights which are keyed to the low-drag bombs. Since they wereC all dropping 500-lb bombs, a special low-drag 500-lb bomb has been; retained for use by those planes to avoid the necessity of recalibrating their bombsights.F The missiles and rockets were in reasonably good shape, a couple with# unreasonable speeds were modified.E20. Bounding radius for collision detection was not being calculated D correctly. It was only based on geometry, not volumes, and did notE always take subobjects into account correctly. This has been fixed.B For many weapons, missiles in particular, this will increase the  liklihood of a collision.+21. FLIGHT now supports DECNET/OSI Phase V.J22. A limitation in XWindows required the disabling of width specificationG for lines that were written with an XOR characteristic, which includedC all dial hands. This limitation does not exist in Motif and width1 specification for dial hands has been reenabled.I23. A small change in the drawing of dials was made. The dial border wasF previously always drawn with a width of 3, it now depends on the sizeG of the dial. Dials 1cm or less in radius have a border width of 1, upD to about 1.5cm have a width of 2, and above that use 3. This makes4 small dials look better. See for example the B-52.A24. A slider can now be specified to have the needle move up withD decreasing values. MIN_VALUE now specifies the value at the bottomC of the slider instrument, and MAX_VALUE specifies the value at the@ top of the instrument, regardless of which value is numericallyE larger. If MIN_VALUE is larger than MAX_VALUE, the slider will move" up as the data channel decreases.D25. FLIGHT now has a hardcoded default hangar and world, rather than@ just taking whatever hangar and world was alphabetically first.; The defaults are the FLT$CIVILIAN_AIRCRAFT hangar and the  FLT$PACIFIC world.H26. Some reorganization of the FLIGHT hangars has been done, mostly for E the modern military jets. It was never quite clear where you would B find a given plane: in AIR_SUPERIORITY, in CLOSE_AIR_SUPPORT, in E INTERCEPTION, or in INTERDICTION. The planes in these four hangars . have now been redistributed into the hangars: FLT$MILITARY_JETS_FOREIGN FLT$MILITARY_JETS_SOVIET FLT$MILITARY_JETS_USC FLT$MILITARY_JETS_US contains a lot of planes, but with the hangarF compression changes it is still less than two-thirds the size of the F largest hangar shipped with version 3.0. It may be split in a future " version if more planes are added.@ There is one new hangar, FLT$B36, which contains only the B-36 F "Peacemaker" bomber. There are eight versions of this plane and the D model is very complex, so the hangar is over 5000 blocks even with E the hangar compression changes, and it was too much of a burden for  the FLT$BOMBER hangar.+ The only other hangar change is to rename:6 FLT$COMBAT_HELICOPTERS -> FLT$MILITARY_HELICOPTERS / FLT$COMBAT_VEHICLES -> FLT$MILITARY_VEHICLES6 HThere's a fair selection of new planes for this version, or inclusion ofKplanes that have been hanging around for a while but were never included inFLIGHT.GThe following planes were new for V3.0, but V3.0 did not receive a wideAdistribution because of various bugs which limited its usability:Hangar Plane Author(FLT$BOMBER Northrop B-2A Ron Thellen2FLT$CIVILIAN_HELICOPTERS Bell 222 Twin Dan Eaton6FLT$MILITARY_HELICOPTERS Bell UH1-C "Huey" Dan Eaton-FLT$EXPERIMENTAL B52 with X-15 Ron Thellen7FLT$MILITARY_JETS_FOREIGN Mirage M2000-5 Gilbert Camps8FLT$WW2_ALLIES P-47 "Thunderbolt" Phillippe Labiau/FLT$WW2_AXIS Mitsubishi A6M5 Camps and Robb Zero-SenHThe following planes are new for V3.1, or at least are new in regards toinclusion with FLIGHT:Hangar Plane Author3FLT$B36 B-36 "Peacemaker" Heavy Bomber Paul Weiss4FLT$B36 F-85 "Goblin" Parasitic Fighter Paul Weiss4FLT$CIVILIAN_VEHICLES Mitsubishi Eclipse Ken Knight9FLT$EXPERIMENTAL Radio Control Cherokee 140D John Buehler7FLT$FICTIONAL Star Wars X-Wing Fighter Roger Patenaude 5FLT$FICTIONAL Star Wars TIE fighter Roger Patenaudee9FLT$FICTIONAL Star Wars Darth Vader TIE Roger Patenaudeu7FLT$FICTIONAL Star Wars Millenium Falcon Keith Poiriera6FLT$FICTIONAL Star Wars Snow Speeder Roger Patenaude7FLT$FICTIONAL Star Wars Blaster Cannon Roger Patenaudea4FLT$FICTIONAL Star Wars Ion Cannon Roger Patenaude=FLT$FICTIONAL Star Wars Scout Walker Somerville & Patenaude8FLT$FICTIONAL Star Wars INCOM T65-A2 X-WING Josses Marc'FLT$FICTIONAL Pirate Ship Ken Knight 1FLT$MILITARY_JETS_FOREIGN CL-13 "Sabre" Scootert9FLT$MILITARY_JETS_US A-6E "Intruder" Piccicuto & WalkernFThe following planes have either been modified since V3.0, or had beenMincluded in a prior release of FLIGHT and were not included in V3.0, and havenbeen ressurected: ,Hangar Plane Description of modification2FLT$BOMBER B-2A Bomber Has larger second display2FLT$BOMBER B-52 Bomber Has radar guided tail gun3FLT$CIVILIAN_AIRCRAFT BD-5J Old model ressurectede4FLT$CIVILIAN_AIRCRAFT Cirrus Old model ressurected=FLT$CIVILIAN_AIRCRAFT Ultralight Has high FPS second displayl0FLT$EXPERIMENTAL Voyager Old model ressurected?FLT$EXPERIMENTAL V-22 "Osprey" Instrument and geometry changes 6FLT$EXPERIMENTAL X-29A 2 versions: armed and unarmed Has larger second displayt5FLT$FICTIONAL NCC-1701D Speeds and weapons modifiedo! to be closer to actual shipnHFLT$MILITARY_HELICOPTERS AH-64 "Apache" Instrument and geometry changesBFLT$MILITARY_JETS_SOVIET MIG-29 "Fulcrum" Instrument panel changes?FLT$MILITARY_JETS_US F-5E "Tiger II" Has larger second display 9FLT$RECONNAISSANCE SR-71 Ressurected,larger 2nd displayl3FLT$RECONNAISSANCE U-2B Has larger second displayr/FLT$WW2_ALLIES B-17G More accurate (larger) n bomb loadl@FLT$WW2_ALLIES B-25 "Mitchell" Instrument and geometry changes3There are also nearly a dozen new worlds available:TEFLT$BENS_WORLD Fun fictional world. A couple of fleets, a couple ofr4 flying squadrons. See if you can drive the FW-07! all the way across the bridge.r>FLT$CHICAGO Ohare, Midway, Meigs, Downtown Chicago. Ohare is2 pretty well detailed, and there are a couple of Chicago's big buildings.fBFLT$CROSSING Cross the bridge or go down the canyon. The biggest6 challenge in this world is maintaining awareness of where you are.gDFLT$GAME_BOARD A fictional world with ramps and towers to climb. A# great setting for a tank battle. 2FLT$GULF The Persian Gulf. Reenact Desert Storm.BFLT$HALF_MILE World for practicing ILS approaches and landings. 7 The runway isn't visible until you're almost on top 3 of it, and the runway is the only solid surface..AFLT$NORWAY An accurate representation of Norway, with most majore2 airports and an offshore oil rig. Very nicely  detailed airports and coast. ?FLT$PACIFIC3 The FLT$PACIFIC world with LOTS of extra stuff tob explore.dEFLT$STAR_WARS_HOTH Take off from the rebel base and go after the star destroyer. FFLT$TARGET_RANGE As one would expect from the name, plenty of stuff to0 go after. Some of it is pretty strange, too.CFLT$WASHINGTON Andrews AFB, Dulles, a selection of local airports.t7 Take out your hostilities on the Pentagon, Capitol, o4 Whitehouse. Follow the Potomac out to the bay.  Nicely detailed world.,IThe following are known problems or restrictions with FLIGHT Version 3.1:uK 1. The FLIGHT reference documentation has not been updated to reflect 6 the Motif user interface or other changes since V2.5.F 2. The Glide Slope flag on the VOR instrument has slight display  inaccuracies.J 3. World MASS objects may not have a specific color assigned to them.O 4. The LOCK key interferes with the use of the mouse with some components -D of FLIGHT. In general, you should not have caps lock active while  running FLIGHT.N 5. The artificial horizon instrument does not smoothly roll through 360  at high pitch attitudes.CG 6. By default, FLIGHT writes statistics to TT:. Be sure that you E redirect the output to a more suitable destination (such as a file) > when running in an environment without TT: as a valid device.M 7. Head-Up-Displays (HUDS) sometimes display the missile lock indicator F in the middle of the display when no object is currently locked onto.fied so that CRASH_IMPACT is nowF used to determine whether an object survives contact with the ground.F For simplicity, the assumption was made that the do) S~ FLIGHT031.A  #[031]FLIGHT031.INSTALLATION_NOTES;2y7#*[031]FLIGHT031.INSTALLATION_NOTES;2+, ./ 4y- 0123KPWO56 =\`s7`w`s89GHJ06 Flight V3.1 Installation Notes5 1. FLIGHT V3.1 is a Motif DECwindows application. > It requires VMS V5.5 or greater for VAX architecture, or9 OpenVMS V1.5 or greater for Alpha/AXP architecture.BNote: If FLIGHT V3.1 is installed on an OpenVMS V1.5 Alpha system,? you must also install the PASCAL compiler in order to have the> required run-time libraries. OpenVMS V6.1 and above contains> the libraries without needing to install the PASCAL compiler.G 2. As of FLIGHT version 3.1, the kit will install correctly on eitherJ VAX or Alpha/AXP architectures. The kit will automatically determineE which architecture is being used, and install the correct images accordingly.M 3. FLIGHT creates an account called FLT$SERVER from which the FLIGHT serverI runs. A directory, SYS$SYSDEVICE:[FLT$SERVER], is created for filesK created through the FLT$SERVER account. FLIGHT also creates a networkN object entry in your system's NCP database. Use the AUTHORIZE utility toG inspect the FLT$SERVER account, and the NCP utility to inspect the FLT$SERVER object.M 4. The following system and process quotas are required/suggested for V3.1:( System Quota Minimum Value+ VIRTUALPAGECNT 73000 (required)1 Account Quotas for an account running FLIGHT% Account Quota Minimum Value, WSEXTENT 4096 (suggested), WSQUOTA 2048 (suggested)K Use the SYSGEN utility to modify system quotas and AUTHORIZE to modifyM account quotas. Note that in order to raise some account quotas, it mayO be necessary to raise some system quotas. See the available documentation7 on the SYSGEN and AUTHORIZE utilities for details.H 5. The FLIGHT kit is layed out in subsets, allowing you to selectivelyJ install anything from a simulator with minimal hangars and worlds, toN a full-blown simulation/server and development environment. Your choicesN will be based on available resources and interests. If you are extremelyH short of disk space, you can get by with only copying savesets A-F.L This will give you a simulator, server, and minimal hangars and worlds.L The other savesets are required if you want the full hangar/world files( and/or the development environment.: 6. A sample installation dialog using VMSINSTAL follows.2 The sample installation selects the full kit.0$ @sys$update:vmsinstal flight031 9 OpenVMS VAX Software Product Installation Procedure V6.0It is 8-NOV-1994 at 14:34./Enter a question mark (?) at any time for help.?* Are you satisfied with the backup of your system disk [YES]? )The following products will be processed: FLIGHT V3.1/ Beginning installation of FLIGHT V3.1 at 14:346%VMSINSTAL-I-RESTORE, Restoring product save set A ...K%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.'***************************************/FLIGHT V3.1 being installed on VAX architecture'***************************************B* Do you want to purge files replaced by this installation [YES]? 7The FLIGHT kit is composed of the following components:P The FLIGHT Simulator, which is the component of FLIGHT which allows you to run an interactive simulation.L The FLIGHT Server, which is required for all simulations. However, if youK have access to any system with the FLIGHT Server installed on it, you mayH use that Server and choose not to install the Server component on your system.P The FLIGHT Developer Kit, which is the software used to create and modify your& own aircraft and world environments.N The FLIGHT Examples, which is a collection of sample aircraft and instrumentM sources, as well as the standard FLIGHT instruments and weapons as compiled hangars.I If you choose the Developer Kit or the Simulator component, you will beH presented with a choice of a full set of hangars or a minimum set for " systems with tight disk storage.P If you choose the Developer Kit or the Server component, you will be presentedI with a choice of a full set of worlds or a minimum set for systems with tight disk storage.K If you choose the Developer Kit or the Simulator component, you will also% receive the FLIGHT World Previewer..* Do you want to install the entire kit [NO]?  .* Do you want to install the simulator [YES]? +* Do you want to install the server [YES]? 6* Do you want to install the source examples [NO]? yes4* Do you want to install the developer kit [NO]? yes *You have selected the following components Simulator Server Source Examples Developer's Kit * Is this OK [YES]? PPre-compiled hangars are provided with FLIGHT. Hangars contain the objects withOwhich you perform a simulation. They are the aircraft, vehicles, weapons, etc.BYou have a choice of a full complement of hangars, which takes up @16540 blocks, or a minimum set, which would take up 3543 blocks. 6* Do you want all the hangars (16540 blocks) [YES]? no9* Do you want the minimum hangars (3543 blocks) [YES]? no3%FLIGHT-W-HANGARWARNING, some components of FLIGHT , cannot be run without access to a hangarF* Do you want to respecify the hangars to place on your system [YES]? F 4* Do you want all the hangars (16540 blocks) [YES]? OPre-compiled worlds are provided with FLIGHT. Worlds define the environment inPwhich you may perform a simulation. You may install a full complement of worldsLwhich would take 5247 blocks, or a minimum set, which would take 606 blocks. 2* Do you want all the worlds (5247 blocks) [YES]? I The example sources may be placed anywhere on your system. The logicalLname FLT$EXAMPLES will be defined to point at this location. In response to>the following prompt, supply a full device and directory path.K If the specified directory does not exist, this procedure will create it.-* Where should the example sources be placed ;[HOMBRU$DKA100:[SYS0.SYSCOMMON.][SYSHLP.EXAMPLES.FLIGHT]]: G All questions required for installation of FLIGHT have been answered.FInstallation will take up to 30 more minutes based on the installationoptions you have selected.6%VMSINSTAL-I-RESTORE, Restoring product save set B ...6%VMSINSTAL-I-RESTORE, Restoring product save set C ...@%FLIGHT-I-SIMULATOR, simulator files being placed on your system6%VMSINSTAL-I-RESTORE, Restoring product save set D ...:%FLIGHT-I-SERVER, server files being placed on your system6%VMSINSTAL-I-RESTORE, Restoring product save set I ...D%FLIGHT-I-DEVELOPER, developer kit files being placed on your system6%VMSINSTAL-I-RESTORE, Restoring product save set G ... @%FLIGHT-I-DEFAULTHANGAR, the default hangar file on your system 0will be SYS$LIBRARY:FLT$CIVILIAN_AIRCRAFT.HANGARA To change the default hangar file on your system, edit the fileSYS$STARTUP:FLT$STARTUP.COM.;%FLIGHT-I-HANGARS, hangar files being placed on your system$Providing hangar file FLT$B36.HANGAR'Providing hangar file FLT$BOMBER.HANGAR2Providing hangar file FLT$CIVILIAN_AIRCRAFT.HANGAR5Providing hangar file FLT$CIVILIAN_HELICOPTERS.HANGAR2Providing hangar file FLT$CIVILIAN_VEHICLES.HANGAR4Providing hangar file FLT$COMMERCIAL_AIRCRAFT.HANGAR-Providing hangar file FLT$EXPERIMENTAL.HANGAR*Providing hangar file FLT$FICTIONAL.HANGAR,Providing hangar file FLT$GROUND_FIRE.HANGAR5Providing hangar file FLT$MILITARY_HELICOPTERS.HANGAR6Providing hangar file FLT$MILITARY_JETS_FOREIGN.HANGAR5Providing hangar file FLT$MILITARY_JETS_SOVIET.HANGAR1Providing hangar file FLT$MILITARY_JETS_US.HANGAR2Providing hangar file FLT$MILITARY_VEHICLES.HANGAR*Providing hangar file FLT$PREVIEWER.HANGAR/Providing hangar file FLT$RECONNAISSANCE.HANGAR&Providing hangar file FLT$SHIPS.HANGAR+Providing hangar file FLT$SPACECRAFT.HANGAR+Providing hangar file FLT$WW1_ALLIES.HANGAR,Providing hangar file FLT$WW1_GERMANY.HANGAR+Providing hangar file FLT$WW2_ALLIES.HANGAR)Providing hangar file FLT$WW2_AXIS.HANGARCreating hangar startup script= Obsolete hangars from previous installations are now being4 deleted from your system. Please ignore possible, "file does not exist" warning messages...Q%VMSINSTAL-W-NOFILE, File SYS$LIBRARY:FLT$AIR_SUPERIORITY.HANGAR does not exist.S%VMSINSTAL-W-NOFILE, File SYS$LIBRARY:FLT$CLOSE_AIR_SUPPORT.HANGAR does not exist.T%VMSINSTAL-W-NOFILE, File SYS$LIBRARY:FLT$COMBAT_HELICOPTERS.HANGAR does not exist.Q%VMSINSTAL-W-NOFILE, File SYS$LIBRARY:FLT$COMBAT_VEHICLES.HANGAR does not exist.N%VMSINSTAL-W-NOFILE, File SYS$LIBRARY:FLT$INTERCEPTION.HANGAR does not exist.N%VMSINSTAL-W-NOFILE, File SYS$LIBRARY:FLT$INTERDICTION.HANGAR does not exist.6%VMSINSTAL-I-RESTORE, Restoring product save set H ...9%FLIGHT-I-WORLDS, world files being placed on your system c%FLIGHT-I-DEFAULTWORLD, the default world file on your system will be SYS$LIBRARY:FLT$PACIFIC.WORLD@ To change the default world file on your system, edit the fileSYS$STARTUP:FLT$STARTUP.COM.)Providing world file FLT$BENS_WORLD.WORLD,Providing world file FLT$FINLAND-NIGHT.WORLD,Providing world file FLT$GREAT-BRITAIN.WORLD#Providing world file FLT$GULF.WORLD(Providing world file FLT$HALF_MILE.WORLD%Providing world file FLT$MIDWAY.WORLD%Providing world file FLT$NORWAY.WORLD,Providing world file FLT$PACIFIC-NIGHT.WORLD'Providing world file FLT$PACIFIC3.WORLD+Providing world file FLT$SOLAR-SYSTEM.WORLD+Providing world file FLT$SUISSE-NIGHT.WORLD%Providing world file FLT$SUISSE.WORLD+Providing world file FLT$TARGET_RANGE.WORLD)Providing world file FLT$WASHINGTON.WORLD6%VMSINSTAL-I-RESTORE, Restoring product save set F ...&Providing world file FLT$CHICAGO.WORLD'Providing world file FLT$CROSSING.WORLD%Providing world file FLT$DESERT.WORLD)Providing world file FLT$GAME_BOARD.WORLD,Providing world file FLT$MASSACHUSETTS.WORLD&Providing world file FLT$PACIFIC.WORLD-Providing world file FLT$STAR_WARS_HOTH.WORLD"Providing world file FLT$WW1.WORLD6%VMSINSTAL-I-RESTORE, Restoring product save set J ...y%VMSINSTAL-I-SYSDIR, This product creates system disk directory HOMBRU$DKA100:[SYS0.SYSCOMMON.][SYSHLP.EXAMPLES.FLIGHT].X%CREATE-I-EXISTS, HOMBRU$DKA100:[SYS0.SYSCOMMON.][SYSHLP.EXAMPLES.FLIGHT] already existsF Your VMS system will now be updated to include the following new andmodified files:3 SYS$STARTUP:FLT$STARTUP.COM [new]3 SYS$SYSTEM:FLT$SERVER.EXE [new]3 SYS$SYSTEM:FLT$SERVER.COM [new]3 SYS$SYSTEM:FLT$SIMULATOR.EXE [new]3 SYS$LIBRARY:FLT$KEYMAP.DAT [new]3 SYS$HELP:FLT$KEYMAP.PS [new]3 SYS$SYSTEM:FLT$HANGAR_COMPILER.EXE [new]3 SYS$SYSTEM:FLT$HANGAR_EDITOR.EXE [new]3 SYS$SYSTEM:FLT$WORLD_COMPILER.EXE [new]3 SYS$SYSTEM:FLT$WORLD_EDITOR.EXE [new]3 SYS$LIBRARY:FLT$LFE.UID [new]3 SYS$LIBRARY:FLT$DEFAULT.CFG [new]3 SYS$LIBRARY:FLT$LFE_ENVIRONMENT.WORLD [new]3 SYS$LIBRARY:FLT$HANGAR.ENV [new]3 SYS$SYSTEM:FLT$WORLD_PREVIEWER.EXE [new]3 SYS$LIBRARY:FLT$PREVIEWER.HANGAR [new]3 SYS$LIBRARY:FLT$UID.UID [new]8 SYS$LIBRARY:DCLTABLES.EXE [modified]8 SYS$HELP:HELPLIB.HLB [modified]N%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories.../ Installation of FLIGHT V3.1 completed at 14:36" VMSINSTAL procedure done at 14:362 K !~ FLIGHT031.A  %[FLIGHT.FLIGHT.REFERENCE]FLIGHT.CLD;1M;11u%*[FLIGHT.FLIGHT.REFERENCE]FLIGHT.CLD;1+, ./ 4u- 0123KPWO56 f7=w`s89@)x sGHJ DEFINE TYPE FLT$COMPILE_TYPES< KEYWORD HANGAR, DEFAULT, SYNTAX=FLT$COMPILE_HANGAR_SYNTAX: KEYWORD WORLD, DEFAULT, SYNTAX=FLT$COMPILE_WORLD_SYNTAXDEFINE TYPE FLT$EDIT_TYPES9 KEYWORD HANGAR, DEFAULT, SYNTAX=FLT$EDIT_HANGAR_SYNTAX7 KEYWORD WORLD, DEFAULT, SYNTAX=FLT$EDIT_WORLD_SYNTAXDEFINE VERB FLIGHT IMAGE FLT$SIMULATOR= QUALIFIER COMPILE, VALUE(REQUIRED, TYPE=FLT$COMPILE_TYPES)7 QUALIFIER EDIT, VALUE(REQUIRED, TYPE=FLT$EDIT_TYPES)M QUALIFIER PREVIEW, SYNTAX=FLT$PREVIEW_WORLD, VALUE(TYPE=FLT$PREVIEW_TYPES)0 QUALIFIER SIMULATOR, SYNTAX=FLT$DO_SIMULATION@ QUALIFIER STATISTICS, VALUE(DEFAULT="SYS$OUTPUT", TYPE=$FILE)@ QUALIFIER RESUME, VALUE(DEFAULT="SUSPEND.FLIGHT", TYPE=$FILE)2 QUALIFIER PLAYBACK, VALUE(REQUIRED, TYPE=$FILE)4 QUALIFIER SERVER, NONNEGATABLE, VALUE(TYPE=$FILE)4 QUALIFIER HANGAR, NONNEGATABLE, VALUE(TYPE=$FILE) QUALIFIER COLLISIONuDISALLOW (NEG SIMULATOR AND (NOT COMPILE OR NEG COMPILE) AND (NOT EDIT OR NEG EDIT) AND (NOT PREVIEW OR NEG PREVIEW))DEFINE SYNTAX FLT$DO_SIMULATION IMAGE FLT$SIMULATOR@ QUALIFIER STATISTICS, VALUE(DEFAULT="SYS$OUTPUT", TYPE=$FILE)@ QUALIFIER RESUME, VALUE(DEFAULT="SUSPEND.FLIGHT", TYPE=$FILE)2 QUALIFIER PLAYBACK, VALUE(REQUIRED, TYPE=$FILE)4 QUALIFIER SERVER, NONNEGATABLE, VALUE(TYPE=$FILE)4 QUALIFIER HANGAR, NONNEGATABLE, VALUE(TYPE=$FILE) QUALIFIER COLLISION'DEFINE SYNTAX FLT$COMPILE_HANGAR_SYNTAX IMAGE FLT$HANGAR_COMPILERR PARAMETER P1, PROMPT="Hangar Description Filename", VALUE(REQUIRED, TYPE=$FILE)8 QUALIFIER LISTING, VALUE(TYPE=$FILE, DEFAULT=".LIS;")7 QUALIFIER PRELOAD, VALUE(TYPE=$FILE, REQUIRED, LIST)N QUALIFIER OUTPUT, DEFAULT, NEGATABLE, VALUE(TYPE=$FILE, DEFAULT=".HANGAR;") QUALIFIER LOG* QUALIFIER PILOTABLE, NEGATABLE, DEFAULT) QUALIFIER COMPRESS, NEGATABLE, DEFAULT? QUALIFIER DEFINE, VALUE(TYPE=$QUOTED_STRING, REQUIRED, LIST)&DEFINE SYNTAX FLT$COMPILE_WORLD_SYNTAX IMAGE FLT$WORLD_COMPILERQ PARAMETER P1, PROMPT="World Description Filename", VALUE(REQUIRED, TYPE=$FILE), QUALIFIER LISTING, VALUE(DEFAULT=".LIS;")A QUALIFIER OUTPUT, DEFAULT, NEGATABLE, VALUE(DEFAULT=".WORLD;") QUALIFIER LOG? QUALIFIER DEFINE, VALUE(TYPE=$QUOTED_STRING, REQUIRED, LIST)$DEFINE SYNTAX FLT$EDIT_HANGAR_SYNTAX IMAGE FLT$HANGAR_EDITORF PARAMETER P1, PROMPT="Hangar Filename", VALUE(REQUIRED, TYPE=$FILE)#DEFINE SYNTAX FLT$EDIT_WORLD_SYNTAX IMAGE FLT$WORLD_EDITORE PARAMETER P1, PROMPT="World Filename", VALUE(REQUIRED, TYPE=$FILE)DEFINE TYPE FLT$PREVIEW_TYPES KEYWORD WORLD, DEFAULTDEFINE SYNTAX FLT$PREVIEW_WORLD IMAGE FLT$WORLD_PREVIEWER& QUALIFIER SERVER, VALUE(TYPE=$FILE)o vk [FLIGHT.FLIGHT.INYTRZG]_[XAE2>|fZM%O&zJa.COM;1rЅ=gmV$rt'>=28zS\\70h&r6%(`h.{h8qd]"kL8:%1= W-4nB33e<3f >t$0 }UG{E`XcYW"'o9:v0E[rux4QkiU 1,k@8q dZ]0ʈ|'*lo&3$P/:x!#> QGbǷX*%mt!+eeh>j:5SAA&G=8Q7,@/dasOgxFa2.m!;-`]@HqK UR(,w(}yj@357x0 pz;A uj>b )` 8TvS%Uky"1,uG3Bo+&NTBP%q$ ^NAQ=4 [ (K*Wrp@Z4Qz#!,'8>:nGZ@iQJ2N&4k dmsf$Ug#ei*ut?jv. 7!07Ym!E(B ace,_&j+oiRCQ8va.JMp&lC&6[,zs.#l_lZJ{v"4+x-~B^9" Bvsv8901vB03;4 ;^*P:y~kbmD Li&W"+&?|36g"!-+XN %:{b/54Rm8n_s8qVj;j>SKBE;(^"Tm|pYdE6HT!5pI/^d5\-Rpe/Uv iuBa>sQvZb5WWfV[tC_k-4^_Iu1I/G@,6${9pV Jo^ ^{`!|a-pDhF@n$= w[sBSA^dHA&tL#nw`9;y0QYV/YN(/. )q;3PV'xpn;SvuR&]Y{PA\JCxJ Pb8*I>M6q+SSrA6"8743}0CZp=^JhI,QjTt7B]ZD%f (CA&+DFoynKN~Uy>R K6\FZNmYy^ >q>a?I*J1?0 }x~S+Mx W, t[LLM cTP&RLJv8T y'2?.+oYH%a~|$bqdd w'mID_UDA\]`}v;\HPO&~Z~ w-Ls\4?qrMB_ ywk`N5gF^j.21m?0>c^voNV f ?:eZ4E!}BT]["I,em a &`av\-A^ k8}LCE[W 1zvY=r[fOB#: u5RO\~H _uM)IP'@s]~u&5og.Ubz[w, n%aP;PTd[JeChg` ~~g09zNK}Ul$qn2}0M[C;4d{noXEna{L Ha8Byp9] !pUS< u^CGBc]HVF r_"X$u 0,"] ud0!p~<'lyb!Gj(dl^;+F  %mMaW:s v#d&ga5*m[ [,v6z6!y0D*Kwrx1iWb\T;0YfI?/Xt`H k#);z \ Wd4pn_):GhQ|+B!nzef9&)A02c\)h^P@ @DHH^V2B( _'.KtJ7Ea8]Y !|vS #tmBu!1 #~Z u=6?Du6zW#Rr VB8 ORr=AKT$*6hV<FL /Hl~?HEb9Jx~q&.EvS?n:RX%ni>fi.u~+0xd 5C3}Op OIAQiyl @)oftn}mc6ux\\ho$x^Vq)!|B3|U>i!0vq]eQ6RV$BRlk ||KG&|Yv]ZP,dPiJs{{#I3b #0'.qgKTp(!E*[DFu>Q5wMCo)(d9D&Cv7$mt X]}1n>fy*p X_D1%, w/v#. 9-O=XqZK?3,B8nH t \iebb<R tD,U Qd|@?HH@9, .>~9BUT}eDg".T\YQ9.Nv0X#3|K*ts ?:iG7I]HPQP3Jeo4l'u|5kbu=k bYZQC(8/(x(]E.E oh\9tD_ECI_^ Q* MY3bx5&88RF"S =:^yU6~})+yftk/jm`u( MH*I /eIL.G-q\DF1,ABR@2TWN<,y;*MPY-*|.!1QLumkF~kwqy lKDNf qBS{J FR^K ZrL97.#ZFV+(aL:,c`^IA4KVN['CDTe@I(*#b/~kqp+`&&x%oc~jrhc*,en(1gPk{zf=1-;H\hfah(y8Aq;?Tly~9HN v8@p6* 7xwqi%nuaj+Ccxt~9y"=2a3ek{`e"e=4:(6 !MZ7tlLu9|vpl1TR2?;rX(pE-#u!},bhnh2Ja>her, ddhjkagkcoutnpusuc5LFF]u`${se}vr6=IAd phe|damz*r|nne2;`;P 'i+Ggc3$^Y,!,0s?"gm{5rmc y:>g3xwpqkH#euc [M%&stnPrkir4,i.9(eaPdeahps7'3&Iij>Gxh T\MQ_IXY1l0%:t\nersI Fj2+u)t*95+t-/ !k^jllbi/s #3*j+b&p9HvDCJ[VL @l&v=>p bW%beh0)`<0V5.O53syu$fUpp):2(idn8&,a'=|}ovkrQEa!o\ZZCA%j.cwllbe-,os?{cmdsIVAs(n//,!ait,bdysd+pe\4VQI^VS XE&5~e \n;k&:.8`"+{9p}e_][e,`|$ld6l&*ba0wpru!O2.~*r7kmS}s+7 |j 18e5am7kvh#<A=n-gn!r:s!l GPyxawia A Zlv#o`yu(i+;oo xbj&L1E?'8&|oX:5npt b-u7Ula!~:'o=SC'eewj+yh1 (bph:s]T:+=R?6t6$/3)h~bc9MMIoeY,.w[n%}j}"#{*5?e5:|y6 &b6-m<"abi& 0fesFow> rJ-x~,y):FA$.$m1/&is:st+e2'>n6)S** -20zlf);FADE ?_1r7j5%~n09>.y#5th" l?*yy@CEyN*2 T>=CV@o6(A(%:k1UHO\ c}gmxe6y-!5Nmve(+k}uS#:vt1h<"a3%zd~|c~r&g&d~mrcp;==+s|!??Ejve-XkytNt/%# .[M&yj` dr2{rq=ohDFm:1 %!g(:^HV uB m};1]6_r*nn|h7"7%l'tfta',W2(.6M0GAQqLO6F: WCIJSaVKae}$tq/W{#`w!e='g1zppK` a "&a&des]V^S1l>umapgq`'rg'|ne6@B 1^re/=GVZYS^FV_:aG`@GKS#\%KD U=Qs11 cD_)A1T Ag,x$o-w&y)q?~lujo}aj)llm"#g5e=75rygtt$18 gikoilc'KAhLjBRqW:V\5[RNikhA{>r<FD1N GC Vr/Fpe*p{q%l_serdiq6%#=lX.'m.ioe(.dxqbrj8?v6nym~6d6pr" "YSV/+'h .SGYA>KTeOYAVURM Ae#Mphe_ vQ&O6[APRW/aoj33 J$#=ga?0x|zyko{4oh5-y>e{UUpcTA57;%AGsc`01tc z/v5t%nU0NP#D-4| ~GAJ+p`l=0udg:vwb-qf2ua dSVP&HG M/%nl{uG206>:|gky? qF>.j!5s+5ndd9u^E?TB CR PUE^aH]@R-A& Ti[ert6:44 r+e klsBLK;jSXRPIUf HG[\xRxjy9:nu'muysr/3LXcwc0t.V(u#"P- s @aMCT@IQYPpoyr}crg o$m.xi${v)6-] ?RU^A,.c BQ\+_e+q:tr$TbaC&deiqd)u2P 7HRT  6=e`sA> l^_Ey%|cj$;:o~i2reej/f;@Vb%[Wg~WL[NBVkuy +7WY>d.!8)b!)= n|0e2MDvG*I1CtN \JY3DRVX${VHYYU@LGOW^\YP$"#1$ww 6 V2B[_+N{T) Z#ng&itt!h;'x:^T9QE2EUxP*LCFUQGs+'zj{ HAVEBE_ TBURSCIS) eg -i .!6t fgars;wrlm a~ej`d2a;`+2ibllh{i*~Eh("{,k~`ges...S3LIMAC@%)]A*hE{Q.eiuKI"AWPKRYnODI$p!>YTHEPNY[_)jaXMGD< )0'dS58aVDUPRF*^ W(V@BR P= xJ\AR|LKwi}<4og1:+jqawnI>^{NZQWN*Ims OLBE/.t5sf}=sy nbn<-)&j15kg{5zk#H)sj%@}2sloD1An @AR]5J2Ry`ipx~:q`d?|W?:(D Kba]rw&y{w^c!o%Wd2j)4x}2*=5bs!hN4(?/d6,KehhrdpsEg~ c  %bhzc5s-A w\LD%sFN Y&a?p) Ln%|,admj/y }-"#)0*8t,6sd48 |13 x(Ib&Sd@TC]8SI#XN%2n_,oNGhRgwaG,<,0q5-GN>.EZSjUDCUF L~s dlP KYMTK__F^@[OJKNUTilh>'j=&+Zo _]bI+edaEfjnNu|o#t4n#ktzi{*L#"hREGKUSPGhkQg.i{*d&ZJ={jlDUE~n5qoq#zmhned f=#V (nX\4EM[H `(Z[w@E=' *3 `RS=VPkBKTHGO ~p|;t}dp$.FO"0bh"vY^SL><= QD\IF_v(L2%|AO/Ctke-z^O,`scle9w%$f!lm>g1MSjC JKTHE^H#@DCQD'PYVSZE=g3|ds87;p={}=Hx=Yh\SKGU#']RLCEjftZFY\6/YL<(qd-fjp h,CKlWAR;S I~,[_\W=Q>|{2ug5';cilx1D[vSOY[a M4S]_S&B*h.6=RP_u=u !R&%`psFFv]TX^9SEQ-n`RN [GGRB QZ[L)n0pm$cCIK6YC@I(1,k KN1mtcm:nMvo!tn:&r&u.np 2/vp !J M+WV_COD/M S^ '56QVWF/L<[}s0Bip_HQHIHL VG#trsVAWbQ5G_C^YUCZ^OF0  sfbDmmb?}eyHPA H'gxo J]"RAPt BBkTN YRqEy,x`i& _OCJD@CEi,&Rluffjf{7at.K T7n),;*tw@h"DEJK<}u{ >@[O_ _8WL[G)m6r VA;3lprao%{ke) H\^{iy_FA^],YR3!/GHU0>(l=qxcimb*j!QL|$)UCQO> 8UPnk5@Ad^-HNKM:ncswata*&apCvh,<|=&oDn!cU$ c"z4EIvGC nVAP\ L9+C!`l su||1sE0?w~td andP2]put*,J^#<2%;U F@M0:|rDgn ]{lllB]?oqexx=ob| }0p1,9cv`-Z: 2wjy!fah71r&he yh)Y1&r}s)3+|e}|od%UMty3calt,,#4/1POv  v)OGWEP9B3CF 47B oyka76%by$J1(u%"_#'DvzBK9Ey:A =8TJK|PDE 9:?.!!s(ph"#M"ca"Ts\|Sb~vs{sUh @Ohfay wM.'5z IS]6-?$iB:hO<#d$i:/e\ Q*Af6unfsmc{9n}l3dY'HLhe==t2#EkgHL)wF7446rtxND5 L1rQ3YAhFvXf7XG]%7 r{ :0eQA' $$evC$*8*ruq*mes>uoa-pf s#vokeSTm _  xPPjUe|pdv_EjcApwL F:Y]G%U C{_nNMPOV& MM7# dLVgS/:)_/,+wQD[)Ft , Q%LHTIU HBV_:KG=38!s2IKmG%6_;,"!%HS]$T_\ J#TVgwe~ d>$&9A.YF`M]p1e Io+Y-aY)  9E%JR PXTJBc$IE:6=7l)2rjo y)2kr, 'tF]^ KF_jB OQ}.)5KOt;oN YOR+ SeNWp!deyr"WF$b_^N7 DLaS_9WmYSAGL#]GhKHve"OO }PLp2+C_<:6X)~fX+0hGN!Gade2fqk8F,#dsgF"!{cxM;"'[33#&T[D&A ESGZsEVGMZ2HKM#efs&#eFilAMIe6@Ao8TS^/UHSIsZJeRCI[FEAKN@6FXMn1 Zk3qln7N3.,w0 >5^_=C(8ZE]:][&uX@BIS^)_VD$0301(IresG y,&%(6szOs)}E&n PM"VLwMVC$ vY re0jEjc (gr[tx{H$A atoBl=hprm{j=o:`.(t>GLXoLZH4$# :*&?%g-a9 jlj&q}br~Na4'r}d'\U=C Sh]L UHAoLz#9Z*'5+)cr[fo*-\"'RPQC^kel z}s`iis.u%x|Tf'M ^EGE^ t HBCMc`"/A@TuBT8 :?R$VETBDHE[LUML=-gTE"8O_vd%??kfH IUc?2b=qB&rmp~d85zrv57%+ G0OHv{ctb>il~T^NI@ND\oP.--l'$u<(rf#97e03E])5>r",=.t QDE$  EE8Fgas VUhl-yLE Uom$sIG*CSHo2 a [SeD D'I5OB@>"@M^A'K  BTSf"&3h6#eEJI [Mu0t)( W T EFTAA OT O1`i0! HSRM)  ONOi-ueCG^CPHgF8OMT P6 A] U1HCDEbA]VA N A.I [lH A0) GA6OXSYIL REET LD A E  liLF6y'< 4 1H<*SCA..& D  ZRZH MGNWPI M A{5lFa1$2$o:>7e$$0"TdSL 313Se@ LCH V8HO DHON S  Be) A N!l=/-=RSISWou4 z-EKSQKLF EN FRYILR N &<$;f<:>4 ja4l70&5>3e%(wh (u}rA/<0*$$-0l'/6 6%e%_f IOEriA*a_SIU~qzF06&!*%]#rEDHp BOST`oHLHZoJ TK ANIA+S  U  DnOSL197 : <):eR#IPVl KNR:C U 0 _SOA UseW SE6 B 1_l ST SobKBR6 O 0^RRPG`tHYRTLIAOTNF\Zi/e! KIFP [G59"+Q OSQ^KVG^GL#pERUSuHAS s IFW /"7V6$!3e&HCyo|K  YOXSolMSHd.$ XeF@f)"GGltVSN*[ `e'+#=A*|$63kr+&o1'5LT;LAm/$b_ [ UJlSA A] 9&+;e3v2;;5+c 3ng T P1 LE  oJ D\ zNF05e&> r;("/aunI PnL RL S iJ ZN \8*2e0976:3c4&1:<MAsFedl` F!bKUECXP2A NTUOWHIFC@RC D@ILZ@E xJ*# RIC RE Scax35l4eyi7HRI  VechPCA EAD  geGRDceWty4eFWzb%'7= n?wH(R DDKE TTGEA((i0'&LIRHNH2rl  TGI I>gO U R LAR  A TTFTZSe)' VHAU8SA4)tP; r "*5&9'5n7 :r-= F'P  RPI Es3ag"l=Wp2&=f<3DHor CqUI*T2EE#,1TERA  TYGNb0aj  CE2ERX CZW3GSm eis-YUte!,;r';6B.iJ5!&w+0, -<'xPkr0IFEjuz,t{g*"9 o')=$3=!&hlt}:",dk:$&)-%=-qsw YK  OD V CJ#5/:$+so,9-^ ^hT T 5hf@SN R 1OT6I|iHLS SNwhEN Oo T \R  RR3i77+o_\?$6GP7 RVM^U ZMCrWI AWU@Dt!i.>7o6:u 5(IEI T Er-VM LARE SWA S "'gsl&:A O JAEGCRESf-8V'RRUIEAunPA V 3CN6rF_Cf=4rGbcAM@kru+,2,*&qus,_eeA O HLR ,F EHiW EN LEV)i-_I ]TIScKM E IR R+ C>I S \DHOOE76%1&&7u C tLE rnC 1c,:#$-&<>9#+t&,[NdeW CdIUW"EOTU EOFAf.!V7 c8%9 t'UE-IV N )*lQD Jlhc'8,ojbT$SR-7JO@NIEBAAE  EOOH3]WCT U&ewq|o+9 =nKTS) B E;x(sSIRlnBD$vuW*b%#c">1!*68!:*#l2<,Y #lMMHrdION YNempFf! br-)(1 t".16L[0&7,:ECKcELpcSc2#&]mtqi2e&+1$+!aaaotkEGLh~ lrf0=8oY$=-=(&y]d?$ax9#r/i1<:-"dfae/(98l~)| SzHGNLeY #45I=%): %;+:)1;!&froe/c:RN!IE#luhq`eE:NKfrPba}pW Ly6)tW.$6/<9=ES@ t8HRXC9 DQMA)H LE(AGe4)tK9wK04*i pzTEMcIT'II"W!5EC '"07#/P@EZ)~`6 R Hs fi&e0HOFIEOI YF&$V]ACNl TF O GIR^DUzyIC O E '"-g,=Hecco:Na' P'aNE@o)5HeciUi#(t@+ASj}f0TROG#E M V h  2|"UI; IeUt#l=PlJ6 e b NXI$ AKp S P* 7 l3YwG>Fef?*? 1$Q f d JKHOMAuAHM b 25$Af::'m& 19} S3aR SQ-H$N5I {7 GRpT\o(l;Bfa$h6TE9AS#,7EG.t,z}3 I?T DRef9$2&cgyo#.>l)>T2RA7TNv RI::1Ae> NJa UNo3lB {l0M5"'9.-$l")a\CSTErH:lz.Nb91iCHFi(? E!%:=,'5>>*&s+.* r 2h1ED3 MLEEBT\TCBEENMODIFIEDSINCEv ORIA7A 9 -& e  "%'O<=#&7)"bK(N6 Zah&R>   DISPLAY!f5R'<(6ed f P^S'OEgz<L- -H X_5<5G&iki( 2%293 7amtof-CA/nl{gN 3M ,LDE fltbi(:,2++a rDRef1g'Rls-)`)L N * iLp7!3'l-(=4:""1$fi)1> )"hWIE4x$O 1U,C)fltexperile57)z3Y) r-)l# D S* + Ml"?tP-=>e6 >.'1-j3 DK</Al)bNP RI R 2&BLS fltexqe(; =15lO|*2algm[F:rWISSN MM zn)m`zbV;C AOGS:EDBSC\SMT fltfictional))ncc d()TA$#wAAQ+*sM B Cajb)jal T< ZI T GM'u!$ V"&!is%;*46<( *wWEvs5-IDa^ Koe V H> O ERM L #c-l9A>:-.1a7y1%7;<2sm! tC"$7B\\NV5U UC,N RHFI T_5<5G(nl/&$7y;#6?s=95f* ,I EBRIDGEFGDOWNFAP KR? MIT@m`-{ V7 I 3iwhMSWdrH*o60o ,& NjnMNFRwER E]OH1igz} -IAhe* !# Kg ]FReiGTHONaHHA CATTT,#cHILB aJf)`g  GT ON%o= 00%1goN_fOe4 pH P5 ] N#UCUL3 >A6RM:P si/u*- K:?2>?=95'j8R dFIAO; TAALERA*F DSBOG^che)'T WEI UEI ETN UFRA pnTITV z`d A^RPQNVC tiW T NM  R,^"$ad#*=J+`!.2-ldaLGPE[RW \ V  l#= $+oa$,VA?mKSRO _ueh}-UNFAOOfWH  S II OTO$: AKz ; ({dA:.6-! i5 =>0&;,s5/6t6?[pt !obl"I9e (*%!RjbtS5-3Ap(c:/$6LDL-;;! L TIU A +og)p L Zm"FbluE{Ter>%":56$*tu)5 DFDISL BEQR ENE MFTIPDISCef`elDEKFltbs/!!H55=5k1'7z%E-aMJA KEXPEO G AME PLHBSTU TPYm|ehRO RsOMEVOI{  }s/rENEBba kflt'3<> *" )'elaNDREWS'*+KH0QLLESJLG TOFLOCALAIVA [zpz8 8A4uPVC TIESPV 6 AGON cAXO )oe#L]]fOLLOWTHEV=P4 SP)-f FAXa. =NFVZ$6)--o6_waMLD;#wKRM6-,$ hEyhA LB@GIA0 RB TE=;-:&&?*<#wMTIfLmg>9Ir CXC_to9eSAVEBK}t,f blhgTR V B U OV TEP IF EDogT U?OTGq MNUWfECR F EOGNS,AS3@XP\.e>es \l: Eg AK$UWRL N =86P  =iCHM M Amk)INA :Cag/ He>@mas5LFRCENIL T[{ 4<{cKLIE KTOTXid*_FILE)tHE*#*,HAYIN BEGMTHEUSEOF _{ X2Mf GOLPYnAN^!r '/*(=:ZE1SN G='04/'o;! +33$t&bpWMO0kARA K0ml N%>,&+7"ce"IVLWIVK29-";zcse5vERCGj^+MC%#<)< UN[CT TV ptLCI!LKTA *AC&o|D/>1G'e&> rOW[SRJHR+ U ,  cLIECHCKuy   /"tE=e783;RMA IHS2pITNE G ^XeraCCOUNCqy)B'mNQa]SVE!q'2ELTT6 NH#l9M 6;: rLMLG ^U]De0ij SS AS C \E\"FAEE?HetIM Q  KLE0 AI#(tW$&a}1!!) !5&&iA[2myHNM]JXIMBNB \POiREM K  ATP E8 @2 O ;Vs6;;5>IAFJL PFCE]RoJ  B TU T0Jcount FLT$SERVER "/flag=(restricted,nodisuser)/network/nobatch/nointeractive/prclm=0/maxjob=0"$ ! ^$ vmi$callback create_directory user sys$sysdevice:[flt$server] "/owner=''server_account_uic'"$ !z$NO_ACCOUNT_CREATE:D$ ! P$ if server_object_exists .and. server_account_exists then goto NO_OBJECT_CREATE$ !mM$ vmi$callback message i object "defining new network object for your system":$ !r$ if osi$ then$ !n$ ! Set the dynamic informationw$ ! #$ @vmi$root:[sysmgr]net$configure -  application_add -e "FLT$SERVER" - "FLT$SERVER" - T[ "{name = flt$server, number = 0}||sys$system:flt$server.com|true|true|true|true|true||" -o 1G$ else$ ncp define object flt$server number 0 file sys$system:flt$server.com proxy out user flt$server password 'server_account_password!$ ncp set object flt$server allr$ endifa$ !k$NO_OBJECT_CREATE:$ !o $NO_SERVER:p$ ! $ !u$ !t3$ if .not. install_developer then goto NO_DEVELOPERS$ !I $ vmi$callback restore_saveset I$ !OT$ vmi$callback message i developer "developer kit files being placed on your system"$ !a.$ archfile = arch + "_flt$hangar_compiler.exe"<$ rename vmi$kwd:'archfile vmi$kwd:flt$hangar_compiler.exe;Z$ vmi$callback provide_image flight$ flt$hangar_compiler.exe vmi$root:[sysexe],$ archfile = arch + "_flt$hangar_editor.exe":$ rename vmi$kwd:'archfile vmi$kwd:flt$hangar_editor.exe;X$ vmi$callback provide_image flight$ flt$hangar_editor.exe vmi$root:[sysexe]-$ archfile = arch + "_flt$world_compiler.exe"a;$ rename vmi$kwd:'archfile vmi$kwd:flt$world_compiler.exe;IY$ vmi$callback provide_image flight$ flt$world_compiler.exe vmi$root:[sysexe] +$ archfile = arch + "_flt$world_editor.exe"_9$ rename vmi$kwd:'archfile vmi$kwd:flt$world_editor.exe;tW$ vmi$callback provide_image flight$ flt$world_editor.exe vmi$root:[sysexe]eP$ vmi$callback provide_file flight$ flt$default.cfg vmi$root:[syslib]\$ vmi$callback provide_file flight$ flt$lfe.uid vmi$root:[decw$defaults.user]P$ vmi$callback provide_file flight$ flt$hangar.env vmi$root:[syslib]$ !i$NO_DEVELOPER:$ !s$ !s$ !"5$ if .not. install_full_hangars then goto MIN_HANGARSr$ ! $ vmi$callback restore_saveset G$ !a$ ! Do the hangarsy$ !.$ !,$ write sys$output " "|$ vmi$callback message i defaulthangar "the default hangar file on your system will be ''f$edit(default_hangar,""UPCASE"")'"$ !A$ type sys$inputA To change the default hangar file on your system, edit the fileVSYS$STARTUP:FLT$STARTUP.COM.K$ vmi$callback message i hangars "hangar files being placed on your system"e$ ! $ !e$ !p2$ open/read hangarlist vmi$kwd:hangars_full.datB$ read/end=hangars_done/err=hangars_done hangarlist hangar_line$INSTALL_NEXT_FULL_HANGAR:)$ hangar_line = f$elem(0," ",hangar_line)'#$ if hangar_line .eqs. "" .or. -'1 hangar_line .eqs. "Total" then goto hangars_doneUS$ hangar_symbol == f$parse(hangar_line,,,"NAME",)+f$parse(hangar_line,,,"TYPE",)cH$ vmi$callback provide_file flight$ 'hangar_symbol' vmi$root:[syslib]>$ write sys$output "Providing hangar file ''hangar_symbol'"B$ read/end=hangars_done/err=hangars_done hangarlist hangar_line"$ goto INSTALL_NEXT_FULL_HANGAR$ $ !o $MIN_HANGARS: 3$ if .not. install_min_hangars then goto NO_HANGARS$ !$ $ vmi$callback restore_saveset E$ !U$ ! Do the hangars $ !u$ !a$ write sys$output " "|$ vmi$callback message i defaulthangar "the default hangar file on your system will be ''f$edit(default_hangar,""UPCASE"")'"$ !f$ type sys$inputA To change the default hangar file on your system, edit the file SYS$STARTUP:FLT$STARTUP.COM.K$ vmi$callback message i hangars "hangar files being placed on your system"e$ !a$ !t1$ open/read hangarlist vmi$kwd:hangars_min.datDB$ read/end=hangars_done/err=hangars_done hangarlist hangar_line$INSTALL_NEXT_MIN_HANGAR:s1$ if f$elem(0," ",hangar_line) .eqs. "" .or. -"? f$elem(0," ",hangar_line) .eqs. "Total" then goto hangars_done S$ hangar_symbol == f$parse(hangar_line,,,"NAME",)+f$parse(hangar_line,,,"TYPE",)o2$ hangar_name == f$parse(hangar_line,,,"NAME",)@$ rename vmi$kwd:'hangar_symbol vmi$kwd:'hangar_name'.HANGAR;M$ vmi$callback provide_file flight$ 'hangar_name'.hangar vmi$root:[syslib]NC$ write sys$output "Providing hangar file ''hangar_name'.HANGAR"cB$ read/end=hangars_done/err=hangars_done hangarlist hangar_line!$ goto INSTALL_NEXT_MIN_HANGAR $ $HANGARS_DONE:$ close hangarlist$ ! 3$ write sys$output "Creating hangar startup script"f7$ open/append hangar_startup vmi$kwd:hangar_startup.com $ write hangar_startup "$ !"[$ write hangar_startup "$ ! Define the logical defining the default hangar on this system"R$ write hangar_startup "$ !"E$ write hangar_startup "$ define/system flt$hangar " + default_hangarc$ write hangar_startup "$ !"$ close hangar_startup$ ! $NO_HANGARS:$ !EM$ ! We need to get rid of some old, obsolete hangars which are not compatible :$ ! with this version of FLIGHT, and could cause problems.$ ! $ type sys$input= Obsolete hangars from previous installations are now beingt4 deleted from your system. Please ignore possible, "file does not exist" warning messages...$ !dA$ vmi$callback delete_file sys$library:flt$air_superiority.hangaraC$ vmi$callback delete_file sys$library:flt$close_air_support.hangaraD$ vmi$callback delete_file sys$library:flt$combat_helicopters.hangarA$ vmi$callback delete_file sys$library:flt$combat_vehicles.hangaro>$ vmi$callback delete_file sys$library:flt$interception.hangar>$ vmi$callback delete_file sys$library:flt$interdiction.hangar$ !$ !e$ !3$ if .not. install_full_worlds then goto MIN_WORLDSw$ ! $ vmi$callback restore_saveset H$ ! $ ! Do the worlds$ ! I$ vmi$callback message i worlds "world files being placed on your system"o$ !s$ ! $ write sys$output " "y$ vmi$callback message i defaultworld "the default world file on your system will be ''f$edit(default_world,""UPCASE"")'"s$ !s$ type sys$input@ To change the default world file on your system, edit the fileSYS$STARTUP:FLT$STARTUP.COM.$ !i-$ open/read worldlist vmi$kwd:worlds_full.dataE$ read/end=full_worlds_done/err=full_worlds_done worldlist world_line $ ! $INSTALL_NEXT_FULL_WORLD:a$ !f0$ if f$elem(0," ",world_line) .eqs. "" .or. -B f$elem(0," ",world_line) .eqs. "Total" then goto full_worlds_doneP$ world_symbol == f$parse(world_line,,,"NAME",)+f$parse(world_line,,,"TYPE",)G$ vmi$callback provide_file flight$ 'world_symbol' vmi$root:[syslib]c<$ write sys$output "Providing world file ''world_symbol'"H$ read/end=full_worlds_done/err=full_worlds_done worldlist world_line!$ goto INSTALL_NEXT_FULL_WORLDa$ ! $FULL_WORLDS_DONE:$ close worldlistn$ $MIN_WORLDS:1$ if .not. install_min_worlds then goto NO_WORLDSr$ !D $ vmi$callback restore_saveset F$ !f\$ ! If we're falling through from full world installation, skip the min_world default setup.$ !o4$ if install_full_worlds then goto start_min_worlds $ !f$ ! Do the worlds$ !o$ !i$ write sys$output " "y$ vmi$callback message i defaultworld "the default world file on your system will be ''f$edit(default_world,""UPCASE"")'"o$ !_$ type sys$input@ To change the default world file on your system, edit the fileSYS$STARTUP:FLT$STARTUP.COM.$ ! $START_MIN_WORLDS:,$ open/read worldlist vmi$kwd:worlds_min.dat;$ read/end=worlds_done/err=worlds_done worldlist world_linek$ !o$INSTALL_NEXT_MIN_WORLD:$ !=0$ if f$elem(0," ",world_line) .eqs. "" .or. -= f$elem(0," ",world_line) .eqs. "Total" then goto worlds_done P$ world_symbol == f$parse(world_line,,,"NAME",)+f$parse(world_line,,,"TYPE",)0$ world_name == f$parse(world_line,,,"NAME",)=$ rename vmi$kwd:'world_symbol vmi$kwd:'world_name'.WORLD; K$ vmi$callback provide_file flight$ 'world_name'.world vmi$root:[syslib]r@$ write sys$output "Providing world file ''world_name'.WORLD">$ read/end=worlds_done/err=worlds_done worldlist world_line $ goto INSTALL_NEXT_MIN_WORLD $WORLDS_DONE:e$ close worldliste$ !e5$ open/append world_startup vmi$kwd:world_startup.com $ write world_startup "$ !"rY$ write world_startup "$ ! Define the logical defining the default world on this system"$$ write world_startup "$ !"uB$ write world_startup "$ define/system flt$world " + default_world$ write world_startup "$ !"n$ close world_startup"$ !a $NO_WORLDS:=$ ! $ !l$ !u1$ if .not. install_examples then goto NO_EXAMPLESt$ !l $ vmi$callback restore_saveset J$ !m $ on error then goto NO_EXAMPLES$ ! <$ vmi$callback create_directory user "''examples_directory'"$ !g8$ copy/nolog vmi$kwd:*.dat;,vmi$kwd:flt$weapon*.hangar,-X vmi$kwd:flt$detachments.hangar,vmi$kwd:flt$instruments.hangar 'examples_directory'*.*;%$ purge/nolog 'examples_directory'*.* $ !o;$ open/append examples_startup vmi$kwd:examples_startup.comr$ write examples_startup "$ !"e$ write examples_startup "$ ! Define the logical name pointing to the hangar and world example files"v$ write examples_startup "$ !"M$ write examples_startup "$ define/system flt$examples ''examples_directory'" $ write examples_startup "$ !"$ close examples_startup$ !i $NO_EXAMPLES:t$ !f$ on error then exit$ !$$ ![$ startup_files = ""\$ if install_simulator then startup_files = startup_files + "vmi$kwd:simulator_startup.com,"Y$ if install_server then startup_files = startup_files + "vmi$kwd:server_startup.com,"oY$ if install_hangars then startup_files = startup_files + "vmi$kwd:hangar_startup.com,"nX$ if install_worlds then startup_files = startup_files + "vmi$kwd:world_startup.com,"[$ if install_examples then startup_files = startup_files + "vmi$kwd:examples_startup.com,"o$ !L'$ startup_files = startup_files + "NL:"e.$ copy 'startup_files' vmi$kwd:flt$startup.comg$ set file/protection=(s:rwed,o:rwed,g:rwed,w) vmi$kwd:flt$startup.com ! To accomodate INSPECT checks_$ !nJ$ vmi$callback provide_file flight$  yj~ FLIGHT031.A < [FLIGHT.FLIGHT.KIT]FLT$UID.UID;1DEVELOPMENT.COM;1ij *[FLIGHT.FLIGHT.KIT]FLT$UID.UID;1+, .i/ 4ii-<0123KPWOj5 6;g1B7w`s89@)x sGHJro|URM 1.1Motif Uil CompilerV1.1-000 8-SEP-1994 12:18:27.30FLIGHTxs c p  h L 4D< 8  0PH XWPMainWEOpenWorldDialogWESaveWorldDialogWESaveGeometryDialogWESaveSourceDialogWEMainHEMergeHangarDialogHEOpenHangarDialogHESaveHangarDialogHESaveGeometryDialogHESaveSourceDialogHEMainFSCustomFilmCanisterDialogFSCustomRecordingDialogFSCustomHangarDialogFSMainH dId (XFSMain,r-RiaTWDr4$voHreto`Pn@,fs_command_buttonslfs_message_listfs_weapon_listgfs_entrypoint_listnfs_aircraft_listfs_displays34_valuesistfs_displays34_labelsmRefs_displays12_valuesFSfs_displays12_labelsfs_displays_labelfs_scalesfs_togglesfs_server_valuefs_server_labelfs_file_buttonsfs_file_valuesfs_file_labelsH T$IT 0fs_file_labels "   %' &fs_file_buttonsHfs_file_buttonse@,fs_hangar_labelfs_recorder_labellfs_canister_label_wH XIX 4fs_canister_label H"H (y$ ISO8859-1 Film CanisterH XpIX 4fs_recorder_label H"H *y& ISO8859-1Flight RecorderH TIT 0fs_hangar_label DHH !Ty ISO8859-1HangarH LIL 0fs_file_values "   %' &fs_file_labelsfs_file_labelstone8$fs_hangar_valuefs_recorder_valuer_fs_canister_valuer_H I \4fs_canister_valuehfPFieldCreate pH P y ISO8859-1H  I \4fs_recorder_valuehfPFieldCreate pH  y ISO8859-1H | I| X0fs_hangar_valuehfLFieldCreate lpH  y ISO8859-1H h I 0fs_file_buttons "  %& &ifs_hangar_buttonfilfs_recorder_buttonfs_canister_buttonH  I 4fs_canister_button x/ PhflStartDialogH ! y ISO8859-1ChangeH L I 4fs_recorder_button x/ PhflStartDialogH ! y ISO8859-1ChangeH I 4fs_hangar_buttonn x/ PhflStartDialogro|x]] i  4  p$ L T`  s < E O ts , a H  l9 ~P lI  \ # Jl P \ d ( hnx 58  { HL `PT\ \  & l  4@Ll L , ,D (Z P  L   L j 7            R d     t h  $ H   6    l  ' H x k ,2 Y       H  } D   ` T   9      h >ClassTable>ResourceTablewp_command_buttonswp_message_listwp_entrypoint_listwp_display4_valuewp_display3_valuewp_displays34_valueswp_display4_labelwp_display3_labelwp_displays34_labelswp_display2_valuewp_display1_valuewp_displays12_valueswp_display2_labelwp_display1_labelwp_displays12_labelswp_displays_labelwp_displayrate_scalewp_scaleswp_server_valuewp_server_labelwp_canister_buttonwp_file_buttonswp_canister_valuewp_file_valueswp_canister_labelwp_file_labelsWPMainWEOpenWorldDialogWESaveWorldDialogWESaveGeometryDialogWESaveSourceDialogwe_world_buttonswe_world_separatorwe_object_buttonswe_object_listwe_canister_buttonwe_file_buttonswe_canister_valuewe_file_valueswe_canister_labelwe_file_labelsWEMainHEMergeHangarDialogHEOpenHangarDialogHESaveHangarDialogHESaveGeometryDialogHESaveSourceDialoghe_hangar_buttonshe_hangar_separatorhe_edit_instrument3_namehe_edit_instrument2_namehe_instrument23_nameshe_edit_instrument3_buttonhe_edit_instrument2_buttonhe_instrument23_buttonshe_edit_instrument1_namehe_edit_instrument0_namehe_instrument01_nameshe_edit_instrument1_buttonhe_edit_instrument0_buttonhe_instrument01_buttonshe_instrument_labelhe_instrument_separatorhe_aerodynamics_buttonshe_aerodynamics_labelhe_aerodynamics_separatorhe_object_buttonshe_object_listhe_canister_buttonhe_file_buttonshe_canister_valuehe_file_valueshe_canister_labelhe_file_labelsHEMainFSCustomFilmCanisterDialogFSCustomRecordingDialogFSCustomHangarDialogfs_command_buttonsfs_message_listfs_weapon_listfs_entrypoint_listfs_aircraft_listfs_display4_valuefs_display3_valuefs_displays34_valuesfs_display4_labelfs_display3_labelfs_displays34_labelsfs_display2_valuefs_display1_valuefs_displays12_valuesfs_display2_labelfs_display1_labelfs_displays12_labelsfs_displays_labelfs_displayrate_scalefs_fuel_scalefs_scalesfs_spinstall_togglefs_collision_togglefs_togglesfs_server_valuefs_server_labelfs_hangar_buttonfs_recorder_buttonfs_canister_buttonfs_file_buttonsfs_hangar_valuefs_recorder_valuefs_canister_valuefs_file_valuesfs_hangar_labelfs_recorder_labelfs_canister_labelfs_file_labelsFSMainFLIGHTro|PH !y ISO8859-1ChangeH I 0fs_server_label  %' t&fs_file_labels H !4y ISO8859-1ServerH  I X0fs_server_valuehfLFieldCreate   %' &/ hf _hConnectToServerfs_server_labelister_fs_server_label_hangaH  I  ,fs_togglesa "  %' &fs_server_labelnrfs_spinstall_togglefs_collision_toggleH  LI \4fs_collision_togglehfPFieldCreate p H .ly* ISO8859-1Collision detectionH  I \4fs_spinstall_togglehfPFieldCreate p H 9@y5 ISO8859-1Enhanced spin/stall simulationH ,I, ,fs_scales s "%' &  fs_togglesfs_server_value_sl_fs_displayrate_scalengafs_fuel_scaleorH  I X0fs_fuel_scalehfLFieldCreated$ !(d esH `y ISO8859-1FuelH 4I `8fs_displayrate_scalehfTreFieldCreated$ !(d H /hy+ ISO8859-1Maximum Display RateH DI 4fs_displays_labelle  %' x&fs_toggles H (y$ ISO8859-1 Crew stationsH < I 8fs_displays12_labels "  %' & (fs_displays_labelfserl_fs_display2_labelfs_display1_labelleH x I \4fs_display1_labellshfP FieldCreate pH  y ISO8859-1PilotH 8 I \4fs_display2_labellshfP FieldCreate pH #l y ISO8859-1Not UsedH H IH 8fs_displays12_valuesf "   %' &"fs_displays12_labelsl"fs_displays12_labels_labep4l fs_display2_valuelufs_display1_valueluH  8 I \4fs_display1_valueeshfP FieldCreate( xH  DECW$DISPLAYH  p0Ip \4fs_display2_valueeshfPFieldCreate(ro|DxxH HIH 8fs_displays34_labelsf "   %' &"fs_displays12_valuesl"fs_displays12_values_labep4l fs_display4_labellufs_display3_labelluH I \4fs_display3_labellshfP FieldCreate pH #\y ISO8859-1Not UsedH I \4fs_display4_labellshfP FieldCreate pH #(y ISO8859-1Not UsedH \I\ 8fs_displays34_valuesf"   %' & "fs_displays34_labelssplay"fs_displays34_labels4lH44fs_display4_valuelufs_display3_valueliH  pIp \4fs_display3_valueeshfPFieldCreateH  pdIp \4fs_display4_valueeshfPFieldCreateH  I 4fs_aircraft_listes +d  0%' &   fs_weapon_list"fs_displays12_valuesy"iH lI X0widget-0-662-16hfLFieldCreate)2 hfListBoxChangeH  0I0 4fs_entrypoint_list +d    %' &  fsfs_weapon_listfsfs_aircraft_listfs_aircraft_listH HI X0widget-0-699-16hfLFieldCreate)2 hfListBoxChangeH  I 0fs_weapon_list +     fs_message_list fH tL It X0widget-0-731-16hfLFieldCreate)H  ( I 0fs_message_list +     fs_command_buttonsfH t It X0widget-0-763-16hfLFieldCreate)H  I 4fs_command_buttons     omueH  I 0widget-0-794-16 |/ Lhfh RunFlightSimulatorH  y ISO8859-1RunH  I 0widget-0-805-16 |/ Lhfh PlaybackRecording H # y ISO8859-1PlaybackH pI 0widget-0-816-16 x/ Lhfh ResumeSuspended H !y ISO8859-1Resumero|(     pD,l(  P t8\8  D    d xT 44\      T $ l $    T    l L D      h L x   d  H @     L 4     P    ro|TH I 0widget-0-827-16 |/ Lhfh QuitFlightSimulator H y ISO8859-1ExitH I 8FSCustomHangarDialog,,- 1 0 hfuDismissDialoghfCompleteDialogs  fsH (y$ ISO8859-1 Change HangarH /y+ ISO8859-1SYS$LIBRARY:*.HANGARH ,I 8FSCustomRecordingDialog,,- 1 0 hfuDismissDialoghfCompleteDialogsfsH *py& ISO8859-1Change RecorderH ,y( ISO8859-1*.FLIGHT_RECORDERH  I  <FSCustomFilmCanisterDialog,,- 1 0 hfsmDismissDialogfhfmpCompleteDialogirH /y+ ISO8859-1Change Film CanisterH  (y ISO8859-1*.EPSH llIl (PHEMains,r-R-\L<,0fslmpX@,ahe_hangar_buttonshe_hangar_separatorhe_instrument23_namesluhe_instrument23_buttonshe_instrument01_nameshe_instrument01_buttonshe_instrument_labelhe_instrument_separatorhe_aerodynamics_buttonshe_aerodynamics_labelhe_aerodynamics_separator_she_object_buttonsvehe_object_list_he_file_buttonshe_file_values_he_file_labelsH I 0he_file_labels "   %' &he_file_buttonshe_file_buttonshe_canister_labelH X IX 4he_canister_label H"H (L y$ ISO8859-1 Film CanisterH  I 0he_file_valuese "   %' &he_file_labelshe_file_labelstonhe_canister_valuer_H  I \4he_canister_valuehfPFieldCreate pH  y ISO8859-1H  I 0he_file_buttons "  %& &he_canister_buttonaH  I 4he_canister_button x/ PhflStartDialogH ! y ISO8859-1ChangeH  @P I@ 0,he_object_listt+*    %' &   'he_aerodynamics_separatorhe_file_buttonsr_valuhe_object_buttonss_hsH  I \4widget-0-1052-16hfPFieldCreate)2 hfListBoxChangero|4H $I$ 4he_object_buttons "%' &  he_file_buttonshe_aerynshobH I 4widget-0-1086-16 / Phfl ViewObjectGeometryH "8y ISO8859-1View...H I 4widget-0-1097-16 x/ PhflStartDialogH +y' ISO8859-1Configuration...H I 4widget-0-1108-16 |/ Phfl DeleteObjectH !y ISO8859-1DeleteH I 4widget-0-1119-16 x/ Phfl StartDialogH +y' ISO8859-1Save geometry...H \I 4widget-0-1130-16 x/ PhflStartDialog H )y% ISO8859-1Save source...H 8I 4widget-0-1141-16 x/ PhflStartDialog!H -ty) ISO8859-1Flight Envelope...H  I <he_aerodynamics_separator       #he_aerodynamics_label_filH PI 8he_aerodynamics_labelto   | %he_aerodynamics_buttons#"ynH '(y# ISO8859-1 AerodynamicsH I 8he_aerodynamics_buttons "    %he_instrument_separatoreryn%$#H ,I 4widget-0-1205-16utt |/ Phfl EditLiftCurve&H "D y ISO8859-1Lift...H  I 4widget-0-1216-16utt |/ Phfl EditDragCurve'H " y ISO8859-1Drag...H  I 4widget-0-1227-16utt / Phfl EditSideLiftCurve(H ' y# ISO8859-1 Side lift...H   I 8he_instrument_separator       !he_instrument_labelhe_insH  I 4he_instrument_label   x %he_instrument01_buttons!)umH * y& ISO8859-1InstrumentationH ,d I, 8he_instrument01_buttons "    um!he_hangar_separatortoreryn%he_edit_instrument1_buttonhe_edit_instrument0_buttonH  I <he_edit_instrument0_button / XhftEditInstruments*H "y ISO8859-1Edit...ro|4H I <he_edit_instrument1_button / XhftEditInstruments+H "y ISO8859-1Edit...H \I\ 8he_instrument01_namestt "     !he_hangar_separatoryn%he_instrument01_buttonsstrume1_@s$he_edit_instrument1_namehe_edit_instrument0_namee_iH  xIx d<he_edit_instrument0_namehfXFieldCreateH  xLIx d<he_edit_instrument1_namehfXFieldCreateH XIX 8he_instrument23_buttons "     !he_hangar_separatoryn#he_instrument01_namessstme< he_edit_instrument3_buttonehe_edit_instrument2_buttoneH dI <he_edit_instrument2_button / XhftEditInstruments,H "y ISO8859-1Edit...H xI <he_edit_instrument3_button / XhftEditInstruments-H "y ISO8859-1Edit...H \TI\ 8he_instrument23_namestt "     !he_hangar_separatoryn%he_instrument23_buttonsstme@$he_edit_instrument3_namee_ehe_edit_instrument2_namee_iH  xIx d<he_edit_instrument2_namehfXFieldCreateH  xIx d<he_edit_instrument3_namehfXFieldCreateH  I 4he_hangar_separator       he_hangar_buttons H   J#~ FLIGHT031.A < [FLIGHT.FLIGHT.KIT]FLT$UID.UID;1MIN.DAT;15i6V>I 4he_hangar_buttonsr "    her4y32u1o0/.H  I 4widget-0-1501-16r / Phfl SaveHangarToFile5H  y ISO8859-1SaveH  I 4widget-0-1512-16r x/ Phfl StartDialog6H % y! ISO8859-1 Save as...H  I 4widget-0-1523-16r x/ Phfl StartDialog7H " y ISO8859-1Open...H T I 4widget-0-1534-16r x/ PhflStartDialog8H # y ISO8859-1Merge...H $I 4widget-0-1545-16r |/ Phfl CompressHangar9H #\y ISO8859-1CompressH I 4widget-0-1556-16r / Phfl ExitHangarEditor:ro| LpH y ISO8859-1ExitH I 4widget-0-1567-16r / Phfl QuitHangarEditor;H 4y ISO8859-1Quit859H I 4HESaveSourceDialog,,- 1 0 hf DismissDialoghf4CompleteDialog<=0lH 5 y1 ISO8859-1Save Object Source To FileH  $y ISO8859-1*.DATH lI 8HESaveGeometryDialog,,- 1 0 hf smDismissDialogfhf mpCompleteDialog>?H 7y3 ISO8859-1Save Object Geometry To FileH y ISO8859-1*.PSionH I 4HESaveHangarDialog,,- 1 0 hf DismissDialoglohf CompleteDialogl@AfsH .<y* ISO8859-1Save Hangar To FileH #Ty ISO8859-1*.HANGARH I 4HEOpenHangarDialog,,- 1 0 hf DismissDialoglohf CompleteDialoglBCdH &y" ISO8859-1 Open HangarH #y ISO8859-1*.HANGARISOH I 4HEMergeHangarDialog,,- 1 0 hfDismissDialoglohfCompleteDialoglDEH 'Ty# ISO8859-1 Merge Hangar H #ly ISO8859-1*.HANGARH (I( (PWEMainH,r-R we_world_buttonswe_world_separatorwe_object_buttonswe_object_listwe_file_buttonswe_file_valueswe_file_labelse%H I 0we_file_labels "   %' &we_file_buttonseparatwe_file_buttons_objecli_we_canister_label H X IX 4we_canister_label HF"hH (H y$ ISO8859-1 Film CanisterH  I 0we_file_valuese "   %' &we_file_labelsepwe_file_labelston_olwe_canister_valuer_plH  I \4we_canister_valuehfPFieldCreate pGH  y ISO8859-1ueH  I 0we_file_buttons "  %& &we_canister_buttonaH  I 4we_canister_button x/ PhflStartDialogHH !y ISO8859-1Changero| H  0I0 0we_object_listt +d    %' &   r_ we_world_separatorfilwe_file_buttonswe_object_buttonswe_fe_IlH I \4widget-0-1820-16hfPFieldCreate)2 hfListBoxChangeH DI 4we_object_buttons "%' &  we_file_buttons_separorLiKJH I 4widget-0-1854-16 / Phfl ViewObjectGeometryMH y ISO8859-1ViewsplH I 4widget-0-1865-16 x/ PhflStartDialogNH (y$ ISO8859-1 Save geometrydCH I 4widget-0-1876-16 x/ Phfl StartDialogOH &y" ISO8859-1 Save sourceH  hI 4we_world_separator       &we_world_buttonsesH I 4we_world_buttonsr "    wToSoRQPH lI 4widget-0-1927-16r |/ Phfl SaveWorldToFileUH xy ISO8859-1Saveft_H I 4widget-0-1938-16r x/ PhflStartDialogVH %Ly! ISO8859-1 Save as...H I 4widget-0-1949-16r x/ PhflStartDialogW H " y ISO8859-1Open...H  I 4widget-0-1960-16r |/ Phfl ExitWorldEditorXatH  y ISO8859-1Exit H  I 4widget-0-1971-16r |/ Phfl QuitWorldEditorY_cH  y ISO8859-1QuitH d I 4WESaveSourceDialog,,- 1 0 hf DismissDialoghf SCompleteDialogZ[H 5 y1 ISO8859-1Save Object Source To FileH  y ISO8859-1*.DATH  I 8WESaveGeometryDialog,,- 1 0 hfsmDismissDialogfhfmpCompleteDialog\]weH 7, y3 ISO8859-1Save Object Geometry To File859H Hy ISO8859-1*.PS H I 4WESaveWorldDialoge,,- 1 0 hfDismissDialoglohfCompleteDialogl^_ro| H -y) ISO8859-1Save World To File1H "y ISO8859-1*.WORLDH @I 4WEOpenWorldDialoge,,- 1 0 hfDismissDialoglohfCompleteDialogl`aH %ty! ISO8859-1 Open WorldeH "y ISO8859-1*.WORLDH I (XWPMaino,r-R  slpXt@,wp_command_buttonsfwp_message_listwp_entrypoint_listewp_displays34_valuesamewp_displays34_labelsnswp_displays12_valueswp_displays12_labelsnswp_displays_labellwp_scalesenwp_server_valuewp_server_labelwp_file_buttonswp_file_valuesawp_file_labelsaH I 0wp_file_labels "   %' &wp_file_buttonswp_file_buttons,wp_canister_labeltoSOH XIX 4wp_canister_label Hb"H (Hy$ ISO8859-1 Film CanisterH I 0wp_file_valuese "   %' &wp_file_labelswp_file_labelstonwp_canister_valuer_umH I \4wp_canister_valuehfPFieldCreate pclaH y ISO8859-1uttH I 0wp_file_buttons "  %& &wp_canister_buttonaH I 4wp_canister_button x/ PhflStartDialogdH !y ISO8859-1ChangeeH L I 0wp_server_label  %' t&wp_file_labelseesH ! y ISO8859-1ServerH  4 I X0wp_server_valuehfLFieldCreate   %' &/ hf ConnectToServerwp_server_labelwp_server_labeltonsfH ,h I, ,wp_scalesva"  %' & wp_server_valuerwp_server_valueewp_displayrate_scalest4H  I `8wp_displayrate_scalehfT"FieldCreated$ !(dfH / y+ ISO8859-1Maximum Display RateH  I 4wp_displays_labelle  %' x& wp_scalesg H * y& ISO8859-1Viewer displays I \4widget-0-1052-16hfPFieldCreate)2 hfListBoxChangero| ,H I 8wp_displays12_labels "  %' & (wp_displays_label_serr_rwp_display2_labelwp_display1_label_dH I \4wp_display1_labellshfP FieldCreate phctH &,y" ISO8859-1 Previewer 1H I \4wp_display2_labellshfP FieldCreate piH &y" ISO8859-1 Previewer 2H HIH 8wp_displays12_valuesf "   %' &"wp_displays12_labelsr"wp_displays12_labels_labep4_ wp_display2_valuerywp_display1_valueplPH  I \4wp_display1_valueeshfP FieldCreate( xj H  DECW$DISPLAY-H  pIp \4wp_display2_valueeshfPFieldCreate(H HIH 8wp_displays34_labelsf "   %' &"wp_displays12_valuesr"wp_displays12_values_labep4_ wp_display4_labelrywp_display3_labelpl H `I \4wp_display3_labellshfP FieldCreate pkH &y" ISO8859-1 Previewer 3H PI \4wp_display4_labellshfP FieldCreate plerH &y" ISO8859-1 Previewer 4H \I\ 8wp_displays34_valuesf"   %' & "wp_displays34_labelssplay"wp_displays34_labels4_H44wp_display4_valueplwp_display3_value_dEdH  pTIp \4wp_display3_valueeshfPFieldCreateH  p Ip \4wp_display4_valueeshfPFieldCreateH   H I  4wp_entrypoint_lists +d   %' &   wp_message_list"wp_displays12_valueswpam H  I \4widget-0-2495-16tshfPFieldCreate)2 'hfListBoxChangeH   I 0wp_message_list +      wp_command_buttonswnH x Ix \4widget-0-2527-16hfPFieldCreate)H  I 4wp_command_buttons     omupoH I 4widget-0-2558-16s / Phfl RunWorldPreviewerqH y ISO8859-1Viewro| T H I 4widget-0-2569-16s / Phfl QuitWorldPreviewerr+H y ISO8859-1Exit...H 0Z3$4@HWcr}4DRblt~ DXmlayoutDirectionborderWidthbottomAttachmentbottomOffsetbottomWidgetcolumnsdefaultPositiondialogTitledirMaskentryAlignmentlabelStringleftAttachmentleftOffsetleftWidgetmarginHeightmarginWidthmaximumminimumnumColumnsorientationpackingrightAttachmentrightOffsetrightPositionrightWidgetscaleHeightscaleWidthscrollBarDisplayPolicyselectionPolicyseparatorTypeshadowThicknessshowValuespacingsubMenuIdtitleStringtopAttachmenttopOffsettopWidgetvaluevisibleItemCountvisualPolicywidthxycreateCallbackactivateCallbackcancelCallbackokCallbacksingleSelectionCallbackH #Z :Vi}XmCreateFileSelectionDialogXmCreateFormDialogXmCreateLabelGadgetXmCreateListXmCreatePushButtonGadgetXmCreateRowColumnXmCreateScaleXmCreateScrolledWindowXmCreateSeparatorGadgetXmCreateTextFieldXmCreateToggleButtonGadgetEditInstruments,H "y ISO8859-1Edit...H xI <he_edit_instrument3_button / XhftEditInstruments-H "y ISO8859-1Edit...H \TI\ 8he_instrument23_namestt "     !he_hangar_separatoryn%he_instrument23_buttonsstme@$he_edit_instrument3_namee_ehe_edit_instrument2_namee_iH  xIx d<he_edit_instrument2_namehfXFieldCreateH  xIx d<he_edit_instrument3_namehfXFieldCreateH  I 4he_hangar_separator       he_hangar_buttons H  I 4he_hangar_buttonsr "    her4y32u1o0/.H  I 4widget-0-1501-16r / Phfl SaveHangarToFile5H  y ISO8859-1SaveH  I 4widget-0-1512-16r x/ Phfl StartDialog6H % y! ISO8859-1 Save as...H  I 4widget-0-1523-16r x/ Phfl StartDialog7H " y ISO8859-1Open...H T I 4widget-0-1534-16r x/ PhflStartDialog8H # y ISO8859-1Merge...H $I 4widget-0-1545-16r |/ Phfl CompressHangar9H #\y ISO8859-1CompressH I 4widget-0-1556-16r / Phfl ExitHangarEditor:&][~ FLIGHT031.Ag b [DECWINDOWS-HELP]FLT$HELP.HLB;5_FULL.DAT;15*[DECWINDOWS-HELP]FLT$HELP.HLB;5+,g ./ 4-b 0123 KPWO56-颔7:w`s89@)x sGHJz% VAX-11 Librarian V04-00颔颔5$FSeHEWEWP 颔1 FS 2 OVERVIEW=TITLE Overview=INCLUDE FS BASICS=INCLUDE FS FAA_CERTIFICATION=INCLUDE FS KEYBOARD=INCLUDE FS START_PREREQ=INCLUDE FS CONFIGURE_AIRCRAFT=INCLUDE FS CONFIGURE_WORLD=INCLUDE FS HISTORY9FLIGHT's Flight Simulator component allows you to pilot a7wide variety of aircraft in any of the available FLIGHT environments.9FLIGHT performs realtime, three dimensional simulation of:aircraft on any X-windows workstation. The display of theworld  is wireframe, not solid.FLIGHT supports1- Takeoffs and landings, including undercarriage< and flap controls, as well as catapult and ramp takeoffs.:- All forms of flying, including supersonic, subsonic and9 hovering aircraft such as the AV-8B Harrier II and the* Bell 206B JetRanger III - a helicopter.- Acrobatic flying4- Instrument navigation, including ADF and VOR/ILS.3- Weapons, including air-to-air and air-to-surface9 guided missiles, gravity weapons, trace rs and remotely piloted cruise missiles. :- Distributed simulations, allowing for multiple users to( fly together in the same environment.5- Multi-user simulations, allowing for more than one: workstation to be used for a particular aircraft. This; allows for trainers and adding crews to larger aircraft.:- General terrain in simulator environments, allowing for# mountains, cliffs, canyons, etc.;- Color display, smooth animation, and display rates which* may be  as high as 30 frames per second.;In addition to these features, you can use other components:of FLIGHT to build your own aircraft, weapons, instrumentsand simulator environments.;For more information about using FLIGHT, double click on an.item from the list of additional topics below.;When you see a topic that lists no additional topics, click7on the Go Back button to return to the topic previously:viewed, or choose Go To Overview from the View menu above.;For more information a bout using help, choose help from theHelp menu above.2 ABOUT =TITLE About=INCLUDE FS OVERVIEW=INCLUDE FS HISTORYDECwindows FLIGHT$Software Version: FLIGHT Version 2.52For more information about FLIGHT, double click on*Overview from the additional topics below. 2 HISTORY=TITLE Brief History of FLIGHT;Development of FLIGHT began in February of 1986 in response2to a simulation application which ran on DEC video5terminals. It was such a crude simulator that it was; decided to pursue the construction of a rather more serious simulator.<The work was begun by John Buehler and Andr Pavanello, with;consulting aid by Jim Roth and Phil McKinley. At the time,2the fastest DEC graphics machine available was the:VAXstation I, a 0.3 VUP B&W workstation capable of drawing&perhaps one hundred vectors per second9The first prototypes were incredibly crude experiments in;becoming familiar with animation of wireframe objects. The6prototypes used an internally- developed form of 3D GKS:(Graphical Kernel System). Typically, frame rates were in9the neighborhood of 1 frame per second. These prototypes7merely displayed wireframe objects from various angles.:When construction of the actual V1.0 software was started,6basic aircraft simulation (aerodynamics) were added, a;custom-designed 3D display package was built (by Jim Roth),;basic aircraft instrumentation was added (by Dave Griffin),<and several aircraft models were constructed, as well as the <environment in which the aircraft were intended to fly. The8display was targetted for a VAXstation II running UIS, a&DIGITAL-proprietary windowing package.8The first aircraft models were very spartan. Typically,9they consisted of less than 30 lines (one had only 6) and;had no working parts. All were hardwired into the code and;lacked most of the more sophisticated aspects of the models'found in the current version of FLIGHT.9Similarly, the single simulator environment was extremely;simple, consisting of a single cross-shaped airport runway,8two simple towers and a set of pyramid-shaped mountains.<Follow-on versions of FLIGHT came quickly, usually spaced by7several months. The following are the hilights of eachversion:V1.0 25-JUN-1986 UIS<Introductory version. Fixed set of aircraft, one world, one3weapon type. Distributed simulations and collision9detection supported. Single missile in flight at a time.V1.1 24-SEP-1986 UIS.User-defined aircraft supported. User-defined8instrumentation supported. RADAR instrument introduced.Smooth animation introduced.V1.2 16-DEC-1986 UIS<Distributed simulation support dropped. CONTROL and DIGITAL2instruments introduced. User-defined environments6supported. Level Of Detail specifications introduced.V1.3 14-FEB-1987 UIS4SLIDER, DIAGRAM and HORIZON instruments introduced. :Simulation of flaps introduced. Multiple world viewpoints3supported. Simulation of ground effect introduced.V1.4 21-MAY-1987 UIS4Distributed simulations restored. Stationary object=support. World previewer added. ADF instrument introduced. 9As many as 20 weapons may be in the air at the same time.V1.5 15-AUG-1987 UIS6Addition of numerous data basis keywords. VOR/ILS and3TOGGLE instruments introduced. Manual engine start required.V1.6 3-FEB-1988 UISRefinements and bug fixes.V1.7 25-MAR-1988 UIS<The flight recorder is introduced. Radar-guided weapons are-introduced. Numerous modelling enhancements.V2.0 15-AUG-1988 DECwindows4DECwindows port. Support for UIS is dropped. 7 newaircraft added.V2.1 3-OCT-1988 DECwindows9Support for the IF command in keyboard bindings. Supportfor DIAGRAM instrument dropped.V2.2 15-JAN-1989 DECwindows9Support for DISPLAY/PANEL/VIEWPORT structure introduced. 6Numerous modelling enhancements, including support for0takeoff ASSISTS and MASSes in worlds. Over 1000!installations logged in 8 months.V2.3 1-OCT-1989 DECwindows9Redesign of User Interface. World editor introduced. 3D7world definition introduced. Crew support introduced. <Improved support for HUDs introduced. Double precision math;introduced, expanding FLIGHT's useable simulation area from5a 500 mile radius sphere to one which encompasses theEarth/Moon system and beyond.V2.4 1-MAY-1990 DECwindows@Turn/Slip instrument added. World Previewer returns. Extensive=world modeling bug fixes. Refinements to treatment of radar.6Firing sequences introduced. Important simulation bug fixes made.V2.5 1-JUL-1991 DECwindows<'Two-wing' simulation is introduced, increasing the accuracy<of the aerodynamic simulation, particularly at higher angles:of attack. This release is provided to the DECUS softwarelibrary.0From V1.0 through the present, all time spent on:construction of FLIGHT has been performed during the spare8time of employees. It should be recognized that DIGITAL;ma nagement has been supportive of the development effort at all times.<Many thanks go to all the DIGITAL employees who have donated;their time to construct models for FLIGHT and to consult on6various aspects of the simulation. Currently, the kit4contains over 60 aircraft types and a dozen weapons,7including air-to-air and air-to-surface missiles. Also:included are several standard worlds, and others are under3construction. Be sure to take note of the aircraft9designers, whose names app ear next to the aircraft in thesimulator user interface.8Thanks also to those who have helped with the testing of8FLIGHT both formally and informally and for providing so;many ideas for ways in which the software could be improved:and for all the information about aircraft and simulators.6Special thanks to Tom Dahl for his invaluable software;efforts on FLIGHT, for providing so many accurate, detailed<aircraft and world models and for acting as a co-conspirator:on many of the ideas that have made their way into FLIGHT.It's been fun.; John Buehler9 Nashua, NH9 1-JUL-19902 FAA_CERTIFICATION=TITLE FAA Certification Level5FLIGHT has not been certified by the Federal Aviation:Administration (FAA) at any level and does not fulfill the*requirements for time spent on simulators.2 BASICS=TITLE FLIGHT Basics=INCLUDE FS KEYBOARD=INCLUDE FS START_PREREQ=INCLUDE FS CONFIGURE_AIRCRAFT=INCLUDE FS CONFIGURE_WORLD9FLIGHT allows configuration and execution of a simulation5through the DECwindows interface which you see on the workstation.:In general, the configuration which you may perform allows6you to specify which aircraft you want to fly from the<current collection of aircraft (known as a hangar), how much8fuel you want and where in the simulator environment you:wish to start. You may also change simu lator environments-and hangars as well as several other options.9To run a simulation, you select the Run Simulation option9from the Control menu. This will cause the simulation to;begin, presenting you with a display of the interior of the:aircraft cockpit. This display will vary from aircraft to<aircraft, but is generally limited to one or more instrument<panels and one or more world viewports. These viewports are6displays showing you, the pilot, what you see from thecockpit of your aircraft.3Once started, you control the simulator through the9workstation keyboard, mouse, and through software toggles9which appear on the instrument panel. A simulation stops9and you are returned to the DECwindows interface whenever:your aircraft is destroyed, or you choose to exit from thesimulator by pressing KP-MINUS.2 START_PREREQ-=TITLE Prerequisites to Starting a Simulation=INCLUDE FS HANGARS=INCLUDE FS SIMULATION_SERVERS9There are two conditions which must be satisfied before a$simulation may be started. They are 1. A FLIGHT Hangar is loaded.2 2. A FLIGHT Simulation Server connection exists.:See the Additional Topics below for more information aboutHangars and Simulation Servers. 2 HANGARS=TITLE Hangars=INCLUDE FS CONFIGURE_AIRCRAFT8A Hangar is a file containing a collection of aircraft. :From this collection you may select an aircraft to perform;your simulation in. Unless a Hangar is loaded, FLIGHT will9not have the infor mation necessary to start a simulation.6Hangars have the file type HANGAR and are installed by9FLIGHT in the directory SYS$LIBRARY. They contain all of:the aircraft provided by FLIGHT. To load any of them, use:the Configure menu's Change Hangar File option. This will;display a dialog box listing the available hangars. Select8one and click on OK. This will cause FLIGHT to load the7selected Hangar, making all the aircraft in that Hangar<available to you. See Configuring an Aircraft in the topics/below for information about selecting aircraft.<Note that it is possible to build your own Hangars with your.own aircraft using other components of FLIGHT.2 SIMULATION_SERVERS=TITLE Simulation Servers=INCLUDE FS CONFIGURE_WORLD=INCLUDE FS COLLISION_DETECTION7A Simulation Server is a computer node running FLIGHT's7Simulation Server software. You must be connected to a7Server in order for FLIGHT to run. This is because the5simulator environment is obtained from  such a Server.4The task of connection is trivial. By selecting the<Configure menu's Configure World option, FLIGHT will display:the Configure World dialog box. In this dialog box, there9is a field titled Server. Merely type in the name of any5computer node which you know to be running the FLIGHT6Simulation Server software and click on the Connect toServer button.9The Flight Simulator main window will indicate whether or7not the connection was successfull. As a simple way of;kn owing if a connection was successfull, merely look at the9contents of the list box below the Server field. It will1contain a list of entry points into the simulator4environment loaded from the Simulation Server if theconnection was successfull.;Note that it is possible to build your own environments for5use with Simulation Servers using other components ofFLIGHT.2 CONFIGURE_AIRCRAFT=TITLE Configuring an Aircraft=INCLUDE FS CONFIGURE_WORLD=INCLUDE FS HANGARS=INCLUDE FS !CREW_AIRCRAFT5Configuration of an aircraft is performed through the:Configuration menu's Configure Aircraft option. Selecting6that option will cause FLIGHT to display the ConfigureAircraft dialog.5The Configure Aircraft dialog allows you to select an:aircraft in the current hangar, set the amount of fuel for;the aircraft to carry, and configure the aircraft for using7multiple workstations (if the aircraft is so designed).9Configure the aircraft the way you want it, then click on"8OK. As a shortcut, you can double-click on an aircraft,9which will select the aircraft and OK the dialog for you.9See the additional information below for more information;about using multiple workstations for a single aircraft and other topics.2 CONFIGURE_WORLD=TITLE Configuring a World=INCLUDE FS CONFIGURE_AIRCRAFT=INCLUDE FS SIMULATION_SERVERS#=INCLUDE FS DISTRIBUTED_SIMULATIONS=INCLUDE FS COLLISION_DETECTION1Configuration of a world is performed through the<Config #uration menu's Configure World option. Selecting that7option will cause FLIGHT to display the Configure Worlddialog.8The Configure World dialog allows you to select an entry:point in the current world, turn collision detection on or9off and change the Simulation Server being used. See the4additional information below for more information onSimulation Servers.8Configure the world controls the way you want them, then7click on OK. As a shortcut, you can double-click on an9entry po$int, which will select the entryp oint and OK thedialog for you.2 DISTRIBUTED_SIMULATIONS=TITLE Distributed Simulations=INCLUDE FS SIMULATION_SERVERS=INCLUDE FS COLLISION_DETECTION=INCLUDE FS CREW_AIRCRAFT:A distributed simulation is one in which multiple aircraft:are all flying in the same environment. That is, they are;using the same Simulation Server. Indeed, that is all that;is required for a distributed simulation to be created; all:interested users should specify th%e same Simulation Servernode.7A maximum of 8 users may connect to the same SimulationServer.:A distributed simulation is not used for allowing multiple<users per aircraft. This is described in "Crews", which can-be found in the additional information below.2 COLLISION_DETECTION=TITLE Collision Detection=INCLUDE FS CONFIGURE_WORLD=INCLUDE FS SIMULATION_SERVERS7Collision Detection is the term used for the process of<determining when a moving object (aircraft, weapon, et &c) has-struck another object (moving or stationary).9A moving object may collide with another moving object (a:tracer round striking another aircraft) or a moving object7may collide with a stationary object (a bomb striking a5building). In both of these situations, it is highly:dependant upon the particular objects colliding as to what6the results will be. Many objects merely explode when8struck, while others may be damaged a little at a time. ;This is up to the designer of the object 's concerned and you8will generally find out what happens by trial and error.8Collision detection is not used for determining when you:come in contact with the ground. This includes mountains,1valleys and other terrain-like surfaces. This is;significant because you can turn collision detection on and8off freely, while terrain detection is always in effect.<To determine whether collision detection is on or off, bring;up the Configure World dialog box. See Configuring a World<for how (to do this. In that dialog there is a toggle button<which is labelled "Collision detection". If it is lit, then<collision detection will be performed for you. If not, then<no collision detection will occur. You may turn this toggle7to any desired state before each simulation is started.6If collision detection is off, you will be able to fly;through any world object without fear of damage - unless it<also contains terrain information. Remember that terrain is9always solid. The difficu )lt part as a user is to realize4that things like buildings may be modelled either as;terrain, or as objects which are affected by this collisiondetection toggle.;In general, you can turn collision detection off if you are3merely flying in civilian aircraft and are not very8interested in the objects around you except as reference7points. If you don't need it, don't use it. Collision6detection can be expensive, and it is performed by the4Simulation Server. Eight users requesting col*lision:detection from the same Simulation Server may slow it down8considerably. If eight users request it, be sure that a5fast enough machine is running the Simulation Server.9If you are dogfighting or otherwise attempting to destroy:objects, you should leave collision detection on. Turning;off collision detection means that you and your weapons are8like ghosts and can neither damage other aircraft nor bedamaged by them.2 CREW_AIRCRAFT =TITLE Crews=INCLUDE FS CONFIGURE_AIRCRAFT +9The Configure Aircraft dialog contains three fields which:relate to configuration of crew simulations. They are the8three text fields at the right of the dialog. Each text;field wants to contain the name of a DECwindows workstation3which you are authorized to create a connection to.:To the left of each text field is a label. It will either<read "Unused" or will contain some name indicating what crew=member a display has been configured for, such as "Copilot". ;A value of "Unused ," means that there is no crew display for;that position and the workstation name to its right will beignored.7Any other value means that if you type in the name of a:DECwindows workstation into the text field to the right of1the label, FLIGHT will display that crew member's;instruments and viewports on the specified workstation. If9there is no workstation name specified for a crew member,5then the crew member's display is not created at all.6Note that the pilot's display is alway -s created and is9presented to you on this workstation. There is no way to disable this.9Each crew member's display runs in real time, just as the5pilot's display. When a crew member invokes the EXIT=command, only that crew member's display will be taken down. ;The simulation will continue unless the crew member exitingis the first crew member.6Also, control instruments which appear on various crew<member displays may control the same aircraft function. For5example, a Pilot and . Copilot display may both contain1control sticks for flying the aircraft. In these5situations, one crew member should lock their control9instrument and the other should unlock the control. This;ensures that the correct crew member is actually flying the:plane. The other crew member will see the control motions5of the crew member actually controlling the aircraft. 2 KEYBOARD=TITLE Keyboard Functions=INCLUDE FS VIEW_CONTROLS=INCLUDE FS ENGINE_CONTROLS=INCLUDE FS FLAPS_CONTRO/LS=INCLUDE FS CONTROL_STICK=INCLUDE FS FLIGHT_RECORDER=INCLUDE FS BRAKE_CONTROLS=INCLUDE FS WEAPON_CONTROLS=INCLUDE FS EXITING=INCLUDE FS RADIO<Most simulator functions have been, by default, bound to key9sequences on the workstation keyboard and mouse. Not all8functions will work with all aircraft, and some aircraft<have additional functions available through software toggles)which are displayed on instrument panels.8While FLIGHT provides default keyboard bindings, you c 0an<change them by modifying the file SYS$LIBRARY:FLT$KEYMAP.DAT:This is where FLIGHT looks to determine the meaning of all;keyboard sequences. The documentation provided with FLIGHT7only describes the default keyboard and mouse bindings.;In the description of each key sequence, the FLIGHT command6which is bound to that key sequence is listed as well.:The file SYS$HELP:FLT$KEYMAP.PS is a PostScript file which6shows the keyboard arrangement of the various keyboard5functions that FLIGHT 1provides. A PostScript-capable/printer is required in order to print the file.9See the additional information below for a description of;the functional areas of the simulator available through thekeyboard and mouse.2 VIEW_CONTROLS=TITLE View Controls8FLIGHT provides extensive viewing controls which allow a9user to look around while in the aircraft cockpit, change9between multiple view locations in the aircraft, or watch;the aircraft from a variety of stationary locations ou2tside the aircraft.KP7SET VIEW_MODE PILOT:This causes FLIGHT to display the currently selected pilot.view with the aircraft geometry not displayed.PF1-KP7SET VIEW_MODE ALTERNATE:This causes FLIGHT to display the currently selected world<view such that the current aircraft is always being visuallytracked.PF3-KP7$SET VIEW_MODE PILOT/AIRCRAFT_VISIBLE:This causes FLIGHT to display the currently selected pilot;view with the aircraft geometry displayed. This may give 3a:more realistic quality to the simulation over the function available from the sequence KP7.PF2-KP1 ... PF2-KP9SET ALTERNATE_VIEW n9These sequences select between the various world views in6the current world. PF2-KP1 shows the first such view,;PF2-KP2 shows the second, etc. The world view windows will9be titled by the name of the world view location that youhave selected.<Whenever you are viewing a simulation from a world view, the9aircraft you are flying is tracked such th 4at it is always:located in the center of the display. You can zoom in and&out on your aircraft to better see it.PF3-KP1 ... PF3-KP9SET PILOT_VIEW direction;These sequences each select a direction to look at while in<the pilot view mode. PF3-KP2 looks backwards, PF3-KP6 looks;right, PF3-KP4 looks left, etc. If you look at the numeric8keypad, you will see the relationship between the number:selection and the direction they correspond to. Note that4PF3-KP4 looks up and PF3-KP9 loo5ks down. PF3-KP7 is"reserved for a different function.PF4-F1 ... PF4-F20SET PILOT_VIEW/VIEW=n:These sequences each select a different pilot view to look6from. For example, the default pilot view (PF4-F1) is:usually a view in the aircraft from where the pilot sits. 6Other pilot views can show the copilot view, passenger<views, bombardier views, etc. The aircraft designer decides(the number and placement of pilot views.Find CYCLE VIEW8This key causes FLIGHT to cycle between th6e various view9directions from the current pilot view. It is similar in<function to the PF3-KPn sequences which allow you to look in8specific directions. The FIND key allows you to look in9each direction in sequence, except for looking down. The3order of views that the FIND key cycles through is:"FORWARD, RIGHT, BACKWARD, LEFT, UP Next ScreenZOOM IN4This key works two ways. The first is while you are8watching your aircraft from a world view. It causes the<view to zoom in on 7 the current aircraft. You may repeatedly9zoom in until the aircraft is as large as you like. Note:that the world view tracks a little behind moving aircraft%to give a better sense of its motion.=The second behavior is for when you are inside the aircraft. 8A pilot view may have magnification controls to it. The<number and power of the magnification controls is determined<by the aircraft designer, but you may select between them by<pressing the Next Screen key. Each press of the Next 8Screen5key causes the next magnification level to be used todisplay the pilot view. Prev ScreenZOOM OUT7This key works just like the Next Screen key, except inreverse.PF1-Next Screen ZOOM IN/MAX;This sequence produces the same effect as pressing the NextScreen key 10 times.PF1-Prev Screen ZOOM OUT/MAX:This sequence causes all zooming of a view to be cancelled;out to the default levels that were set at the beginning of;the simulation. It will only affect the c9urrent view mode,$which will be either pilot or world.2 ENGINE_CONTROLS=TITLE Engine Controls<These controls are for controlling the engine throttle. You<must use the screen toggle available on all aircraft to turnthe aircraft engine on.;It is possible for the engine to shut down for a variety of;reasons. If this happens, the only thing you need to do is6to use the screen toggle to turn the engine back on by4flipping it to the off position and then back to on.Up ArrowSE:T THROTTLE INCREASE<Each press of this key will increase the throttle setting by;one step. The size of a step is determined by the aircraft6designer. Usually, there is an instrument showing the2throttle setting and current engine power setting. Down ArrowSET THROTTLE DECREASE9This is identical in function to the Up Arrow key, except%that it reduces the throttle setting. PF1-Up ArrowSET THROTTLE FULL%This sets the throttle to full power.PF1-Down ArrowSET THROTTLE N;ONEThis sets the throttle to idle.DOSET THROTTLE AFTERBURNER:This sets the throttle into the afterburning position. An<afterburner is a feature of most modern military jet engines<and can provide a significant increase in engine power for a<tripling (or more) in fuel consumption. Whether an aircraft:has an afterburner is determined by the aircraft designer.9Note that the afterburning throttle setting is requesting:more power than PF1-Up Arrow, which requests 'full' power.<2 FLAPS_CONTROLS=TITLE Flaps Controls<There are only four controls for flaps. They lower or raise4the flaps by increments or provide full or no flaps.KP3SET FLAPS INCREASE;This increases the amount of flaps lowered by the increment:that the aircraft designer has established. Some aircraft:do not have flaps. Increasing the amount of flaps lowered7tends to increase both the lift and drag aspects of thewing.KP6SET FLAPS DECREASE;This has the reverse effect of PF3. T=hat is, it raises theflaps by one step.PF1-KP3SET FLAPS FULL7This causes full flaps to be lowered, providing maximumeffect on lift and drag.PF1-KP6SET FLAPS NONE9This causes the flaps to be fully raised, eliminating theeffect on lift and drag.2 CONTROL_STICK=TITLE The Control Stick=INCLUDE FS WEAPON_CONTROLS;FLIGHT provides the CONTROL instrument as the primary means5of fine control of an aircraft's functions. The most9obvious example of this is the joyst >ick or control column9found in aircraft. This is the physical instrument which;the CONTROL instrument is designed to represent. A CONTROL;instrument may also be used to position moveable weapons orclose an aircraft canopy, etc.:On the screen, a CONTROL instrument appears as a rectangle:of some arbitrary size with tick marks on the midpoints of2the sides, a center set of tick marks and a circle(indicating the current control position.:When the circle is filled solid, the CONTROL ins5;~ FLIGHT031.Ag b [DECWINDOWS-HELP]FLT$HELP.HLB;5IN.DAT;15|>?trument is:said to be locked. It will not respond to movement of the7mouse. When the circle is only an outline, the CONTROL6instrument is said to be unlocked. It will follow the8motion of the mouse pointer on the screen, regardless of8whether or not the mouse pointer is in the control area.9When a simulation is started, all CONTROL instruments arelocked.MB1 (mouse button 1)SET CONTROL LOCK TOGGLE4This causes FLIGHT to change the lock on any CONTROL2instruments which the mous@e pointer is in. If the2instrument is locked, this will unlock it. If the:instrument is unlocked and, therefore, tracking the mouse,this will lock it.MB3 (mouse button 3)SET CONTROL HOME VERTICALSET CONTROL HOME HORIZONTALSET RUDDER CENTER<This causes FLIGHT to center the CONTROL instrument that the1mouse pointer is in. It also centers the rudder.:Note that MB2 (mouse button 2) is used for weapons controlin the default bindings.2 FLIGHT_RECORDER=TITLE The Flight Re Acorder=INCLUDE FS RECORDER_KEYS;FLIGHT provides a flight recording capability for recording:what happens during an interactive simulation. It records6what happens to you and to any weapons which you might:launch. It does not record what happens to objects in the2world, including other aircraft and their weapons.9In order to record or replay a simulation, you must first:load a flight recorder tape (a file) before the simulation9begins. This is accomplished by selecting "Set Recordin Bg9File..." from the Playback option of the File menu in the8Configuration dialog. This will present you with a file8selection dialog which allows you to specify an existing<recording file or a non-existent file, indicating the FLIGHT+should create a new recording file for you.;Once loaded, you have the option of replaying the recording*or recording a new simulation in the file.6If you choose to record a simulation, merely start the;simulator as usual using the Run option, then press Cthe F118key. This is the RECORD key of the flight recorder. It:begins the recording process just as a tape recorder does.;Until you exit the simulator or stop the recorder using the5F13 key (STOP), each frame of your simulation will be;recorded to the file that you loaded as the flight recordertape.5If you choose to replay a recorded simulation, select9"Playback Recording" from the Playback option of the File8menu in the Configuration dialog. This will immediately6begin replayin Dg the original simulation, complete with;weapon launches. Until the recording completes or you stop3the recorder using the F13 key (STOP), the original recording will continue to play.4In general, you should assume that three frames of a7recording of a single aircraft flying around requires 19block of disk space. If you are running a simulator at 55frames per second, then each minute of recording will9require somewhere around 40 blocks of disk space. FLIGHT1recording tapes grow in Eincrements of 128 blocks.:See the Additional Topics below for more information aboutthe flight recorder controls.2 RECORDER_KEYS=TITLE Flight Recorder Controls;FLIGHT provides controls for the flight recorder which very8closely parallel the controls of a typical cassette tape recorder.F11SET RECORDER RECORD<This causes FLIGHT to begin recording the current simulation:onto the current recording tape which has been loaded. If6no tape is currently loaded, this functionF is ignored.6Note that you may start and stop recordings many times;during a simulation, just as a conversation may be recorded'at random moments onto a cassette tape.F12SET RECORDER REWIND:This causes FLIGHT to move to the beginning of the current<recording tape in order to begin playback or record over the9beginning of the tape. Note that when a recorder tape is<first loaded, it is positioned at the beginning of the tape.F13SET RECORDER STOP<This causes FLIGHT to stGop the RECORD or PLAY operation that:was currently in progress. If a PLAY is stopped, then the<windows displayed for the simulation playback are taken down:and you are returned to the Configuration dialog box. If a<RECORD is stopped, then the tape remains positioned where it9is and no more frames will be recorded until F11 is againpressed.F14SET RECORDER FPLAY4This causes FLIGHT to fast-forward one step during a9playback of a recording. It may be repeatedly pressed to9produce faHster and faster playbacks or to slow or pause a:fast backwards playback. A normal playback is forwards ata speed of 1:1PF1-F14SET RECORDER RPLAY<This causes FLIGHT to fast-reverse one stp during a playback8of a recording. It may be repeatedly pressed to slow or5pause a fast-forward playback or to actually make therecording play backwards.PF2-F14SET RECORDER PPLAY:This causes FLIGHT to pause the playback at whatever frame;is currently being displayed. To start the playIback again,7use F14 or PF1-F14 to playback the recording forward orbackgwards, respectively.2 BRAKE_CONTROLS =TITLE Brakes:There are only four controls for brakes. They increase or<decrease the brake setting by increments or apply full or no<brakes. The effectiveness of brakes varies from aircraft to<aircraft. In the default aircraft, the general rule is that9full brakes can oppose full, but non-afterburning, enginepower on a level surface.9Note that for simulating arresteJd landings (such as on an6aircraft carrier), it is suggested that you apply full:brakes while still in the air. When you land, you will be4stopped as quickly as the aircraft allows for. Some<aircraft have excessively effective brakes to allow for this very thing.KP4SET BRAKES INCREASE9Each press of this key will increase the brake setting by;one step. The size of a step is determined by the aircraft designer.KP1SET BRAKES DECREASE<This is identical in function to tKhe KP4 key, except that itreduces the brake setting.PF1-KP4SET BRAKES FULL7This sets full brakes. Brakes are assumed to be of the7anti-skid variety, so you cannot lock up the brakes andskid.PF1-Down ArrowSET BRAKES NONE$This releases the brakes completely.2 WEAPON_CONTROLS=TITLE The Weapon System=INCLUDE FS GUIDED_WEAPONS:FLIGHT provides for a wide range of weaponry to be carried7onboard each aircraft. However, the number and type of;weapons carried is det Lermined by the aircraft designer. At8present, you must carry the single weapon load which theaircraft designer has picked.;The onboard weapons are organized into 4 firing sequences. 8You may select between the firing sequences using the F19through F4 keys. Firing of the currently selected firing:sequence is achieved by clicking MB2. The definition of a;particular firing sequence is set by the aircraft designer.<As an example, sequence 1 might be guns, sequence 2 might be5SidewinderM missiles, sequence 3 might be Sparrows andsequence 4 might be Chaff.7Although the above describes a select-then-fire mode of9interaction, you may also fire a sequence directly by the8use of the F17 through F20 keys, each of which fires the9sequences 1 through 4 respectively, without regard to thecurrently selected sequence.<Once fired, a weapon will fly until it collides with another7object, the ground, or until it decides that it has hadenough and destroys itself.;An unlimitNed number of weapons may be launched/fired at any7one time, but the more weapons you fire, the slower thesimulator will become.F17 through F20WEAPON FIRE 1 through 43This causes FLIGHT to fire weapons according to the8specified firing sequence (1 through 4). If there is no7next weapon in the sequence, the sequence is consideredempty and a bell will sound.MB2 (mouse button 2)WEAPON FIRE SELECTED8This causes FLIGHT to fire the currently selected firing:sequence. If therOe is no next weapon in the sequence, the3sequence is considered empty and a bell will sound. F1 through F4WEAPON SELECT 1 through 4;This causes the current firing sequence to be set according;to the key you press. Once selected, a firing sequence maybe activated by pressing MB2.COMMA LOAD WEAPONS;This causes FLIGHT to rearm the aircraft with a full weapon5load. This may be performed any time the aircraft is9stopped and on the ground. This may also be performed as8maPny times as you like. Pressing the COMMA key multiple5times will not give you more than a full weapon load.2 GUIDED_WEAPONS=TITLE Guided/Smart Weapons=INCLUDE FS RADAR_WEAPONS=INCLUDE FS SURFACE_WEAPONS;Part of FLIGHT's weaponry capabilities includes the ability9for designers to build smart weapons which are capable of8guiding themselves to a target. In the default hangars,0there are a variety of guided weapons including:AIM-7F Sparrow MissileAIM-9L Sidewinder MissileQAGM-65A Maverick Missile9The Sparrow and Sidewinder missiles are what FLIGHT calls:RADAR guided weapons. The Maverick missile is what FLIGHTcalls a SURFACE guided weapon.2 RADAR_WEAPONS%=TITLE Launching RADAR-guided Weapons9In order to launch a radar-guided missile, you must first6arm your weapons system. This is done by pressing the6PERIOD key on the keypad. Once this is done, the lead6weapon in the selected firing sequence begins actively;searching out targets. When it findRs a target, they notify'the aircraft that they are ready to go.:Each aircraft may optionally display this information in a:variety of ways. In the F18, F14A and F16C, there are HUD:indicators to show what object is locked onto. The HUD is6made visible in some aircraft by enabling the weapons.9Once lock-on has been achieved, you may launch the weaponwhenever you like.9Once launched, you may begin searching for a new target. 5The RADAR-guided weapons are fire-and-forget weapons,8Smeaning that once you have fired them, you needn't worry;about keeping them on track to their target. They have all7the machinery they need to do that onboard the missile.2 SURFACE_WEAPONS'=TITLE Launching SURFACE-guided Weapons;In order to launch a surface-guided missile, you must first6arm your weapons system. This is done by pressing the9PERIOD key on the keypad. Once this is done, you need toselect a target.;Target selection is achieved by merely getting the heads-up9bo Tresight dot to be touching the point on the ground that;you want to hit. Note that you must point at a location on3the ground, not at an object. The SURFACE guidance:capability is not aware of objects in the world. It locks;onto a coordinate in the world and then attempts to hit it.8If you aim at the top of a building, the weapon will hit7somewhere behind it because that is the location on the*ground that you were actually pointing at.5Note that a SURFACE-guided weapon locks onto a t Uarget4location at the moment that it is fired, not before.9Once launched, you may begin searching for a new target. 7The SURFACE-guided weapons are fire-and-forget weapons,8meaning that once you have fired them, you needn't worry;about keeping them on track to their target. They have all7the machinery they need to do that onboard the missile.;Frequently, because of the accurate aiming needs of SURFACE8guided weapons, aircraft designers provide extra zooming6capabilities on their aiVrcraft to allow for more exact pointing. 2 EXITING&=TITLE Exiting/Suspending a Simulation9There are three interrelated functions which allow you to9exit a simulation, suspend a simulation or do both at the same time.MINUSEXIT9This causes FLIGHT to exit the current simulation for the;user invoking the EXIT function. If any other crew members.exist , the simulation will continue for them.;If no other crew members exist, the simulated aircraft will be destroyed.9If the Wre are other objects which have crew members in the5same simulation (e.g. piloted weapons, etc), then the;overall simulation continues until all users have exited or"their aircraft has been destroyed. PF2-MINUSSUSPEND8This causes FLIGHT to write the current simulation state:into a file which you must have specified before starting;the simulation. This is done via the Suspend/Resume option:of the Control pulldown in the main simulator dialog. The9Set Suspend File... option allowXs you to load an existing5recording or create a new recording. Note that these8suspend files are, in fact, FLIGHT recordings which lastonly a single frame.;Suspending a simulation does not stop it. It merely causes7the suspend file to be created. Multiple suspends willoverwrite prior suspends. PF1-MINUS SUSPEND/EXIT;This combined the previous two functions. It is completely'equivalent to SUSPEND followed by EXIT.2 RADIO=TITLE The Radio4FLIGHT provides an instrum Yent which is found in most<aircraft which is a simulation of a radio. Because it's not8possible to actually handle spoken transmissions, FLIGHT6allows typing on the keyboard to be transmitted at the3frequency that the radio is set to. Your typing is-transmitted as you type it, letter by letter.<A radio appears as a box with a frequency indication and two<lines in which text appears. The top line shows what others7are transmitting on your frequency, and the bottom line;shows what you h Zave typed. In the case of an aircraft with9multiple radios you do not need to worry about indicating6which radio you want to transmit on. As you type, the7typing is transmitted on each frequency that a radio is tuned to.:You may transmit at the same time that you are receiving. 4However, this may result in a third party seeing two;transmissions at the same time, resulting in garbage on hisradio.;The following editing is allowed as you type. Because each<key you type is transmit[ted as you type it, the editing that;you see will be seen by others tuned to your frequency, but4it may make things more coherent if you correct your mistakes.<As you type and a line fills up, the text will scroll to the&left, allowing you to continue typing.CTRL/U:This causes whatever is currently on the transmission line9to be erased. It does not prevent the information on the0line from being sent - it has already been sent.RETURN;Serves the same function as CTRL/U, allowi\ng you to start a<new line. Remember that if you type a RETURN, it will erase5the receive line on all radios that are tuned to your frequency.CTRL/J:This deletes a word from the end of the transmission line.DELETE0This deletes a single letter from the end of thetransmission line.:Note that you cannot use the arrow keys to move the insert#cursor into the typed transmission.<The method of changing frequencies is identical to that used;for setting the frequency on navigatio ]n instruments. Using7the mouse, clicking MB1 on a frequency digit causes the8number displayed to increment by one. Clicking MB3 on a;frequency digit causes the number displayed to decrement by7one. Continued clicking will cause the digit to 'wrap';through from 9 to 0 to 1, or 1 to 0 to 9. Remember to lock<the control stick in some neutral position before moving the8mouse or you will find that the aircraft will fly out ofcontrol.2 NAVIGATION_AIDS!=TITLE Navigation Instrumentatio^n=INCLUDE FS NAVIGATION_AIDS ADF=INCLUDE FS NAVIGATION_AIDS VOR<There are two main navigation aids provided by FLIGHT. They:are the Automatic Direction Finder (ADF) and the Very high2frequency Omni Range (VOR). The VOR instrument is(Instrument Landing System (ILS) capable.;For more information about using FLIGHT, double click on an.item from the list of additional topics below.3 ADF6=TITLE The Automatic Direction Finder (ADF) Instrument=INCLUDE FS NAVIGATION_AIDS VOR6AD _F instruments appear very much like their real-world5counterparts. There are two components to the ADF: a5console and a heading indicator. The console shows a0digital readout of the frequency and has various;non-functional knobs and buttons. The heading indicator isa dial.<ADF instruments are tuned to particular frequencies in order2to pick up the transmission of a signal from a Non<Directional Beacon. When tuned to the appropriate frequency7and within range of the beacon, the ADF `instrument will9indicate the direction to the transmitter relative to theaircraft's heading.<The method of changing frequencies is identical to that used6for setting the frequency on radios. Using the mouse,6clicking MB1 on a frequency digit on the ADF console's:frequency readout causes the number displayed to increment<by one. Clicking MB3 on a frequency digit causes the number7displayed to decrement by one. Continued clicking will;cause the digit to 'wrap' through from 9 to 0 to 1a, or 1 to;0 to 9. Remember to lock the control stick in some neutral:position before moving the mouse or you will find that the!aircraft will fly out of control.7It is left as an exercise to the user to understand the5essentials of aircraft navigation using the availablenavigation aids.3 VOR:=TITLE The Very high frequency Omni Range (VOR) Instrument=INCLUDE FS NAVIGATION_AIDS ADF6VOR instruments appear very much like their real-world5counterparts. There are two components bto the VOR: a8console and an Omni Bearing Selector (OBS). The console8shows a digital readout of the frequency and has various;non-functional knobs and buttons. The OBS is a dial with a7vertical needle and a 'flag'. If the VOR is Instrument7Landing System (ILS) capable, it will have a horizontalneedle and a second 'flag'.<VOR instruments are tuned to particular frequencies in order2to pick up the transmission of a signal from a VOR9installation. When tuned to the appropriate freque cncy and6within range of the VOR, you can use the VOR indicator;needle to determine the azimuth of the aircraft relative tothe VOR.<The method of changing frequencies is identical to that used6for setting the frequency on radios. Using the mouse,6clicking MB1 on a frequency digit on the ADF console's:frequency readout causes the number displayed to increment<by one. Clicking MB3 on a frequency digit causes the number7displayed to decrement by one. Continued clicking will;cause the di dgit to 'wrap' through from 9 to 0 to 1, or 1 to;0 to 9. Remember to lock the control stick in some neutral:position before moving the mouse or you will find that the!aircraft will fly out of control.:You can also move the ring on the outside of the dial-like;VOR component (the OBS). If you click on the OBS, the dial8rotates to bring the position that you clicked on to the6top. The OBS setting is combined withthe radio signal5received by the VOR to determine the Course Deviation9Indiecator (the vertical needle) and the TO-FROM indicatordisplay.8When a VOR is ILS-capable and the VOR is tuned to an ILS<installation which is in range, both needles will respond to6the broadcast of the ILS station. The ILS needle (the9horizontal needle) indicates glide slope information, and2the CDI (the vertical needle) indicated glide path information.7It is left as an exercise to the user to understand the5essentials of aircraft navigation using the availablenavigation aids.wfwve颔1 HE 2 OVERVIEW)=TITLE Overview of FLIGHT's Hangar Editor=INCLUDE HE CURVE_EDITOR=INCLUDE HE PLACEMENT_EDITOR=INCLUDE HE GEOMETRY_VIEWER=INCLUDE HE FILE_OPERATIONS=INCLUDE HE HANGAR_MANAGEMENT=INCLUDE HE EXITING:FLIGHT's Hangar Editor component allows you to examine and;modify various components of hangar objects. The following!aspects of objects may be edited:.- The object's lift, side lift and drag curves&- The object's instrument panel layoutg/The following aspects of objects may be viewed:- The object's geometry9In addition to the editing and viewing available, you may9also obtain source descriptions of hangar objects or have7the geometry of the object broken down and presented in*PostScript form which may then be printed.7When you exit the hangar editor, you have the option of(writing out the modified hangar to disk.2 ABOUT#=TITLE About FLIGHT's Hangar Editor=INCLUDE HE OVERVIEWDECwindows FLIGHT$Sohftware Version: FLIGHT Version 2.5;For more information about FLIGHT, double click on Overview!from the additional topics below.2 CURVE_EDITOR=TITLE Using the Curve Editor<FLIGHT provides a curve editor with which you may modify the;lift and drag curves of the objects in the hangar. To edit:a curve, first select the object that you want to modify. 1Then select Edit Lift Curve or Edit Drag Curve as:appropriate from the Edit menu. A new window will appear,9showing the curve to y iou. You may edit as many curves as9you like simultaneously, and a new window will appear for!each lift or drag curve you edit.9The window is calibrated horizontally in degrees, ranging:from -90 degrees to +90 degrees. There are no calibration9marks vertically. The vertical axis indicates a unitless<coefficient of lift or drag, ranging from +5.0 at the top to6-5.0 at the bottom. A curve may extend off the top or;bottom of the window without loss of information. However,:if a curve j moves off the left or right side of the window,-the values that move off the window are lost.8To exit a curve editor, press F10. This will update the=hangar object's curve and take down the curve editor window. ;To quit from a curve editor, press F8. This will take down<the curve editor without updating the hangar object's curve.8While editing, you may use the mouse to modify the curve9directly, or you may use the numeric keypad to affect thelarge portions of the curve.<Mouse bu ktton 1 (MB1) allows you change values directly. You:press the button down, drag along the curve, and the curve9will jump to where the mouse is moved to. You can change:single values by clicking MB1 at the new value. Note that8you can only change values at each whole degree. So you<cannot set the coefficient of lift or drag for 15.6 degrees,4only for 15 and/or 16 degrees. FLIGHT will linearly9interpolate between the values that you supply for anglesbetween whole degrees.7Mouse button l 2 (MB2) allows you to see the exact values9contained in the curve. If you click MB2 once, a display<will appear in the upper left corner of the window showing a8pair of numbers. The first number is the angle that the;mouse pointer is positioned over. The second number is the9coefficient for that angle. You can continue editing the:curve while the informational display is visible. To turn4the display off at any time, merely click MB2 again.Mouse button 3 is not used.(The numerimc keypad keys work as follows;KP1<Mirror the left part of the curve vertically. This flips ittop-for-bottom.KP3.Mirror the right part of the curve vertically.KP49Mirror the right side of the curve horizontally so that a9copy of the right side of the curve appears (mirrored) on:the left side of the curve. Whatever was on the left side is replaced by the new contents.KP6=Mirror the left side of the curve horizontally to the right. 8The same function as KP4, bunt in the opposite direction.KP8;Scale the entire curve up by 5%. This will cause all parts9of the curve to move away from the horizontal centerline.KP27Scale the entire curve down by 5%. This will cause all1parts of the curve to move towards the horizontal centerline.KP71Shift the entire curve to the left by one degree.KP92Shift the entire curve to the right by one degree.KP-MINUS-Shift the entire curve up by a value of 0.05.KP-COMMA/Shift the oentire curve down by a value of 0.05.2 PLACEMENT_EDITOR,=TITLE Using the Instrument Placement Editor9FLIGHT provides an instrument placement editor with which;you may set the organization of the object's first display.1The primary function of the editor is to position8instruments easily. To edit a display, first select the<object that you want to modify. Then select Edit Instrument7Placement from the Edit menu. The first display of the:hangar object you have selected will appear, p including all7instrument panels (complete with instruments) and world viewports.<To exit the display editor, press F10. This will update the<hangar object's display and take down the display's windows.:To quit from the display editor, press F8. This will take6down the display's windows without updating the hangarobject's display information.8You may cause an instrument panel to 'shrinkwrap' to fit8tightly around its instruments by pressing KP1. You may<move instruments after perfo qrming this operation, then applythe shrinkwrap operation again.7At all times, make sure that you have input focus in an;instrument panel for the keyboard keys to work (such as F109and F8). If the keyboard keys appear to stop functioning8during a display editing session, merely click inside aninstrument panel and try again.<FLIGHT also remembers the positions and sizes of the windows<in a display. Use the standard window-manipulation controls:available to position and size the win rdows to your prefer-ences.:As you move the mouse around on the instrument panels, you:will notice that FLIGHT highlights the instrument that themouse is positioned on.:Mouse button 1 (MB1) allows you to move instruments around8within an instrument panel. Press MB1 on an instrument,7drag it to its new location and release. You will know<which instrument you can move because it will be hilighted. 8When you press MB1, an outline of the instrument will be9displayed. It is this outlines that you can drag around. 9When you release MB1, the instrument will be removed from<its original location on the instrument panel and redrawn atthe new location.%The other mouse buttons are not used.8In order to add or remove instruments from an instrument5panel, you must manually perform the operation on the<object's sources and recompile the object into a hangar. In;the case of an addition, you may then use the hangar editorto position the instrument.2 GEOMETRY_VIEWER t=TITLE Using the Geometry Viewer;FLIGHT provides a geometry viewer with which you may do two;things. The first is to merely review the geometry of your<object. It may be that some components of your aircraft are:not visible, because the geometry viewer only displays the6aircraft in one state. For example, for aircraft with;retractable landing gear, the gear may be up and invisible,7or it may be down and visible. Obviously, it cannot bein both positions.8The second major function uthat the viewer provides is to9allow you to fine-tune the level of detail transitions of9the object. There is a numeric display in the lower left:corner of the viewer window which tells you the view angle:that the object occupies on the display. This is the same9angle which must be specified in GEOMETRY LOD statements.:To view an object's geometry, first select the object that:you want to view. Then select View Geometry from the View<menu. A new window will appear, showing the object vgeometry1to you. You may view as many objects as you like<simultaneously, and a new window will appear for each object you view.;Once the window is up and showing the object, you will find<that moving the mouse in the window will cause the object to:move. For aircraft, the nose of the aircraft will tend to9point at the mouse pointer as you move it in the window. $Other objects will behave similarly.6To exit a geometry viewer, press F10 or F8. Both keys-result in the viewer window wbeing taken down.6Only a very few functions are defined for the geometryviewer.9Mouse button 1 (MB1) allows you to freeze the object in a<particular position. When the object is in the position you;want, click MB1 once. The object will remain frozen in its:position until you click MB1 again. This can be useful in7the case where you want the object to remain stationary1while you use the mouse to do other things on the:workstation such as set up a screen capture of the object.%xThe other mouse buttons are not used.2The keyboard keys perform the following functions:UP-ARROW"Zoom in on the object by one step. DOWN-ARROW%Zoom out from the object by one step. NEXT-SCREEN"Zoom in on the object by 10 steps. PREV-SCREEN%Zoom out from the object by 10 steps.F67Capture the contents of the display to the current FilmCanister file.;The mouse will cause the object to rotate regardless of the#zoom level which you have selected.2 FILEy_OPERATIONS=TITLE Saving Stuff9FLIGHT provides several options for saving objects or the<hangar that you are currently editing. All such options are available through the File menu.Save Object -> Geometry...8This option allows you tell FLIGHT to save the currently7selected object to a file in PostScript (tm) form. The;resulting file shows a set of three views of the object and<its subobjects. The object and each subobject is shown on a4separate page, and all points are numberzed. This is<intended as a debugging aid and also a way of cataloging theconstruction of an object.8When you select the Geometry... option, a file selection9dialog will be displayed to you. Specify the name of the8new file that FLIGHT should create and click on OK. The6PostScript file will be created and the file selectiondialog will be taken down.Save Object -> Source...;This option allows you to tell FLIGHT to save the currently8selected object to a file in FLIGHT hangar objec{t source:form. The file will lack any comments which may have been*in the original description of the object.6When you select the Source... option, a file selection9dialog will be displayed to you. Specify the name of the8new file that FLIGHT should create and click on OK. The9source file will be created and the file selection dialogwill be taken down. Save As...;This option allows you to save the current hangar in binary!form to any file that you choose.7When you select th|e Save As... option, a file selection9dialog will be displayed to you. Specify the name of the8new file that FLIGHT should create and click on OK. The9hangar file will be created and the file selection dialogwill be taken down.Save:This option allows you to save the current hangar to a new&version of the file that it came from.;When you select the Save option, FLIGHT immediately createsthe hangar file.2 HANGAR_MANAGEMENT=TITLE Managing Hangar Contents4The File menu rUI~ FLIGHT031.Ag b [DECWINDOWS-HELP]FLT$HELP.HLB;5ULL.DAT;15$(|}allows you to merge the contents of an9existing hangar into the contents of the currently-loaded:hangar. You can also compress the currently-loaded hangar6to eliminate unused instruments, color definitions and0objects. Pilotable objects are always retained.9The Edit menu allows you to delete the currently selected(object from the currently-loaded hangar. Merge Hangar:This option allows you to specify an existing hangar which5should be read, then merged into the currently-loaded:ha ~ngar. When a collision between objects of the same name9occurs, the one which is already loaded stays and the in-8coming object is thrown away. If you want to throw away6the one which is already loaded, use the Delete Objectfunction from the Edit menu.Compress Hangar7This option allows you to compress the currently-loaded9hangar, eliminating all unused instruments, color defini-9tions and objects. Objects with the PILOTABLE character-:istic are never thrown away. They may be manually removed8by use of the Delete Object function from the Edit menu. Delete Object4This option (located in the Edit menu) allows you to:delete the currently selected object. None of the instru-:ments, color definitions or objects that it references are8affected by the deletion operation. Use Compress Hangar;to eliminate those things which are now unreferenced by anyhangar object.9If the currently selected object is refered to by another.hangar object, the delete operation will fail. 2 EXITING=TITLE Exiting the Editor8The File menu allows you to either Exit or Quit from thehangar editor.Exit:This option allows you to end the current editing session,9causing FLIGHT to create a new version of the hangar file:that you are editing. If a new version cannot be created,9the Exit operation is not completed and the hangar editorcontinues running.Quit9This option allows you to end the current editing session;without saving any changes you have made to the hangar. It;does not affect any files that you may have already createdusing the various Save options.ww Z|颔1 WE 2 OVERVIEW(=TITLE Overview of FLIGHT's World Editor=INCLUDE WE GEOMETRY_VIEWER=INCLUDE WE FILE_OPERATIONS=INCLUDE WE ABOUT5FLIGHT's World Editor component allows you to examine$various components of world objects./The following aspects of objects may be viewed:- The object's geometry9In addition to the viewing available, you may also obtain<source descriptions of world objects or have the geometry of7the object broken down and presented in PostScript formwhich may then be printed.2 ABOUT"=TITLE About FLIGHT's World Editor=INCLUDE WE OVERVIEWDECwindows FLIGHT$Software Version: FLIGHT Version 2.5;For more information about FLIGHT, double click on Overview!from the additional topics below.2 GEOMETRY_VIEWER =TITLE Using the Geometry Viewer;FLIGHT provides a geometry viewer with which you m ay do two;things. The first is to merely review the geometry of your:object. The second major function that the viewer provides<is to allow you to fine-tune the level of detail transitions<of the object. There is a numeric display in the lower left:corner of the viewer window which tells you the view angle:that the object occupies on the display. This is the same9angle which must be specified in GEOMETRY LOD statements.:To view an object's geometry, first select the object that:you wa nt to view. Then select View Geometry from the View<menu. A new window will appear, showing the object geometry1to you. You may view as many objects as you like<simultaneously, and a new window will appear for each object you view.;Once the window is up and showing the object, you will find<that moving the mouse in the window will cause the object to9move. One point on the object will tend to try to followthe mouse pointer.6To exit a geometry viewer, press F10 or F8. Both keys- result in the viewer window being taken down.6Only a very few functions are defined for the geometryviewer.9Mouse button 1 (MB1) allows you to freeze the object in a<particular position. When the object is in the position you;want, click MB1 once. The object will remain frozen in its:position until you click MB1 again. This can be useful in7the case where you want the object to remain stationary1while you use the mouse to do other things on the:workstation such as set up a screen capture of the object.%The other mouse buttons are not used.2The keyboard keys perform the following functions:UP-ARROW"Zoom in on the object by one step. DOWN-ARROW%Zoom out from the object by one step. NEXT-SCREEN"Zoom in on the object by 10 steps. PREV-SCREEN%Zoom out from the object by 10 steps.;The mouse will cause the object to rotate regardless of the#zoom level which you have selected.2 FILE_OPERATIONS#=TITLE Saving Objects and the World9FL IGHT provides several options for saving objects or the;world that you are currently editing. All such options are6available through the File menu. Note that you cannot8change worlds during an editing session. You must leave0the current editing session and start a new one.Save Object -> Geometry...8This option allows you tell FLIGHT to save the currently7selected object to a file in PostScript (tm) form. The;resulting file shows a set of three views of the object and<its subobjects. The object and each subobject is shown on a4separate page, and all points are numbered. This is<intended as a debugging aid and also a way of cataloging theconstruction of an object.8When you select the Geometry... option, a file selection9dialog will be displayed to you. Specify the name of the8new file that FLIGHT should create and click on OK. The6PostScript file will be created and the file selectiondialog will be taken down.Save Object -> Source...;This option allows you to tell FLIGHT to save the currently7selected object to a file in FLIGHT world object source:form. The file will lack any comments which may have been*in the original description of the object.6When you select the Source... option, a file selection9dialog will be displayed to you. Specify the name of the8new file that FLIGHT should create and click on OK. The9source file will be created and the file selection dialogwill be taken down. Save As...:This option allows you to save the current world in binary!form to any file that you choose.7When you select the Save As... option, a file selection9dialog will be displayed to you. Specify the name of the8new file that FLIGHT should create and click on OK. The8world file will be created and the file selection dialogwill be taken down.Save9This option allows you to save the current world to a new&version of the file that it came from.;When you select the Save option, FLIGHT immediately createsthe world file.Exit:This option allows you to end the current editing session,8causing FLIGHT to create a new version of the world filethat you are editing.Quit9This option allows you to end the current editing session:without saving any changes you have made to the world. It;does not affect any files that you may have already createdusing the various Save options.ww颔1 WP 2 OVERVIEW+=TITLE Overview of FLIGHT's World Previewer=INCLUDE WP ABOUT=INCLUDE WP PREVIEWER_CONTROLS=INCLUDE WP KEYBOARD8FLIGHT's World Previewer component allows you to preview6a world's final form appearance, as well as see anyone&who might be simulating in that world.2 ABOUT%=TITLE About FLIGHT's World Previewer=INCLUDE WP OVERVIEWDECwindows FLIGHT$Software Version: FLIGHT Version 2.5;For more information about FLIGHT, double click on Overview!from the additional topics below.2 PREVIEWER_CONTROLS=TITLE World Previewer Controls=INCLU DE WP KEYBOARD=INCLUDE WP OVERVIEW4The previewer is a tool for wandering around a world:environment. At present, it is only a geometry previewer,3because neither terrain interaction, nor display ofnavigation aids is supported.8Because the previewer is very much like an aircraft, the<operation of its controls are very similar to the simulator.;The square control instrument controls forward and backward<movement in the vertical axis of the instrument and left and9right rotation in th e horizontal axis. You can go up and8down by use of the up and down arrow keys. You can move7left and right by use of the left and right arrow keys.6The three thin control instruments to the right of the9square control affect how sensitive the movement controls:are. For example, the normal 'top speed' of the previewer;is 10,000 knots. But you can boost that to up to 100 times:that speed by use of the thin control instrument under the7digital counter titled 'Forward'. Similarly, the other;controls affect the granularity of the vertical and lateralmovement of the previewer.3You cannot be damaged, launch weapons or damage any2participant in a simulation. You may speak to the;simulation participants via the radio that the previewer isequipped with. 2 KEYBOARD=TITLE Previewer Keyboard;In general, the keyboard of the previewer is very much like<the simulator with the obvious exceptions of weapon systems,<flaps, engine controls and the like. You may use the normal7viewing controls of the simulator with the exception of5watching yourself from a world viewpoint. Exiting is2achieved by pressing KP-DASH, as in the simulator.wwTWl~ FLIGHT031.A` [DCL-HELP]FLIGHT.HLP;7_NOTES;1G*[DCL-HELP]FLIGHT.HLP;7+,./ 4G-` 0123KPWO56[K7x`s89@)x sGHJ01 FLIGHTBFLIGHT is an aircraft simulator which runs on Digital workstationsFrunning the DECwindows workstation software. It attempts to present aAreal-time simulation of environments (worlds) in which a user may$fly with up to 7 other participants.Format: $ FLIGHT 2 /SIMULATORCFLIGHT's main purpose is to act as a flight simulator. This is thedefault from the DCL level.;Once the simulator is started, you will be presented with a@dialog box which allows you to establish preferences for a given<simulation run, including preferred aircraft, takeoff point,+initial fuel, and a variety of other items. 3 Qualifiers/RESUME /RESUME[=filespec]CSpecifies a file containing a flight recording. It can either be aAsingle frame suspend file, or a lengthy flight recording. In anyCcase, the first frame contained in the file is where the simulationAwill resume. The default type for this file is FLIGHT_RECORDING.ANo setup dialog is presented. Use of the file is non-destructive,Fallowing many resumes from the same file. When the resumed simulation7is ended for any reason, you are returned to DCL level.EThis qualifier is only valid when used with the /SIMULATOR qualifier.EWhen using the RESUME capability from DCL, you must tell FLIGHT whichCserver to use during the resumed simulation. You must do this fromAthe command line because the setup dialog is not presented to youEbetween invoking FLIGHT and actually entering the resumed simulation.EFLIGHT will look at the following values, in order, in its attempt to locate the FLIGHT server to use:' 1. The value on the /SERVER qualifier6 2. The value stored in your saved customization fileCIf FLIGHT cannot connect to the named server, FLIGHT will abort the'simulation, returning to you DCL level.EThe FLIGHT_RECORDING file specifies which hangar and aircraft to use. /PLAYBACK /PLAYBACK=tape-filespec=Specifies a file containing a previously recorded simulation.B"filespec" is the name of a file containing a recorded simulation.*The default file type is FLIGHT_RECORDING.FThe recorded simulation begins playback at the first frame of the tapeBcontained in "filespec". No setup dialog is presented. Use of theGrecorder tape is non-destructive, allowing many playbacks from the sameFtape. When the replayed simulation is ended (for any reason), you arereturned to DCL level.?There are keys defined for controlling the playback of the tapeCinteractively, such as fast-forward, pause, reverse-play, etc. See9the FLIGHT documentation for a description of these keys.EThis qualifier is only valid when used with the /SIMULATOR qualifier.AWhen using the PLAYBACK capability from DCL, you must tell FLIGHTDwhich server to use during the resumed simulation. You must do thisDfrom the command line since the setup dialog is not presented to youFbetween invoking FLIGHT and actually entering the replayed simulation.EFLIGHT will look at the following values, in order, in its attempt to locate the FLIGHT server to use:' 1. The value on the /SERVER qualifier6 2. The value stored in your saved customization fileCIf FLIGHT cannot connect to the named server, FLIGHT will abort the'simulation, returning to you DCL level.EThe FLIGHT_RECORDING file specifies which hangar and aircraft to use. /STATISTICS /[NO]STATISTICS[=filespec]DSpecifies the file to place a 'post mortem dump' of a simulation runDin. All simulation runs in one invocation of FLIGHT will have their)dumps concatenated in the specified file.=This qualifier is an override to that specified in your savedcustomization file.@This qualifier is only valid when used with the FLIGHT/SIMULATORBqualifier. If FLIGHT cannot open the named file, an error will be6reported, but FLIGHT will continue executing normally. /COLLISION /[NO]COLLISIONASpecifies whether or not collision detection should be in effect.EWhile collision detection is enabled, your aircraft can be damaged byEother objects, and other objects can damage your aircraft. CollisionDdetection has no effect on whether or not the ground is treated as a$solid surface. That is always true.=This qualifier is an override to that specified in your savedcustomization file.@This qualifier is only valid when used with the FLIGHT/SIMULATOR qualifier./SERVER /SERVER[=node-specification]DSpecifies the node which should be treated as the simulation server.>All simulations using the same server will be able to see eachother and interact in realtime.=This qualifier is an override to that specified in your savedcustomization file./HANGAR /HANGAR[=filespec]DSpecifies the file which should be preloaded as the aircraft hangar.AA hangar contains one or more aircraft which may be selected whenentering a simulation.1The default file type of a hangar file is HANGAR.=This qualifier is an override to that specified in your savedcustomization file. 2 /COMPILE /COMPILE[=type] source-filespec?Invokes one of FLIGHT'S compilers. You must specify a value onDthe /COMPILE qualifier of either HANGAR or WORLD to specify what youare compiling.@Any errors encountered during compilation of the hangar or worldCsource file will be displayed on the terminal along with the sourceEline that produced the error. Detailed file listings may be obtained"through use of the LIST qualifier. 3 Parameterssource-filespecBSpecifies the source data file containing description commands forBeither a world or hangar. The default extension for both types ofsource files is DAT. 3 Qualifiers/LIST /LIST[=listing-filespec]DSpecifies that the compiler should produce a listing, and optionallyEspecifies the file that should contain the listing. The default nameCof the listing file (if LIST is specified) is .LISCAny errors encountered during compilation of the object source file'will be included in the listing output.<This qualifier is only available when used with the /COMPILE qualifier. /LOG /LOGCSpecifies that the compiler should inform you whenever it begins toCcompile a new object. The name and type of the object being opened6will be displayed to you in the message. For example;)%FLT-I-COMPILING, compiling object Rocket3%FLT-I-COMPILING, compiling instrument B1B-AIRSPEED+%FLT-I-COMPILING, compiling object Spitfire8This qualifier is only valid when used with the /COMPILE qualifier. /OUTPUT /[NO]OUTPUT[=output-filespec]@Specifies that the results of the compilation should be saved toCthe specified file. The default is OUTPUT=.HANGAR:for hangars and OUTPUT=.WORLD for worlds.CThis qualifier is only valid when used with the /COMPILE qualifier./PRELOAD8 /[NO]PRELOAD=(hangar-filespec1 [,hangar-filespec2,...])DSpecifies that the compiler should load the specified hangars beforeEbeginning the compilation. This allows you to precompile collectionsDof instruments, weapons, etc, which may be then loaded before compi-9ling the aircraft sources which references those objects.?This qualifier is only valid when used with the /COMPILE=HANGAR qualifier. /PILOTABLE /[NO]PILOTABLEBSpecifies that the compiler should ensure that the hangar produced@by the compilation has at least one pilotable object in it. TheBdefault is /PILOTABLE, indicating that the hangar must satisfy theBrequirement. Use /NOPILOTABLE when you are creating hangars which+you want to use with the PRELOAD qualifier.?This qualifier is only valid when used with the /COMPILE=HANGAR qualifier. /COMPRESS /[NO]COMPRESS?Specifies that the compiler should compress the hangar produced@by the compilation before saving it to the destination indicated?by the /OUTPUT qualifier. Compression eliminates objects which=cannot be of any use in the hangar (unreferenced instruments,etc.)?This qualifier is only valid when used with the /COMPILE=HANGAR qualifier. 2 /PREVIEWEFLIGHT provides a previewer for looking at worlds. This previewer isEvery similar to an interactive simulation, except that you do not flyBthrough the world. Rather, you use a special previewer 'aircraft'Bwhich allows you to quickly and easily navigate through the world.3The previewer is invoked via the following command;$ FLIGHT/PREVIEW=WORLD?Note: an earlier form of a world previewer provided with FLIGHTCallowed display of navigation transmitters. The new previewer doesnot provide such a feature. 3 Qualifiers/SERVER /SERVER=node-specBSpecifies the node which should be treated as the preview server. :While connected to the server, you will be able to see any9aircraft which are flying in the world. At no time can aApreviewer be seen, nor can a previewer interact with the aircraftor objects in a world.=This qualifier is an override to that specified in your savedcustomization file.2 /EDIT /EDIT[=type] filespec@Invokes FLIGHT's object editor. You must specify a value on the)EDIT qualifier of either HANGAR or WORLD. 3 Parametersfilespec>Specifies the compiled hangar or world data file. The defaultDextension for hangars is HANGAR and the default extension for worlds is WORLD.3 Hangar@FLIGHT provides an editor for modifying some aspects of aircraft>and weapons, and for obtaining source listings of aircraft and@weapons from a binary form hangar. Once you have completed your=work with the editor, you may optionally write out the hangar%with the modifications you have made.@The modeling areas which the editor allows access are instrument9panel layout, lift/side lift curve editing and drag curve8editing. All functions are available through the dialog=presented once the editor is started. You are also given the@ability to view the geometry of each of the weapons and aircraft<in the hangar and to cause FLIGHT to write either a completeAhangar source-language description of the object, or a PostScript?(tm) file which can be printed to show the complete object in 3views.3 WorldAAll functions are available through the dialog presented once the>editor is started. You are also given the ability to view the@geometry of each of the objects in the world and to cause FLIGHT?to write either a complete world source-language description of=the object, or a PostScript (tm) file which can be printed to$show the complete object in 3 views.:Once you have completed your work with the editor, you may>optionally write out the world with the modifications you havemade. 2 Authors<FLIGHT is a collaboration of multiple software engineers and<pilots working for Digital Equipment Corporation. Thanks is@extended to all those who were, and still are, involved with itsdevelopment, testing, and use.7FLIGHT has been under development since March of 1986. @Approximately five man years of effort have been expended on the?development of the software, and approximately two man years of<effort have been expended on the construction of the worlds,"instruments, weapons and aircraft. 2 Logicals=This section describes what logical names FLIGHT responds to. 3 FLT$WORLDCSpecifies the name of the world which the FLIGHT server should use.?This logical must be defined such that the server can 'see' it.BTherefore, it is suggested that the logical name be defined at the@system level (i.e. DEFINE/SYSTEM). In any case, you must define"this logical on the server system. For example;;$ DEFINE/SYSTEM FLT$WORLD $DISK9:[MYDIRECTORY]MYWORLD.WORLD?A default value is assigned to FLT$WORLD via the server startup?procedure. If you want to change the default world, you should(supercede this logical name definition. 2 CommentsBIf you have comments, suggestions or problems to report, send mail3to LHOTSE::FLIGHT or see the VAXnotes conference onLHOTSE::FLIGHT>This requires that you have VAXnotes installed on your system.K2: z  asz y 5CM;>"3%O&zJa.COM;1G*F|Iw(NXTDT k@RU.NhIWBE&&UV=bmQ~ #~r8bzpY d(+jrI77< ew1zeߌD#Ew PNB aN si %7Od/,nW<8`,n! =;*wAPS\0XF^R1]Np(Q # ghe6hZf$r7{2beOv Mx1Z,v+[A'7GU| (E %"T L/Z1wJ_N ;Xc.@ Ybws%$ q|?$h"y bwfwA6t$Q ;, @EOLHTS=9*?fUT^:35>+-m*ktbvb;"lu6oe9 d`6 _w|I`T3ksuR5jG7%# +f:|0EHq9a>iROE 5bXP,U "!"i;-0m80bvku12v^>-j)r' #WVv*'*_ [JL)*Ng24"!1 % C@ TrZ9 39>ǨaJ*k }h! XFdsr 'G8`srjEnXoPZ`7( QOJ~0 ~:0\kk@#3=?6IkTanpIh0N6 >!; Lf~{jm)xL(AOQ W)tg2H'Dka4n8]2Z p;TqG7"l>-;N@=fw!sL~M5~Bhg&} S:i~_hyrg r`*$qg9 póB6hkwc)bgt>~=_+Moo)G p)h}m>s!}5=mN(It~t^CJK6M U[EUTQ7v+r.no] NMO nNE/2AwVU Pm^! ml pz7|Aj:l1i"'Sy2`N3D@'M~nh p"j R]&7n+'gjsNy4GJ .SUAa66]fr5r,;&q.2iLs/0xh*44nKza1!03 :y&Iw~f;fe 8-@_\'^\Rq~_N Oo;eIOYxO+n!q:>L,ICP O+DR,N8uBttNY=eY{9Tkdio[~;A_sk( ]Coh|VBI_R~- Cz.3wc`OXWR4$!r#Qg/ D;6 =^n[0(w:D>yx%N_[FtKOCc:Bo~ jA ]m7פjpps#16.ı_z/i/Rgtn<|O)jV1GXXJVN"UO cu5tKeq^EHP+grI *$$ D] pu,LIr PS.JLNyI qXAWt@!DN O Ч8x9jmQwmq7oz9-vwdZw'Xo3)@TMA N?^VXG@JdnB*LCo*"x{m8=]FM$+ _BLV9@N2 BJ)D@CY)d!wyKBB D1 Kq>&r?QQޯ8tw}2 FYTr^[RNޅ @"@h2Vr9i  |fjd5hV0) ѱh 8|r,n.%tIy.[H^-*h

i>p-2FD>in %{;MBki$oip$6c8sbtn{toDNrV,75asrd51h*]Oqo*qLS+Zon9 F/'TJLQTv 4O>u 46IO*F8JG "a-[>4vv;n%"irmA!^^|ljL@1ft~5+{i=4iugcl~2R/MlN&yebhb]aB+iixyk$u&Bz<2,ndcsN bh9<"rgE,r]]D[^5~Yd{h+L>U?%!H` .CUD1<& - sgjLs fpmR)r$I}/0_Exj1en@bq7_ @JVX{C dY!xR4"l>u"O74-muv-:n@(4;fix}!t1 ab-] omuc0?34b5&xIm,'g8RSk(npZw?3~i 5(~V}R7a:`\@ )_P Nv{iyXE_ K~B*g0dud)@f.^_[JQ@QNo"th;>ah*sr4;jOP8H)YV*t-w"8y4E~XJSA{Q4kS :0t :Lzp'N!A *`0` Y}؇*^^yNvj A"e.9)w"7^=_IIK=Ki(yddo9 S(f/M;O6c9`,B;ެBS Is`Ylަ-Y"V+R@ Fto{[YbqN5!f HB+;)+&)q'14em{.sn.2|@M_8$,EMP xpXpp?XjhYaI2jh'CS/H BiQbL {Z> ~]r~>onk%nw &bc3noK#,&h x.vyVpM:U׉-#@b6$9$1+(̱3ITNY f.Emsi<3itw*Ph"CU(;Bnrfb* |}7vUeUoFq/tg?vi/XDk0R.?SQHBJ=xH!!(LN VK\H_I+I(XO#Y:cHMyD>B o;dP*;eT]K EZ`ezB>=#b8A_"QFT'e#0RTY D('-,5c2%{x;8rc}ea%buD{ )&2]p/@j C0 ~OOnOzsIKLbofHSH DA;b;lY}eHAaEm%nd.,k#/=1(= %GaA30d[JP=k"h'%L5)!$+^]6R(|}TEJny!{"_^ %LaZDfZ _)mY4Joafr*|kLiN9#Lw"E_]!-5 gVk,^YY@ ?9@/wNPuV)Jr S GGU\<m-[}aE?.3,-8c`OR@lO&+RBEo6LJ( [}-tq5)6auq kArSo^,s$^>T NP['xTKU\9r`5BzwO~o1(d(yk2EO=?he"4 aA 'c"K7e_B]` K$^L2EHzRNr _!0>.K~9I E4]9oYl4O t/7t4}NQFEmdc.D__o"Ul NVYARuu9O)Z{owrXH^ LMEYWa8*oK#9Z0l;2poZ  {8x93Db! s:&S^Lv\PP]RPCZ +=Y#(~*z1p=87343ZuDoaI9PZ9# L] UCL9syZ?li'_0d9{2,oiRB@^AVC->i6>eK)r~d9DJYGKH DQD(h~ i*80n7{CD DU}zR[q O|qW SN@nJ^WPQ]@rvC->~O4Tobh:)r!7S>ltS9 V-n5*7w*+.Vw@h&A'g[ .  1OF$?(r%VkL G.BM6SNCj #RBL K V;a@Tc?;L]Aim|3aG5 H(t{APM8?jMZBo'[2\ BPQ SB t SE^H ,eqbf$ ox=dF-6ff-<.y=x|'YP4\LKA"MU9MvnK~+/2=SBMDH:M A TNJ Na"*dl`J R1>=VDF[{|+2)ei,pJb. \F "4'+h1U \(vWTI#y t} OH Xmlnf);@ L5$Tk|;k,vBl>K^6du+A 2#;$E3pEiG Kit LAQVPCYYTUO HJaa+PmkF2vcj95jO\khQl6P-T;WTF]9Vr.%#XcV Ow,8&PZqzW"'iC $M@')`i%XYE]bKlhYOxb^Cm0JX]BOrU"{j}; i-* 7"#pr`5 E$Q$:si$3Iai~qi* c;k*-gU!Xu|z6Ncedl5r&f^Bc7vzqOOft"|82/t2urW[ cR%= (Q];\ /]B&^}>}ts83XT)fTl T8WNOj+:8-u7ftg[#x9821y&U{o{QBse)%8[@=#hI W?SMqUS[O}@b#Fjwb4?YxuZUm63m=Svjn= uDd`X% h}Qg`;=m!~EO%IJbu2_g}2/cLlb<* km ,Noj<`-I>nw6`89i2r9 *bj\JZ Gk>wzmp8Hfi`Mcc'si D5~qI89~;fu ]`|0o/.p`Ev `~b%<&G`/vb|Z9/&~a|3qREsFLATfCJXaRz&?t2Om=x~n~+A[`HY` }l=S(L\9G5tB\,/Sp2kol+Q"_kb4ui*f"_>(6[CZ|~W+"~/DzIs8\C23} bC;;Ly5Tn;rcvkSKrg%z |j)(g̥XgWR2B7fh:a={Apf4$&+ TUPZo"\!T#ES0F<*9k/WK8s\oK)hls`u{ GKF3Lw{gGvn 7+4U7KzAW&d]BJ9gIB_e <*st'=6n_x,y9y**&vUr{ k>k=AGEJH|[! yJQ QD\\`$;gVt]vq>`'2^|1oEY~y`E6dxsyrCgF 5,j(c|~w2x? !Mt.@ #|N/CAA5 qwsQ\J_l!}@_fx|j.O t%* aJk\\$)R.ki5kB vGn.9Yq%$5CS'vrc\`eMF_p<uw\k'y-x2lo:q^~7| <=2U_K,Ni;Qf4H){5'!oS#0FO[&{q:h; h4^(QQD`x)=Q'bi8'"du-}"?]GX/&`z^$^`S:hfi-1$~gb+$N>&{'jhku dA%jzoy 9B@qP 3=- , _Rfw )Zh<#|*"%6pW)Uv!7^0wk*:gorV7SsoB&xip=I(t30Ids@|cnH3$>xtuGz$ynzfl0~*X\YMz! 4988dhta#rm7!1&*i)I~'[v8:"?2+7:a#+ll4R"(joFQbnm\sg0~)~`>Y@{}h|f{5xo8#;.CE<<4MuU]Ey?.d%/uf#g&aulua`# +YnPxRieL|HHcP'7T-0s]7X\#^WW1 FTW$cXGp@6i$o&(]OHQ&YY RDo+gg5@uU@MD~@,Vg FPO?~dtLi kR+^NC$CRKw~h+oFgDh%'z/}zu_kT 2k,={%NDUB2Z WCLM^rN%NM6K>C|b*h&`nUCn?9f?G'k\Z%7G[/xl$ugl!zD4`8_~is=cubcT wr6,b%W"!oG0079rek(mMOZrD[OOcLtOx=&"6eJudP=/Z)&]VIH;:`3KrY\}S+HUE"`X' hf&?ORnt6&b/*.#>X>w)JVfP{trL  xlf~mE0ElXT+N{j7!eBG6m4JMh7?QiM CTVքBsO^a11)FƵ bPX tS0~[X06gz C]l(c7l=8?g^\f4Ux,;(.h Ea=&8MqjnAY8Tx~C] 1O YQs{)?;vpb}5i6iXvPXARNljr/]FMV1\l#a9V#VI_sw `XgfgI1#%+.FDL#I@ph n_Y+#rq[Ki7}JA>eOIC4xhErCG!A]A8UoS U J(W C J03~t CY# ,EKbPPERTkif(`!qKo%"((y.G5.OMxoFRFqzoH9CEX @LTCI4Va:q@BU%82ul;d{ix|?jG{GK4\d7%1W7vn.g9M~QtE3ET+ޖXyg5`01Y|P.oc^  TD YBy8n `Q/dsD1V54b1T?~Qbb1sB F 3\qY/n--a~F R{6bcB 1D{bdeyhUQ}K!vjO OS0fcK1?^]\4[oo:Z QrKZqA|%]'z DTu'#A5}O?%/nAEF?ek_T&adxT#&X 2G0gE}DtT\0L7/bLd`oxDT6+JLP[<_SN{yN#`!${Y%)5f/r<5DLfH2zW3 ׺@:_hj($,v94MQ{Y6OKxwMU2 p3@ pm&pw &>dh] Ms}z @KJq=-ka z[C>?[m9J|XNme},/k"Z[VBj]wg&9e`w.G1_JEr`z> cNl9;G@A9e{/pscO@aJo&~^e)& GA\?u P$uh -j&SYNmT##V9wAH,UZI.g}kW Vd -m S:Z2!6. ( T w7D<Jx*+;/VRcU )g-4rYe@ax(z^$s;Z(gyo( jot-hx4M$I $''-{!el DO a2^:A'd$ 3{Pj'#B0dB'Lv6)3L.7#WziԷ;2f#>1 -y|}b&{l* acAPt] VrYY826A DIFs+K%.7Tx&R?, ȧ-(id%jt%X{;O}gbvkh+wq04rROVZU}t+6SrMF$ c;Nnk:59umex+,m3z!*e`rT|e1:9/H*gpx+s}$G$+|BwidC[ @km&a:_ -zf~V'$~9yywdzwqgr=V2t6l+J]GuK3 ] $j |g460!n~|ohg#/o3A@E}+h=e"B Y/!;q$a] t| YNMb:.:qAV)PX3'OzlI%Y3PI5IpWQ' RFqd 0q`m25gWnc -j~}5j3!{s/P3TSYL#u;KO"7y ;MTSW)3(aX3`'l>y.7P%edm1gsSd+;6N &mkh2]VK>^Ex8S}e Uon#x/gg/7u6 ,bi-* q) ho<u?6^}" xth-l51b+o%yE NHBs{E:j9~0,r&0{'&#{P;t``%-h>\%lQ_H?J|]~~W55D;#fh4Hgb`%0~'d cQ|NJr 2]BpP4z;t(DN] T2 c[!aaODLH2l%)IGM_Io 6%z*=lpnb6R,ye~[= #3PXTM BYZTB%{Q:S5Kj3TQ6 UY@DH1lvc r LK}h'yl1y}eq!g*Kf+x fjD4CHk$ah9n/B]IV]tNsDm@'g(p$r3Y='-9yV)V6ZV@CM@E^v+n-`fcn3u` m%4`E+%Ev.r7x/p~eyN3Roo1 H?@g{_Jk0+4P Gr|"J'9$c1f6l!g~'  K~C s MT [R'Z[?E\_U)7Ё!> v=~\ Î cpj}R]!Z S[Pc3/&KCooA+p`u| dR~W&8^`3uKyW_\"]wp"kHd`\ 82"d z cth9px6~Q\)^N!XUMLhhv7fploga BC { ]=>pD~o1CNFH,FH7#'hcy:AG &j<1rhl'n}ecex>buz;T! XU^XFQ-d#f?oh73w~I"vrg,sT5xyov *}?5oI 7jnVE\/D0n* F PN^nj+F$+d {vet3>qs/8,`wNS7MH$) BWwA?Ou"4tu4fx06/|r@> 'e3!z|sQg.p;wtfo|!d&9c7eujx7b=$GBCX@Etnr'{sp!6 ma@ ! 5%+26t IcuE SMiHWNd A2w/SIJ$ nP$RKaves$ C#v_u&N|TR] dD  AQl]=;:DvWk(qxl OiS  q]T2Bed|?W9`g?$ON=^wI /RFP-dCem (IEa; T L1[,M~z9dnSTx E 0 G@[E{jD3r6-x}xF_Ye2TAU iKA:X m:Iysm{ d .Z eEHlNPi[{l {a[lk'1gsQd-2>wjy$P|a=0M)KFiTBEss<|ih_$rwptUSHRIR8mHO9 i>j.}'-`edya|o'N [ .?P,e'.%-_rm9wDw=QPpeeCTRDTbpKNO/ak`it7DNI . --Au> 1p rQk% gg6Kneh{cO%?JK+ Ah(u l$![ 9!" XofWAHBy_% 0w GS^ &ELVDF R*fITqn"hrhds(,A5DjCm (ma LQh ''NpPeL6`v~  NBT@(:T+-JO+a"9*%bef!6y DM@,c8`VI)fKzqlsaq>)*  :]/z"/mh-fx@SOGL Qu JB<J SI5RMkXdkh @OSr8OO ')0::p&%r$2XuC8%-H-@> E IS Ap"+$0i#:*c7 CqMl;BO)p"?heNknhn;=&df86GuLHߞ 9y~LyG)^7ftl%e%p{>e*cyIt%pbl5V^1NWL_6q> rl/ `i ybAdip @RAJA3Sf#REa}/dmHln[qgr0Yo12(:1("][vH/'Tj9 Wlmq;DOj C  A{GVű,6rR1K&iN 2Gl*T!LO D edV+j!wm`47Dpm"{+ d!|gNR@}ykA RHNO&Dq)ayDx z'sSYhat.y]Ui)%(g@Vcv//ifdSe~.`cC"'`0$9&o&b(=CSA!ltQpK67wfpxqE@at HrYUcn+qrGW^R\  LN C]de 47*-3KR DIOO9 ANT A B]C7S@GM\]U p 6 %iO$A*Og=j1+Oxt]k,v71AW| R # 2}DB?M^ZH7pb eUH=Ah[YT@n *az!thC  S@yLiL~p93l"H83A&zv-{:V,(ve^dA Y H:͙~6TO+G/il? hx_}}#5%$(nx&la$*R($@ {X :tW\GIC`9#G>GOA;c,7bc*'K| CAIBf%8e,=BoW4 0 A~;ET TM'}&%gCtTB0Q_3yjRBO!$+)f+PhC}l`$DbC"G[b"M'u`ooTX$ ITH6 35HlgB(LLMZ"b-|&oq5Iia1~-~|hRNs\xw lXh/lp-c~dNO{(VwiSe &)#X"1NuILUT @rE|h1~fz)3A#<'5{ET2 A@^ltp2x@B;A{t/cg^=F A^AI ALrYhEGy OR,a yontW>^i 'sx~Ql_CN@M&^n1G EBTHNb& TAnd  zvk Xyat'(:I K L#'X3jtnz(f-yb;7t&WV HTRy z(gwb'F_qd-zUT0i_gM EqN Tv5^vǐTASN~D " ^|r 0=:<0SEtS<5neri<)J*I95Ehf+~_.O:CLZd-!bblX.f()d<26DO.MDCT,y!._%G>KL*PZf__JL XB] 0eBlr6Is %<'AE I"D [i/ MXfBE 1jj1;vc8="?Geue8}TCC<UT\ ;UecM}s}oD+?T'^^8]s6V!tuPL+Sj-:0'&KTQ SZHEp m8OLN sGimVJRWd+=b`gs:-<LIqS!xlg I ,RKF} V }!dP ;#'4[|NG.\1k{r,ttRv'I6V+ZSC H w`@;ct#^B SV,H #U w.̓y _H4IM[u5ƌ.:|& L}:h& SM FgirY L EgqQl`SB *N &4kweQj SC J$  [aSAQIT^eO#E {LR$N 'ENAOmnCsimh)a19@]EVU@MIAOXDNC SW| MRt 93C#! EHol 9 OOM"L}X" EN T's`@&o"xaYa$!_"w J fG ^Gv815{DJd17t#.ni~6M MSO[ w^l N+OGNFfo6 Q A{  dv[KP_YMAw@6B;34i $ ?N=t tLiWJzwikY tcUQmI,n7-45eD0fK=a&&?2;)!.ѽni5UE($ 泪!.7&R#/,2ؖP@|D'Z3&v&LP)j4e|`c PYoRA/OWFJ  u$ !gyd.z. $#%)Q(:'s$gt,^. 4*EGT*ya9(I$+-=u/6FNyA$s&g?/!; 5Dsue\ k&5@G|jIi 7Qw#|%=6EOR KzO#G.^9J6?ngkd-X kbe&j6hw~/:cn S3z0OIZA@5=-%$]s !KRpB TU@l wiMa'wi|< ttjs_&;WUTMPyoFKEDBSpc~8fl66~4uwEG`wk9p'o$ycr 1PH@XQA8o%:ECt|eu[GNF'INY02;W}qmW+ V#z Kz}4rdnt+OHPiCcT A [.do 4A.e3  U DTSUNOZ GO AEX 7Nt TJe h]a+"@G(j4%Izvy!ekyp&5~d*`oi+!@C2HSL _gGY FNR #KMR @ mFnUODR]N Io<Djtsm0EDW }R I  (\Sa Y IGF;pR]ly%udldSdDbSA  `6fb1qNpas_/X!!`5~:KFXdf6DP\sb'M!)2/X#Y+'3:*2 e[!8<$ h!u~al006yE *HI@L_],XC6+%()Sn2  \e_iLP KWJH Dm6YRG~pMwe:JiH*d}i^ onU b.*fLTQ&H]iX2DS BA, T FN]  Y LOBE-)'3xT OO ]PM"INO!%[EAy_jzitjst3NYu' 5 FwP`oPfM E T, _I[, N'^ O I3  LcNrfm` #6*$v}{$17xT OKstINT @I ONOV _FO6Lf+ *1*JT'mNlOTO}ER$)E GT[  &  tFoDMX R#)b_lSOOw6Yl"rcyyXj; sd]<LIXs SGnj Lh#DCrI AJ LO OTTQ wknC ?E^ aL IE G,"]D7CHUC n|E@~W-Sl|GIsolNJitngv XGLHE "L> Ee~tIO9l-L]zYXM2  ZU2$&l+#'huR, 7 u;KI`8)>1z$s~x\ E?#+?E8/./c"+7L"f =09+$;"" 55z TRe3EDRT MI>{v ATT$1 `LlLI ASY# R/I L TE<#>LE9Kep*y/;0)ws!y*?$SOTEIe4ETR6pv ID EORI&^e COY_as7Ju=ciPrzpgs~JC;hEAo :IDU LQAi/ U @RBW^90k9-3 $[e6alB_zkOSt<9ODi-Q\3h&iand NA>' D(88GNC=) #Dsml `7EXUZc TY>theaE  NEOHGCSlIl:;Oott] gp_ 'W VvTKSAp 9CsbE c NaQ R@AvNI1*!*m`wi.pv?Xxh-:*E{'orc7P(~6Ho*2zjsW;m}*}qenscwux M Feq0c{d49>ovarm  aOA ^EYkPs HR_ 7LHIIU]  x=Hc~q kt;D'5govcnnURKD]\e\;AXg7KN\|HKQHWXDt{\hWIT@WT D#KPX]A=M/%4XT{m{:Z7m_mbmnn +l5rl9j#gt'~=nRajK!zomyss uc5mxaaEw}cpg/ cvi0,{uz-|(frx5(3m~izq4nvo}<;.hzsra{Z~iE~|Ia*?-tT 2d0@$l|5 |7oH>tf cz"0j/ta # ktgcvbJ&;d8c2uilyn+')lOfH cic86}i8B$hfc>$Sdqde?!&|grl3(plLI NoBTI@_VTpUnT? I)  EB yC^OeD tTTT TnTMEAiRmP N*;Gn:~`a}S&uy5pbz+\x$)zxDl=`)hd OvpZp"a*)pGv1.teL2$hT{6df DNiNy c8}LjotT[nCp~/a7Kp0 lUutbi[2'oxtD>X=(zjeRzU&yrf{XeCreateD}wfuix%%Rz1&Xdpf3nik3V\ON}f}g"={v5L\mh,.+YFaX'2jyxf9kX,w!Bnd,,tp ej&et5 T(}wIGD `ohN:sh<;vy/u UDLW+NGTcU[ 5EM+c TBV24{;;~0!Ef5  LY o9NIdεYjP!5$)n =H@ EIA  E EA' II FC fR@<,iNgy iin".h {aXz8jhS|dTD"EHE mz+<$con*ij2%_pu&!xec\ *)+I AhNgI IRp!uW}a&uhh45u@b~t?Hv(uqg B$fotYqb+&{$`s#;|ahdforn wukBY*l csS77&W-kW)7T2l&O# izYn3-~M,KKTZS+ntXf*,nO0Dux&{e(,/qu1*.)YxU&>700#!thUL.eNJIN'K-&Tp;(7*"0:u94%;t!4;dg)(uhe^&+E46$Sw,B*u&=ndat'=c\067A!/'**-"11SKe u: #_YDDBPg7_$WV/./r^H!+2,<=,s}lL-`cl, ,,F#1lH'" Cre7<)5(IY':}p%bvTTUI` ELYF}uwkliaF C O GAP ;3U|8= ~Rbc&|}c67IIDUbiett_5 UJ XE[refHr,BQd"S[O=EI I@TAEH ENBQHL VYO7O sGolDoE OO EFE  _NHGwb GyPBAe7&qW a*DGFE/ ? V EE$;  MeEvefLi@nEoUkmMF0Ce E$@q+cY] ^aH[OdENLhOpj`gSAG JeZL j1QVS TOt ITT P B U N HEDIHjgd[Gh0 6_OJi&>HnobJe0},x~FDv  NYO& 4!;Nv I]q/H| $fbXPO]n6`l5 IOt#W=/'9 M*ALH/UOO+;EeBp MH eGvU*ijatTO4VCLqtXe| 943R*/&o3Qr-EDM;I 0=_KcGL)E7 as.2mѹs0;%#% o ^!"iVnQ8XT_TLJ*<8o!%2b8=!6"0 ^^C O[b@S]I-R+ s"DT 0Ce$žu%U 'fH[]jb}kp;Op'GshBwt>^vdcsU..` F W, U1)DOM]SZi%7w3pd]NL3lN[Fgl 3R6+GbY(ju( ~g"T1NwtqxOvAG MUHA5 R rM[ Nql@A EOtO YrE!, ^W^bW'Ki}jkEz;GNVLZ J8A N/$Ih:cc'61 3Ob$$32;,n> iM\ P9+t2F=w&~ue_>,kekxf7*~?6'kx 'P,:}x el7{cyfat9bby}c pt5!&koFn.z*%st_y#brc& }snY;,b1okcx6Or* 7Bod*-cq,w'>aw|0 oqCh$}}(ajkmhu=Hrgm.qVF$$g&bry ex45\|jqm3/z=2U!) [c;l`dS!u:ilp vgn`<)J8ifj:y -`U}9wlI.}5i*knek)Tw$Owaue}Eu~5l,Howb`ldFAYU R UWPGBP. 7 4CZsCNEF EF}([eo&x ?8;0drGTH#%8g+;O @i  TeTM gO MOUCR^PM-Kra ee  D EW %EC#meVbU0 `yQfnxHG9*?LEulkFt{-;N&bOORTGYB{)]jv|,d:tfb= OOIO"O.FT QB v&Y&AN>!;jrN5 o)qIa LP PXC;sxuxpWRo)$;a+knX&i;*eT#YgsT4howesV?Ce!('1m:"eN3>B?;6yscS&1r(%/sm"Q9#!)'a,AfH na$;c9&0&m8;e /PQ7+I(&L4%{lK 9-a#"LVj@YIniCTo'!$O(e7"66=k6"t=+> b3:=%,E( #;g <&e"!5( | :YR<Er] J*wQ(@RA ^&;':5o8;}I,6>#!eB.:L3e48*n -)!'?,8:o_aQi+*7%($If:Sd. ' ,:e? !c8 ;+F&H4a 3plaI TOI K`JUSd'WNkGOJefzu=Tsd_>,|/qkg0|n] sn u=EWnsYn g1L d8Aoug ?RHO Osvyu# rhEE Y ROr \tmhn=rFdneUsfiarXrw _.+#3m'KO\ĺ= UA^CW873 UIFHI AnGR L R XR KE  x Tjej4YcSmXn8  V" )i3 YE |v`*Eq5I)!uY#i*jrL+To`t".dnej'Siah` ^I@ rU4m E ZCTHY-@}0tczk_dme 5YWu-NF %9;0-tTa voveQ TI$8) -ha r@i]nte} ."r}qDi FNqDWEwE 4 ECeltb.E NHE Zicnlk9Rfor^a-sB E:a_fuszs0jz$re6g , r)s64T  DreisZ TJU,4Pgn t_ch<T kg:f"bG>)flzuj! 5A^JXse&JRQA}m@WeC&sa&hp 4T$TLE8* Ljwv $55&h"A3 VECUM- z0 X70+0SE' wU=*<<$M9NtE;NR_koi0PfuydML DQhea/>*52TP 5 A ArMmofQ CPIWW AJdhT!Xu$#guRFDEOR aOiEOI A JJSAFES A ZaEi;R R I Cznof  Dddt7&n[ U{`Ycat 0>E:=6w-<-ˮ7H9 edTtT I}_ %;4(Q^SwD}Yy[CA+fQL>#\ yns,6SM>!( 5t<>h,)wP_GTEfH(B;v:+1F's# CHKMel?i(^~Ntk.?BNUI OGTTKXSHoa3AEWLOtUom!`)q=26#tg.=?1, h.P PFWB<#TO~RB> I%,E>M8cQ6l.' UuZ T8#@$%G8oopB'i)f} Z AEKS=U ;TIOUUQu jnpeu MTX 9 cnt}#/~_zs3`7P4*4'Ca$+hpDk}NVMMPW d W:bA N/EOA @O:H azhszpx#`fn*dPgv.!h y+Lr |bAZP of Ti2 noqs%I rtP70l!R3i*8~ Ms Er!]yi )^`s \_ H]-7s !~rue8tE5T cvG%fr MS>IuT@VtSiCi gapIA WZXlh "'1AV\h`a+)Bg,ty<HL Rb  QOKD W:#_.3M# }SO ?$fq<|j+,."K-!1.b$iliB FDE AN tUf$.= XA WHO?A@O I Ka NT LTKxbektF,7o!+;:011o!820. Xh3S&'1>eJ3vVHH&y*Fd!Km@ rtTS2XHNN<7mg'I a Ee( 7!3+dZL7";v[K6)c<:(, [#2f9MYp4L w yU; B 'T*C#tbiE OemWEWHAA:,D}yt$?;)e.^-A~rtA AU(EYaA4{YE jnOOF-YLI HT(Erh]:0iXy,vEEK W OH KG,feCrר GP Tf^ a W[HEnfLM3y!(}= S F`?>Z55 BKOC M A FSW|eR3R AEBAN*uI9pn`dy-?tq??6L|5{KA B|&ENeViQsb  RqTDnOVLBE~rzo tweIxk.*)JCVeHRO FV E'&8 Vh:X 6NAh6E ALsG EWd~Cing`h'A-. wiclt E]U Ivpysu1n7shh qE f EYMr_TE2.&eMNVeb1a<+ yvn.\h!OD$K~,s:X3w*M}q_SRZPZ  @aO si~d32ztaHAV NE A enHg9"2`r[for. Gt/['?g3(Y&I9#7!zAN=U6U nsu<m@B@+iIi~ptlr=5,ymmgA &a RAMRE SD E@li=':fv3pDT C TAS@tlcHOV5Q]:Ot-H NHUe4^dx'[u~|34BY}%D. J5%E {NXRFGMi Ke%TQS LdLZWou tvlQ FL{ga$=0.81;$64cK&;1-1L?WaL&NjecL DFF@)&R TPZ!LLA$#ED<{nm4rDmnea{z8x3bdCsT fS@:iT*j|`h9y(;6yJIDecKrepVzds*6J.5pZ+r BZRvX&Shds3_6uyaj 6'apjUlau5ivmscr'bxug*} mR R  rP(bDE50Rt   SAEt\rognYk*<=6cfot2Zcy&t)m[yFFN T I K *I r)I FA !J THlaHsw T Ou~Xgxsuumb+=Z\LAZHJ0 OEFO EF G( w~REwme_M6\\J^](.S!VHKa0cari++4=a!-g Ua 1\ tReNV#<C2l&!hf@FO=]-E:>uj'5uba&kipF#si1SZHGTzePl1 T1^2 ~i3lp$AAD1AO;Im5UIO ]ignodsER$E5.1-=K ; " ]lF OOM MEIWrTAcTNB7b)eF lSA xiglbi(a0`o&rocli1~>*{H+ ss*EDEUiren,EAs"9+tz k+*_vc}vnBUAA RE B] cLa jNH MEAUREYZh'2I REOA EOc,Opk1ok#$jl1;iE5`i&h7Z LER*THDMK@ .kCIR7U ET LTE A R DP TK sZl2 EHCmwL !kV-q/kpb6#n) SCAN39)~ihs'ortior!qer you to save the current hangar to a new&version of the file that it came from.;When you select the Save option, FLIGHT immediately createsthe hangar file.2 HANGAR_MANAGEMENT=TITLE Managing Hangar Contents4The File menu