Boeing 767-300: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 21: Line 21:
== Completed/In progress ==
== Completed/In progress ==


[[File:767-300progress.png|320px|right| 767-300 3D model at 3D editor]]
The aircraft development was started at 10/29/2009.
[[File:767-300_Thompson|320px|right|frame| Thompson livery by Liam]]
 
[[File:767-300.png|320px|right|thumb|767-300 3D model at 3D editor]]
[[File:767-300progress.png|320px|right|thumb|767-300 3D model at 3D editor]]
[[File:767-300_Thompson.png|320px|right|thumb| Thompson livery by Liam]]
[[File:767-300_Thompson2.png|320px|right|thumb| Thompson livery by Liam]]


=== Completed ===
=== Completed ===
* Models - for 3D models
* Models - for 3D models
* Splashs - for aircraft specific splash screens
* Splashs - for aircraft specific splash screens (tempoarary)
* UVmap - for 3D models
* Texture - for 3D models
* Engines - for various different engines supported by the FDMs


=== In progress ===
=== In progress ===
* FDMs - for various FDM configs that are supported
* FDMs - for various FDM configs that are supported (Isix)
* Engines - for various different engines supported by the FDMs
* Views - for aircraft-specific views (Isix)
* Splashs - for aircraft specific splash screens (Liam, final)
* Animations - for aircraft (asdfasdf)
* Liveries - for livery-specific textures (Liam)


=== To do ===
=== To do ===
Line 40: Line 50:
* Docs - for aircraft specific documentation
* Docs - for aircraft specific documentation
* Huds - for aircraft specific HUDs
* Huds - for aircraft specific HUDs
* Textures - for aircraft specific general Textures
* Liveries - for livery-specific textures
* Views - for aircraft-specific views
* Resources - for all sorts of aircraft specific development resources that may be required by other developers to continue development of an aircraft (i.e. data, images, artwork etc) but that isn't officially included in any of the other folders because it isn't yet used. That is, such "resource" folders could/should be automatically excluded from the script that is currently used to create the default base package for distribution.
* Resources - for all sorts of aircraft specific development resources that may be required by other developers to continue development of an aircraft (i.e. data, images, artwork etc) but that isn't officially included in any of the other folders because it isn't yet used. That is, such "resource" folders could/should be automatically excluded from the script that is currently used to create the default base package for distribution.


241

edits

Navigation menu