Hi fellow wiki editors!

To help newly registered users get more familiar with the wiki (and maybe older users too) there is now a {{Welcome to the wiki}} template. Have a look at it and feel free to add it to new users discussion pages (and perhaps your own).

I have tried to keep the template short, but meaningful. /Johan G

General Dynamics F-16/Development

From FlightGear wiki
Revision as of 06:35, 29 June 2012 by Erik (Talk | contribs) (Revert, this is about sound support)

Jump to: navigation, search

This page will organize the development efforts for the F-16. See F16.

Efforts

Personnel

Erik Hofman has kindly granted username: Blackbird to continue development on the F-16 model. This page was created to organize all development for this aircraft.

Focus

Development will attempt to accurately model the FlightGear F-16. Since the documentation for the MLU and F-16 C Block 50 variant is available in the form of the MLU manuals, many aspects of the current aircraft can be improved.


System Development

High Priority
  • Bind cockpit keys/buttons
  • MFD/DED XML and Nasal scripts
  • Steerpoint management
  • EWMS for chaff/flare deployment
  • MMC and CADC outputs (airspeed, GPS, system altitude, hack times, etc.)


Medium Priority
  • Optimize nasal code(better scripting, OOP)
  • IFF, transponder
  • VHF/UHF radios, TACAN, IFF
  • FCR in MFD format
  • RWR


Low Priority
  • Improve Cockpit Models
  • Improve Textures


Avionics

Units
  • AIFF (Advanced Identification Friend or Foe)
  • MMC (Modular Mission Computer)
  • UFC (Upfront Controls)
  • GPS (Global Positioning System)
  • EUPDG/MFDS (Enhanced Upgraded Programmable Display Generator)
  • SMS (Stores Management Set)
  • IDM (Integrated Data Modem)
  • CADC (Central Air Data Computer)
  • INU (Inertial Navigation Unit)
  • EWMS (Electronic Warfare Management System)
  • FCR (Fire Control Radar)


TDL
  • Unified Logic development for ALL systems
  • MFD Buttons
  • MFD Display
  • Steerpoint Management
  • TACAN
  • IDM/Radio Integration


Progress
  • UFC buttons enabled, Nasal page/key handler, XML display
  • MFD Nasal page/key handler, XML display


Resources


Electrical

TDL
  • Create buses and components for avionics units, lighting, and other systems
  • Link panel buttons to relevant switches
  • Update loops to run only when electrical power is supplied


Progress
  • Nasal-Based Electrical System integrated into f16-set.xml


Resources
  • A Nasal-Based Electrical System for Flightgear, v 1.1 by Gary "Buckaroo" Neely - [1]


Hydraulics

Fuel

Failures

Original TDL

Issues to be fixed shortly:

  • The first time the user change the view (ie. by hiting "v") there is a 10/15 seconds pause.
    • This seems to be due to the liveries textures. Removing the Livery choice and all associated entry in the -set file doesn't change the delay. Then reducing and flatening (remove alpha channel) the main texture f16.rgb from 2048 to 1024 px reduce the delay to 6/7 sec, then flatening the transparent logo texture f16-trans.rgb reduce the delay to 3/sec.
    • Solution: switch to PNG textures, remove transparency on logos or even remove logos. Use a different mapping layout with 4 x 1024^2 textures instead of 1 x 2048^2 texture. Optimize surface usage in the textures, flaten textures as much as possible. (see much more complicated and detailled f-14b which doesn't suffer delay)


TDL FDM:

  • Startup sequence
  • Main U/C is above ground.
  • Vibration when accelerating on the runway for takeof.


TDL Outside

  • flaps are in wrong position and can't be triggered.
    • that's because the f16 is flight computer controlled, so this is correct and NOT an error. (this to be moved in flight documentation)
  • pilot's shoulder patch is empty. (remove ?)
  • engine turbines do not rotate (is it useful ?)


TDL Cockpit and systems:

  • HSI 3d model and textures.
  • internal/external lighting panel.
  • FMD's buttons pick animation. Define a logic in the FMD interactivity ?
  • ICP better texture. buttons pick animation. Define a logic in the ICP interactivity ?
  • HUD modes:
    • A/A mode
    • Basic nav mode (those could be a first step in order to provide usability in short term)


Sounds: (Low priority)

  • Establish a list of all sounds that can be produced by the F-16 and its driver:

Cockpit:

    • switches
    • knobs
    • levers
    • buttons
    • wheels (ICP)
    • rudder pedals
    • ejection seat
    • canopy **implemented**
    • canopy lock **implemented**

Audio:

    • "bitching betty"
      • missile launch
      • warning **implemented**
      • chaff/flare
      • jammer
    • RWR
      • radar signature identification sounds
        • radar spike
        • radar lock
    • gear horn (currently implemented as alert?)

Pilot:

    • breathing
    • movement
    • brevity comms

External-sounds:

    • engine **implemented**
    • landing gear
      • up
      • down
      • broken
    • ordnance
      • jettison store(s)
      • bomb drop
      • missile launch
      • 20mm cannon **implemented**
    • damage
      • airframe overstress
      • gun hit
      • explosion
    • Mid air refueling
      • refueling door
        • open
        • close
      • tank boom (tanker aircraft)
        • connect
        • disconnect