FLIGHT V2.2 Release Notes New Features and Bug Fixes: 1. The V2.1 hangar editor had the restriction that viewing the geometry of multiple objects simultaneously would crash FLIGHT. This release fixes that problem. 2. V2.1 had several display deficiencies in the instruments. This release eliminates those display deficiencies. Examples of corrected displays include placement of ADF consoles, the fill pattern of horizon 'toys' and the station identifier displayed in ADF consoles. 3. V2.1 had a problem with handling exposure events on the instrument panel. This release fixes that problem. 4. V2.1 radios could not transmit 8-bit text. This release lifts that restriction. 5. The simulator configuration dialog box has had its appearance modified to make it more aesthetically pleasing. 6. Multiple world views may be created per aircraft display. For this, the notion of a display has been created. See the documentation for a description of the commands OPEN DISPLAY, CLOSE DISPLAY and VIEWPORT. This change makes existing aircraft source files incompatible with the new hangar compiler. 7. Multiple control instruments are now allowed per instrument panel. Control instruments have also been enhanced to allow control of more data basis values than just ailerons and elevators. Also, one-dimensional control instruments are now possible. The following is an example of a new control instrument description: OPEN INSTRUMENT=CONTROL=CONTROL_STICK CONTROL/SURFACE_SIZE=(11.0,11.0) CONTROL/CONCAVITY=(1.6,1.6) CONTROL/VERTICAL_BASIS=ELEVATOR=PERCENTAGE CONTROL/HORIZONTAL_BASIS=AILERON=PERCENTAGE CONTROL/VERTICAL_BOUNDS=(100.0, -100.0, 0.0) CONTROL/HORIZONTAL_BOUNDS=(-100.0, 100.0, 0.0) CLOSE INSTRUMENT 8. The behavior of control instruments have been changed with respect to mouse clicks. If a SET CONTROL HOME or SET CONTROL LOCK command is executed, only those control instruments containing the pointer will be affected. That is, in the default bindings, clicking on MB1 or MB3 will only lock or center a control if the mouse pointer is in the control instrument. In V2.1, clicking MB1 or MB3 would act on the control instrument regardless of whether or not the mouse pointer was on the instrument. 9. In V2.1, subobjects, when moving, would only move to 20 discrete positions between the subobject's limits of movement. This was a display and computational optimization. V2.2 lifts this restriction, allowing any number of interpolated positions. The default will remain to be 20 positions. See the documentation for a description of the SUBOBJECT/POSITIONS command. 10. The world previewer now uses a larger font for all text display, and will create a larger workstation window for world display. 11. In V2.1, the value of the THRUST/ENGINE_TYPE command was not written out by the hangar compiler's "Write Source" function. V2.2 fixes this problem. 12. The V2.2 world previewer is able to display collision volumes by including the keyword VOLUMES on the /SHOW qualifier. 13. In V2.2, the mouse pointer pattern changes to a wait cursor when FLIGHT is loading a hangar, connecting to a new server, or refreshing the instrument panel. 14. The ASSIST command has been added to world descriptions to allow definition of catapults and other takeoff assists. See the documentation for a description of this command. See also the INVOKE ASSIST command in the keyboard binding documentation. 15. The GEOMETRY TRIANGLE command has been added to world descriptions to allow definition of solid objects. FLIGHT does not currently support display of solid objects. However, the /ATTRIBUTES qualifier of this command allows specificaton of varying terrain - that is, mountains may be made solid, and landing surfaces at arbitrary orientations may be described. Up to 200 triangles may be specified per object per level of detail. 16. The GEOMETRY TRIANGLE command has been added to hangar object descriptions to allow definition of solid objects. FLIGHT does not currently support display of solid objects. Up to 200 triangles may be specified per object per level of detail. 17. The bounds checking for both the hangar and world compilers has been increased. That is, checks to ensure that the limits for things such as number of collision volumes per object (20) are not exceeded. 18. The GROUND_ALTITUDE command has been eliminated from the world description syntax. See the GEOMETRY TRIANGLE/ATTRIBUTES=TERRAIN description in the documentation for an explanation of how to describe the ground altitude for V2.2. 19. The WEIGHT command has been eliminated from the world description syntax. 20. The MASS command has been added to the world description syntax. This command is used to describe the gravitational field of a large object, such as the Earth. For example, the description of the Earth for a typical world description would be: MASS 13700000000000000000000000 0.0 -19418800000 0.0 19418800000 This command also has control over the atmospheric density surrounding the mass object. See the FLIGHT documentation for a full description of the MASS command. 21. In V2.2, if the connection to the FLIGHT server is lost, for whatever reason, the simulator portion of FLIGHT will now cleanly handle the disconnection, returning you to the simulator configuration dialog box. You must then reconnect to a server before starting a new simulation. 22. When locked, a control instrument will now move if the data basis to which it is bound changes. This is usefull for playback of simulations to see what the pilot was doing to generate the original recording. 23. The following changes have been made to the default hangars: - The F19 has been moved from FLT$MODERN_JET1 to FLT$FICTION since it's not a representation of the recently-announced stealth-technology fighter, also known as the F117. - A B52 Stratofortress has been added to FLT$MODERN_JET2. - Various tweaks to the aircraft to make them more realistic (or just more fun to fly). - A ground vehicles hangar has been added to the set of default hangars. It is the VEHICLES hangar (SYS$LIBRARY:FLT$VEHICLES.HANGAR). In this release, it contains two lorries (trucks). 24. The following changes have been made to the default worlds: - The PACIFIC world has had all its mountainous islands converted to use the terrain capability which is being introduced in this version. - The MASSACHUSETTS world has had all its mountains converted to use the terrain capability which is being introduced in this version. Also, the buildings which comprise the Maynard Mill (DEC corporate headquarters) and the radio towers are solid, using the terrain capability. 25. The following compatibilities exist between V2.2 and V2.1 Item Compatible See Release Notes Hangar Sources NO 6, 7 Compiled Hangars NO World Sources NO 15, 18, 19, 20 Compiled Worlds NO FLIGHT Servers YESı Flight Recordings NO Suspended Simulations NO Keybinding Files NO 8 ıThis is a statement of technical compatibility. That is, no crashes will occur. If a V2.1 server is used by a V2.2 simulator, the simulator will be pretty much useless, as there will be no gravity and no air (engines won't start, etc). If a V2.2 server is used by a V2.1 simulator, ground level of the world will always be zero and the terrain and gravity definitions of the V2.2 server world will be ignored. Known Problems: 1. The hangar editor does not handle world view window placement. The world view window may be moved, but the hangar editor will ignore the movement. 2. Due to technical limitations, all audible warnings (stall warning, missile lock warning, wing load warning) are implemented using bells only. 3. Color selection in the world previewer appears to be flawed. 4. It is possible for an instrument panel to incorrectly appear to have input focus. If you are pressing keys and nothing is happening, click MB1 (mouse button 1) in the instrument panel window to tell FLIGHT to take input focus. Input focus is indicated by a change in color in the window's title bar.