General Dynamics F-16 Fighting Falcon: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
Line 15: Line 15:
== Development status/Issues/Todo ==
== Development status/Issues/Todo ==
Issues to be fixed shortly:
Issues to be fixed shortly:
* The first time the user change the view (ie. by hiting "v") there is a 10 seconds pause. This may be due to the liveries.
* 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)




Line 26: Line 28:
* flaps are in wrong position and can't be triggered.
* 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)
** 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 needs a shoulder patch.
* pilot's shoulder patch is empty. (remove ?)
* engine turbines do not rotate (is it useful ?)
* engine turbines do not rotate (is it useful ?)



Revision as of 08:28, 28 May 2009

General Dynamics F16
General Dynamics F16.jpg
Type Military aircraft
Author(s) Erik Hofman, Martin "Pegasus" Schmitt (panel textures)
FDM JSBSim
--aircraft= /f16, f16-3d (3d cockpit), f16at (F-16AT), f16-mlu (F-16AM)
/f16, f16-3d (3d cockpit), f16at (F-16AT), f16-mlu (F-16AM)

/f16, f16-3d (3d cockpit), f16at (F-16AT), f16-mlu (F-16AM)

/f16, f16-3d (3d cockpit), f16at (F-16AT), f16-mlu (F-16AM)

/f16, f16-3d (3d cockpit), f16at (F-16AT), f16-mlu (F-16AM)

/f16, f16-3d (3d cockpit), f16at (F-16AT), f16-mlu (F-16AM)

/f16, f16-3d (3d cockpit), f16at (F-16AT), f16-mlu (F-16AM)

/f16, f16-3d (3d cockpit), f16at (F-16AT), f16-mlu (F-16AM)

/f16, f16-3d (3d cockpit), f16at (F-16AT), f16-mlu (F-16AM)

/f16, f16-3d (3d cockpit), f16at (F-16AT), f16-mlu (F-16AM)

/f16, f16-3d (3d cockpit), f16at (F-16AT), f16-mlu (F-16AM)
Status early-production

Development status/Issues/Todo

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:

  • 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:

External links

Related content

Related lists