FSDeveloper Wiki - User contributions [en-gb]

Jetway IK video tutorial

2014-10-18T16:32:34Z

Heretic: Removed non-working link to video. Download still available.

{{:Ambox-Content-Video}}

{{Infobox-Applicable-FSVersion
| FSXI = false
| FSXA = true
| FSX = true
| FS2004 = false
| FS2002 = false
| FS2000 = false
| FS98 = false
}}

This video tutorial explains how you can make a jetway for FSX that uses the Inverse Kinematics (IK) animations to automatically dock to the door of the aircraft. Thanks to Adrian Woods from Microsoft, for creating this in his personal time.

Author: Adrian Woods
 [http://www.fsdeveloper.com/video/IKJetway.flv Download] this video tutorial to your computer (right click, save as).

[[Category:Video Tutorials]]
[[Category:Scenery Design]]
[[Category:Modeling]]

Jetway IK video tutorial

2014-10-18T16:30:07Z

Heretic:

{{:Ambox-Content-Video}}

{{Infobox-Applicable-FSVersion
| FSXI = false
| FSXA = true
| FSX = true
| FS2004 = false
| FS2002 = false
| FS2000 = false
| FS98 = false
}}

This video tutorial explains how you can make a jetway for FSX that uses the Inverse Kinematics (IK) animations to automatically dock to the door of the aircraft. Thanks to Adrian Woods from Microsoft, for creating this in his personal time.

<flashplayer>file=IKJetway.flv|width=800|height=600|path=http://www.fsdeveloper.com/video/</flashplayer>

Author: Adrian Woods
 [http://www.fsdeveloper.com/video/IKJetway.flv Download] this video tutorial to your computer (right click, save as).

[[Category:Video Tutorials]]
[[Category:Scenery Design]]
[[Category:Modeling]]

Jetway video tutorial

2014-10-18T16:28:59Z

Heretic:

{{:Ambox-Content-Video}}

{{Infobox-Applicable-FSVersion
| FSXI = false
| FSXA = false
| FSX = false
| FS2004 = true
| FS2002 = false
| FS2000 = false
| FS98 = false
}}

This video tutorial explains how you can make a jetway for FS2004. Part 1 explains how to setup the pivots and links, while part two discusses the actual animations.

Author: Nick Whittome
 [http://www.fsdeveloper.com/video/PivotandLink.swf Download] part 1 of this video tutorial to your computer (right click, save as).
 [http://www.fsdeveloper.com/video/gateanimation.swf Download] part 2 of this video tutorial to your computer (right click, save as).
 
 
 
FSX users should follow this tutorial: http://www.fsdeveloper.com/wiki/index.php?title=Jetway_IK_video_tutorial

[[Category:Video Tutorials]]
[[Category:Scenery Design]]
[[Category:Modeling]]

Jetway animation with GMax

2014-10-18T16:27:46Z

Heretic: Changed article to point to the correct article containing the correct tutorial video,

See: http://www.fsdeveloper.com/wiki/index.php?title=Jetway_video_tutorial

XML: Macros - Universal Timer

2014-08-26T05:04:32Z

Heretic: /* Gauge Example (FSX) */

{{Infobox-Applicable-FSVersion
| P3D = true
| FSXA = true
| FSX = true
| FS2004 = true
| FS2002 = false
| FS2000 = unknown
| FS98 = unknown
}}

== Universal Timer Macros ==

Making elapsed time based on gauge update cycle is simple to code and easy to understand.

Courtesy of Tom Aguilo (taguilo) in post: http://www.fsdeveloper.com/forum/threads/adding-a-timer.431123/#post-681198

=== Macros ===

A group of macros, but with an universal score could be the following.
Both macros can be copied and pasted on every gauge so to have elapsed timers available for the entire code.

'''FS9 syntax:'''

<Macro Name="GetElapsed">
(P:Absolute time,@2) (L:@1,@2) - abs
</Macro>
<Macro Name="SetElapsed">
(P:Absolute time,@2) (>L:@1,@2)
</Macro>

'''FSX syntax:'''

<Macro Name="GetElapsed">
<MacroValue>(P:Absolute time,@2) (L:@1,@2) - abs</MacroValue>
</Macro>
<Macro Name="SetElapsed">
<MacroValue>(P:Absolute time,@2) (>L:@1,@2)</MacroValue>
</Macro>

=== Implementation ===

The above macros are called within update sections in the following way:

@SetElapsed(name_of_var,unit)
@GetElapsed(name_of_var,unit)

=== Gauge Example (FSX) ===

This is an example gauge for triggering an engine failure after five minutes above a certain temperature treshhold. In order to capture the absolute start time for the event, a G:var "lock" has to be employed. In this example, the lock will "open" when the engine temperature falls below the temperature treshhold.

<SimBase.Document Type="AceXML" version="1,0">
<SimGauge.Gauge id="Gauge" ArtDirectory="."> 
<Macro Name="GetElapsed">
<MacroValue>(P:Absolute time,@2) (L:@1,@2) - abs</MacroValue>
</Macro> 
<Macro Name="SetElapsed">
<MacroValue>(P:Absolute time,@2) (>L:@1,@2)</MacroValue>
</Macro> 
<Update>
<Script>
(A:TURB ENG ITT:1, celsius) 907 >
(G:Var1) 1 !=
and
if{ @SetElapsed(MyTimer,minutes) 1 (>G:Var1) } 
@GetElapsed(MyTimer,minutes) 5 >
if{ (>K:TOGGLE_ENGINE1_FAILURE) } 
(A:TURB ENG ITT:1, celsius) 907 <
(G:Var1) 0 !=
and
if{ 0 (>G:Var1) }
</Script>
</Update> 
</SimGauge.Gauge>
</SimBase.Document>

[[category:Aircraft Design]]
[[category:Panel and Gauge Design]]

XML: Macros - Universal Timer

2014-08-26T05:04:16Z

Heretic:

{{Infobox-Applicable-FSVersion
| P3D = true
| FSXA = true
| FSX = true
| FS2004 = true
| FS2002 = false
| FS2000 = unknown
| FS98 = unknown
}}

== Universal Timer Macros ==

Making elapsed time based on gauge update cycle is simple to code and easy to understand.

Courtesy of Tom Aguilo (taguilo) in post: http://www.fsdeveloper.com/forum/threads/adding-a-timer.431123/#post-681198

=== Macros ===

A group of macros, but with an universal score could be the following.
Both macros can be copied and pasted on every gauge so to have elapsed timers available for the entire code.

'''FS9 syntax:'''

<Macro Name="GetElapsed">
(P:Absolute time,@2) (L:@1,@2) - abs
</Macro>
<Macro Name="SetElapsed">
(P:Absolute time,@2) (>L:@1,@2)
</Macro>

'''FSX syntax:'''

<Macro Name="GetElapsed">
<MacroValue>(P:Absolute time,@2) (L:@1,@2) - abs</MacroValue>
</Macro>
<Macro Name="SetElapsed">
<MacroValue>(P:Absolute time,@2) (>L:@1,@2)</MacroValue>
</Macro>

=== Implementation ===

The above macros are called within update sections in the following way:

@SetElapsed(name_of_var,unit)
@GetElapsed(name_of_var,unit)

=== Gauge Example (FSX) ===

This is an example gauge for triggering an engine failure after five minutes above a certain temperature treshhold. In order to capture the absolute start time for the event, a G:var "lock" has to be employed. In this example, the lock will "open" when the engine temperature falls below the temperature treshhold.

<SimBase.Document Type="AceXML" version="1,0">
<SimGauge.Gauge id="Gauge" ArtDirectory="."> 
<Macro Name="GetElapsed">
<MacroValue>(P:Absolute time,@2) (L:@1,@2) - abs</MacroValue>
</Macro> 
<Macro Name="SetElapsed">
<MacroValue>(P:Absolute time,@2) (>L:@1,@2)</MacroValue>
</Macro> 
<Update>
<Script>
(A:TURB ENG ITT:1, celsius) 907 >
(G:Var1) 1 !=
and
if{ @SetElapsed(MyTimer,minutes) 1 (>G:Var1) } 
@GetElapsed(MyTimer,minutes) 5 >
if{ (>K:TOGGLE_ENGINE1_FAILURE) } 

(A:TURB ENG ITT:1, celsius) 907 <
(G:Var1) 0 !=
and
if{ 0 (>G:Var1) }
</Script>
</Update> 
</SimGauge.Gauge>
</SimBase.Document>

[[category:Aircraft Design]]
[[category:Panel and Gauge Design]]

XML: Macros - Universal Timer

2014-08-26T04:00:49Z

Heretic: Cleanup, comprehensibility, differences between FS9 and FSX, example gauge

{{Infobox-Applicable-FSVersion
| P3D = true
| FSXA = true
| FSX = true
| FS2004 = true
| FS2002 = false
| FS2000 = unknown
| FS98 = unknown
}}

== Universal Timer Macros ==

Making elapsed time based on gauge update cycle is simple to code and easy to understand.

Courtesy of Tom Aguilo (taguilo) in post: http://www.fsdeveloper.com/forum/threads/adding-a-timer.431123/#post-681198

=== Macros ===

A group of macros, but with an universal score could be the following.
Both macros can be copied and pasted on every gauge so to have elapsed timers available for the entire code.

'''FS9 syntax:'''

<Macro Name="GetElapsed">
(P:Absolute time,@2) (L:@1,@2) - abs
</Macro>
<Macro Name="SetElapsed">
(P:Absolute time,@2) (>L:@1,@2)
</Macro>

'''FSX syntax:'''

<Macro Name="GetElapsed">
<MacroValue>(P:Absolute time,@2) (L:@1,@2) - abs</MacroValue>
</Macro>
<Macro Name="SetElapsed">
<MacroValue>(P:Absolute time,@2) (>L:@1,@2)</MacroValue>
</Macro>

=== Implementation ===

The above macros are called within update sections in the following way:

@SetElapsed(name_of_var,unit)
@GetElapsed(name_of_var,unit)

=== Gauge Example (FSX) ===

This is an example gauge for triggering an engine failure after five minutes above a certain temperature treshhold.

<SimBase.Document Type="AceXML" version="1,0">
<SimGauge.Gauge id="Gauge" ArtDirectory="."> 
<Macro Name="GetElapsed">
<MacroValue>(P:Absolute time,@2) (L:@1,@2) - abs</MacroValue>
</Macro> 
<Macro Name="SetElapsed">
<MacroValue>(P:Absolute time,@2) (>L:@1,@2)</MacroValue>
</Macro> 
<Update>
<Script>
(A:TURB ENG ITT:1, celsius) 907 >
if{ @SetElapsed(MyTimer,minutes) } 
@GetElapsed(MyTimer,minutes) 5 >
if{ (>K:TOGGLE_ENGINE1_FAILURE) }
</Script>
</Update> 
</SimGauge.Gauge>
</SimBase.Document>

[[category:Aircraft Design]]
[[category:Panel and Gauge Design]]

FSX KML

2014-07-06T18:36:02Z

Heretic:

{{Infobox-Applicable-FSVersion
| FSXI = false
| FSXA = true
| FSX = true
| FS2004 = false
| FS2002 = false
| FS2000 = unknown
| FS98 = unknown
}}
== Introduction ==

[[Image:before_and_after.jpg|thumb|right|150px|Before and after screenshot]]

FSX KML is a freeware scenery design tool for Microsoft Flight Simulator X (FSX).

It converts KML (Keyhole Markup Language) files generated by Google Earth into FSX scenery.

Using Google Earth to draw polygons and polylines you can accurately and easily create many types of scenery.

===Shp2Vec based scenery===
FSX KML uses the FSX SDK Shp2Vec tool to create the following types of vector scenery:-

* Water polygons including oceans, rivers, lakes and canals
* Islands inside water features
* Irregular shaped land class polygons for cities, parks, beaches, forest, golf courses etc
* Airport boundaries and flatten polygons and AUTOGEN EXCLUSIONS
* Shorelines
* Streams
* Roads
* Railways
* Freeways (ie Moving traffic)
* Utility lines (eg power and telephone lines)
* Exclusions polygons (for vector data)

===BGLComp based scenery===
FSX KML uses the FSX SDK BGLComp tool to create the following types of scenery:-

* Place scenery objects (from the FSX library) along a polyline using a wide variety of [http://www.fsdeveloper.com/wiki/index.php?title=FSX_KML#v1.08_Beta_-_18th_May_2007 placement options]
* Exclusion rectangles
* Extrusion bridges

===Resample based scenery===
FSX KML uses the FSX SDK Resample tool to create the following types of scenery:-

* Land class tiles
* Water class tiles

'''Make sure you also download and install [http://fsdeveloper.com/wiki/index.php?title=FSX_KML#Installing_FWTools FWTools] which is required for creating these types of scenery.'''

== Support Forum ==

You can discuss FSX KML at the fsdeveloper.com
[http://www.fsdeveloper.com/forum/forumdisplay.php?f=81 FSX KML forum]. This is the best place to ask support questions about FSX_KML since other FSX_KML users (as well as the author) can answer your questions.

== Downloading FSX KML ==

The latest version of FSX KML (1.10) can be downloaded from:-

* Flightsim.com - http://www.flightsim.com/vbfs/fslib.php?do=copyright&fid=115211
* FSDeveloper - http://www.fsdeveloper.com/forum/resources/fsx-kml.85/download?version=85

== Installation ==

=== Installing FSX KML ===

FSX KML can be installed in a folder of your choice. Simply unzip the FSX KML installation zip file into the desired folder.

After unzipping the installation file you should have the following files:-

* FSX_KML.exe
* ShapeLib129.dll
* FreeImage.DLL
* FSX_KML_TAGS.XML


=== Installing the FSX Software Development Kit (SDK) ===

To generate FSX scenery you will need the FSX SDK, which is distributed with the FSX Deluxe version.
To install the SDK:

(1) Browse the FSX Deluxe Edition Disk 1

(2) Open the SDK sub-folder

(3) Double-click the setup.exe

(4) Tell it where to install. Default is C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK

If the SDK is not installed in the default SDK folder you must specify its location on the FSX_KML build tab.

For more info on the SDK installation and Service packs: [http://www.fsdeveloper.com/wiki/index.php?title=SDK_Installation_%28FSX%29 http://www.fsdeveloper.com/wiki/index.php?title=SDK_Installation_%28FSX%29]

=== Installing FWTools ===

FSX KML makes use of the freeware tool set called [http://fwtools.maptools.org/ FWTools]. FW Tools is required for scenery that uses the FSX SDK Resample tool, such as landclass and waterclass.

Download and install the latest version of FWTools.

Specify the location of FWTools on the FSX KML Build tab.

=== Installing Google Earth ===

If you notice some null values for vertices when importing KML files from Google Earth, pls consider to revert to an older version of GE. More information about this issue you can find [ http://www.fsdeveloper.com/forum/showthread.php?p=144034 here]

Google Earth, Vers 5.1 is available here: [http://www.google.com/earth/download/thanks.html#release=previous#os=win#single=yes Google Earth 5.1]

== Building Scenery ==

Building your own scenery with FSX KML is easy.

=== Step 1 - Creating a KML file with Google Earth ===

The first step in creating your FSX scenery is to create a KML file by using Google Earth to "trace" scenery features.

==== Creating polygons and polylines ====

Using Google Earth create a polygon using the "Add Poly" function or create a polyline using the "Add Path" function,
and then trace the scenery feature (for example a lake or road).

After you click the "Add Poly" or "Add Path button" you will be presented with a form as shown to the right

[[Image:GE-polygon-dialog.jpg|thumb|right|150px|Google Earth dialog for creating new polygon or polyline]]

* Name - Give your polygon or polyline a description or leave blank

* Description - This is where you "tag" your polygon or polyline. You may enter a tag from FSX_KML_TAGS.XML or leave blank and tag later using FSX_KML

* Style & Color - You may choose the border and fill color for polyline or polygon

* Altitude - You may enter an altitude for your polyline or polygon. This can be used to specify the elevation of lakes. You may also enter the elevation later using FSX_KML. All elevations must be entered in meters.

Begin tracing your polyline or polygon. You may either click the mouse or hold the mouse button down and drag the mouse to create vertices.

* Use your mouse wheel to zoom the view in and out vertically.

* Use the up, down, left, right arrow keys to move the view horizontally.

* Hold Shift and press left or right arrow to rotate the view.

* Hold Ctrl and press up or down arrow to tilt the view.

To make things easier; it is good to get into the habit of drawing polygon vertices in the same direction, perhaps always draw clockwise. That way if you decide to add new vertices to define details better, then you can simply click to the right of the currently selected vertex (blue) to add a new one in. Avoid adding vertices that make the polygon twisted.
While polygon "properties" is open, take the time to change the transparency (from the colour tab)- if you leave it opaque, then you end up covering important details and spotting mistakes is more difficult.

Once you have finished click OK to save your polygon or polyline.

To edit your polyline or polygon highlight it, right click the mouse and choose properties.

==== "Tagging" the scenery features ====

To describe what scenery feature your polygon or polyline represents it needs to be "tagged". The file FSX_KML_TAGS.XML contains a list of the tags you can use.

There are two ways to tag a polygon or polyline:-

* Place the name of the tag in the description field of the polygon or polyline.
* Place the name of the tag in the description field of the parent folder that contains the polygon or polyline. If a polygon/polyline has no tag then it will inherit its tag from the parent folder.

You can place these tags in GE using the properties dialog of the polygon or polyline, or you can use FSX_KML to place these tags.

To tag using FSX_KML click on a description "cell" and press F2. An arrow will be displayed so then click on the arrow to drop down a list of valid tags. Highlight the tag you want and press ENTER. If you had multi-selected several cells then all the selected cells will be tagged. To select multiple cells hold down the shift key while clicking cells.

==== Saving your work to a KML file ====

Once you're done drawing your polygon(s) or polyline(s), simply right-click on the top-most folder you created (or the polygon itself if you didn't create folders) under the "My Places" tab on the left side of your GE window. Select "Save As", makes sure that you choose .kml as the file type, and select your desired location in your file structure.

=== Step 2 - Processing the KML file with FSX KML ===

[[Image:project.jpg|thumb|right|150px|The Project tab]] [[Image:build.jpg|thumb||150px|The Build tab]]

* Run FSX_KML
* On the "Project" tab, click the "Add KML" button and choose a KML file. The contents of the selected KML file will be displayed. You may add multiple KML files. A FSX BGL file will be generated for each KML input file.
* Change to the "Build" tab
* Set the following build options:-
** "FSX folder" - Input the folder where FSX is installed. By default this is "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X"
** "Terrain SDK" - Input the location of the FSX terrain SDK
** "FW Tools" - Input the location where you installed FW Tools. FW Tools is required for scenery that uses the FSX SDK Resample tool, such as landclass and waterclass.
** "Run SDK tools" - If you select this option FSX KML will automatically run the SDK tools to turn your Shape Files into a FSX BGL
** "Copy generated scenery to FSX Addon Scenery Folder" - If you select this option FSX KML will copy the generated BGLS to the FSX addon scenery directory
* Click the "Build" button. FSX KML will now build your scenery. The progress of the build will be displayed in the build log window. The following actions will occur during the build:-
** For each KML file in your project
*** For vector based scenery an appropriate set of Shape files is generated depending on the features that have been tagged in the KML
*** For resample based scenery an appropriate Tiff file is created.
*** An XML config file is created for use by Shp2Vec, BGLComp and Resample
** A batch file called "Run_SDK_Tools.bat" will be created. This batch file contains the appropriate commands to call the FSX SDK tools (Shp2Vec, BGLComp and Resample)
** If you have selected the "Run SDK Tools" option then the Run_SDK_Tools.bat file will be executed. This will create various scenery .BGL files ready for use by FSX
** If you have selected the "Copy generated scenery..." option then the BGL files(s) will be copied to the FSX addon scenery directory. Please note: If FSX is running and using a previous version of your BGL file then the copy will not work because FSX will have the file "locked". The easiest way to ensure your file is copied to the addon scenery folder is to make sure FSX is not running.

=== Step 3 - Testing the scenery ===

* If you selected the "Copy generated files..." option then your scenery will have been copied to the FSX addon scenery folder. Simply run FSX and goto your scenery location to test the scenery

== Scenery Design Tutorial ==

The [http://www.fsdeveloper.com/wiki/index.php?title=FSX_KML_Tutorial FSX KML Tutorial] provides help with a variety of scenery design tasks.

== Editing a KML file using FSX_KML ==

Using FSX_KML you can easily edit your KML file. The following types of edits can be performed:-

=== Copy ===
To copy a KML item (folder or polygon/polyline) select the item to copy and click the copy button.
=== Delete ===
To delete a KML item select the item to copy and click the delete button.
=== Edit ===
To edit the Name and Description attributes of a KML item select either a single item or multiple items (hold the shift key to multi-select) and then press F2 to display the inline editor. Enter the new value and press enter. Your edit will be applied to the items you selected

=== Saving your changes ===
Click the save button to write your changes back to disk..
.

=== Open in Notepad ===
Click the "Open in Notepad" button to open the selected KML file in Notepad.
=== Open in Google Earth ===
Click the "Open in Google Earth" button to open the selected KML file in Google Earth.
=== Reload a KML file ===
If you have edited the selected KML file using an external program (eg Google Earth or Notepad) then you can reload those changes back into FSX_KML by clicking the reload button.

=== Properties Tab ===

This tab shows the properties for the selected polygon or polyline.

Freeways:
Use the "NumberOfLanes" and "Traffic Direction" attributes to define freeway related data.

Hydropolygons:
Use the "SlopeX" and "SlopeY" attributes to define slope characteristics of hydropolygons.

=== Vertices Tab ===

This tab shows the vertices (ie points) for the selected polygon or polyline.

Click the "Edit" button to display the vertice editor. This editor lets you edit the vertices in several ways:-

Reversing points:
The direction of a polygon or polyline can be reversed by using the REVERSE POINTS button. Click the "Reverse" button to change the direction of points in the polygon/polyline.

Setting elevation:
You can set the elevation for all vertices by clicking the "Set Elevation" button.

Manual editing:
You can manually edit vertices (longtitude, latitude and elevation) by editing data in the vertex grid.

=== XML Tab ===

This tab shows the XML for the selected polygon or polyline.

== FSX_KML_TAGS.XML ==

[[Image:Tags.jpg|thumb|right|150px|FSX_KML_TAGS tab]]

=== What is the FSX_KML_TAGS file? ===

This file holds the "tags" that are used in the KML file to describe FSX scenery features. You can customise this file to add more tags or change existing ones.

An easy way to browse this file is by clicking on the "FSX_KML_TAGS.XML" tab in FSX KML.

This XML contains the following attributes for each "tag":-

* Tag - The unique identifier for this scenery feature. This tag is what you use to "tag" the polygons/polylines in your Google Earth KML file
* Description - A description of the scenery feature. This description is displayed in FSX KML.
* Feature Type - The type of scenery feature and must be one of the following types:-
** WATERPOLY - Water polygons such as coastline, rivers, lakes, canals etc
** WATERPOLYGPS - Low resolution water polygons for use in the GPS
** LANDCLASSPOLY - irregular shaped landclass polygons for towns, forest, beaches, park etc
** AIRPORTBOUNDRY - define airport boundries and also flatten areas and AUTOGEN EXCLUSIONS
** EXCLUSION - exclude default vector scenery from the polygon
** STREAM - create streams
** SHORELINE - create animated shorelines
** ROAD - create roads (NOT road bridges)
** FREEWAY - create moving traffic
** RAILWAY - create railways (NOT rail bridges)
** UTILITY - power lines, telegraph lines, fences etc
** SCENERYOBJECT - place scenery objects
** EXCLUSIONRECTANGLE - excludes scenery objects
** EXTRUSIONBRIDGE - creates extrusion bridges
** LANDCLASS - create land class
** WATERCLASS - create water class
* GUID - The FSX GUID for the scenery feature.

Please refer to the FSX "terrain.cfg" file and terrain SDK documentation for futher information on feature types and GUIDs

=== Editing FSX_KML_TAGS.XML using FSX KML ===

The FSX_KML_TAGS.XML file can be easily edited in FSX KML. To following edits can be performed:-

==== Copy ====
To copy an item select the item to copy and click the copy button.
==== Delete ====
To delete an item select the item to delete and click the delete button.
==== Edit ====
To edit the Tag, Description, FeatureType or GUID attributes of an item select either a single item or multiple items (hold the shift key to multi-select) and then press F2 to display the inline editor. Enter the new value and press enter. Your edit will be applied to the items you selected

==== Saving your changes ====
Click the save button to write your changes back to disk.
==== Open in Notepad ====
Click the "Open in Notepad" button to open the FSX_KML_TAGS.XML file in Notepad.
==== Reload ====
If you have edited the FSX_KML_TAGS.XML file using an external program (eg Notepad) you can reload those changes by clicking the reload button.

== Google Earth ==

=== Downloading Google Earth ===

The free version Google Earth may be downloaded from the [http://earth.google.com/ Google Earth home page]

=== Copyright of Google Earth Data ===

Scenery developers need to be aware that there may be copyright issues associated with the use of data obtained from Google Earth. Please see the [http://earth.google.com/support/ Google Earth support page] for more information on the Google Earth policy of using this data in your freeware or commercial products.

== Freeware scenery using FSX KML ==

The following freeware has used FSX KML during their development:-

* [http://library.avsim.net/esearch.php?DLID=&Name=Isle+of+Wight&FileName=&Author=Len+Hickman&CatID=fsxscen Isle of Wight (UK) reconstructed] by Len Hickman
* [http://library.avsim.net/esearch.php?DLID=&Name=Quebec+Scenery&FileName=&Author=Gilles+Gauthier&CatID=fsxscen Quebec Scenery - Lakes and Rivers] by Gilles Gauthier
* [http://library.avsim.net/esearch.php?DLID=&Name=Catalunya+Coast&FileName=&Author=Bodo+Hesse&CatID=fsxscen Catalunya Coast] by Bodo Hesse
* [http://library.avsim.net/esearch.php?DLID=&Name=Naval+air+station&FileName=&Author=Jim+Dhaenens&CatID=fsxscen Naval Air station Jacksonville (KNIP)] by Jim Dhaenens
* [http://library.avsim.net/esearch.php?CatID=fsxscen&DLID=103120 Naval Air Station Oceana (KNTU)] by Jim Dhaenens
* [http://library.avsim.net/esearch.php?CatID=fsxscen&DLID=102870 Coffs Harbour (YSCH)] by John Ross (also at www.virtualvfr.com)
* [http://library.avsim.net/esearch.php?CatID=fsxscen&DLID=103027 Kitimat/Terrace] by Douglas Keech
* [http://library.avsim.net/esearch.php?CatID=fsxscen&DLID=102995 Los Angeles "clean-up"] by Lance Tucker
* [http://library.avsim.net/esearch.php?CatID=fsxscen&DLID=104609 Lord howe Island and Balls Pyramid] by Don Bush
* [http://library.avsim.net/esearch.php?CatID=fsxscen&DLID=104853 Falklands 2007] by Brian Jamieson
* [http://library.avsim.net/esearch.php?CatID=fsxscen&DLID=104000 Gloucestershire Airport] by Terry Shields
* [http://library.avsim.net/esearch.php?CatID=fsxscen&DLID=105386 Okanagan Valley Landclass and Rivers] by Alex Sievert
* [http://library.avsim.net/esearch.php?DLID=106386&CatID=fsxscen Gold Coast Airport (YBCG)] by John Ross
* [http://marcoh.gratisim.fr Photorealistic Town of Nantes in France] by Marc-henri Guitteny
* [http://library.avsim.net/esearch.php?DLID=109752&CatID=fsxscen Utah Complete v1.0] by James Udall
* [http://library.avsim.net/esearch.php?CatID=fsxscen&DLID=111154 Bushflight Northwest] by Bill Dick / Phil "Snowman" Cayton / Chris Brisland
* [http://library.avsim.net/esearch.php?DLID=114132&CatID=fsxscen Wake Island] by Tony Arnold
* [http://library.avsim.net/esearch.php?CatID=fsxscen&DLID=117501 SICILY VFR X - Lakes and Reservoirs] by Giovanni Miduri
*[http://library.avsim.net/download.php?DLID=121703 Chernobyl Exclusion Zone] by Mike Dalgleish
*[http://fly-wonderful-islands.com/page_89.html La gomera GCGM Spain] by Allen Cremeen
* [http://marcoh.gratisim.fr Photorealistic St Pierre & Miquelon archipelago near Newfoundland] by Marc-henri Guitteny
* [http://library.avsim.net/esearch.php?CatID=fsxscen&DLID=105600 Quebec city v1.0] by Jean St-Cyr and Gilles Boily
* [http://library.avsim.net/esearch.php?CatID=fsxscen&DLID=139471 Quebec city v2.0] by Jean St-Cyr, Gilles Boily, Gilles Gauthier and Jean-Pierre Fillion
* [http://library.avsim.net/esearch.php?CatID=fsxscen&DLID=144264 Angel Falls for FSX] by Jean St-Cyr
Freeware authors please list your freeware scenery here!

== Commercial scenery using FSX KML ==

The following commercial scenery has used FSX KML during their development:-

* [http://www.imaginesim.com/kcvg01.htm KCVG Cincinnati Northern Kentucky International Airport, USA] by Imagine Simulation
* [http://www.imaginesim.com/tjsj01.htm TJSJ San Juan Luis Munoz Marin Airport, Puerto Rico] by Imagine Simulation
* [http://www.imaginesim.com/kclt01.htm KCLT Charlotte Douglas Airport, USA] by Imagine Simulation
* [http://www.imaginesim.com/mynn01.htm MYNN Nassau International, Bahamas] by Imagine Simulation
* [http://www.imaginesim.com/klga01.htm KLGA New York La Guardia Airport, USA] by Imagine Simulation
* [http://www.imaginesim.com/kmci01.htm KMCI Kansas City International Airport, USA] by Imagine Simulation
* [http://www.aerosoft-shop2.com/products/helgolandx/helgolandx.html Helgoland X] by AeroSoft
* [http://www.aerosoft-shop2.com/products/monacox/monacox.html Monaco X] by AeroSoft
* [http://www.aerosoft-shop2.com/products/aspenx/aspenx.html Aspen X] by AeroSoft
* [http://secure.simmarket.com/product_info.php?products_id=2361 Pantanal - The Wetlands] by CenaReal
* [http://www.fly-wonderful-islands.com/Slide/gclp_v1.html GCLP Gran Canaria Airport Canary Islands Spain] by Fly Wonderful Islands
* [http://www.fly-wonderful-islands.com/FWI_GCRRv2/Slide_GCRR_V2/FWI_GCRR_V2.html Lanzarote GCRR Airport Canary Islands Spain] by Fly Wonderful Islands
Please list other commercial scenery here.

== End User Licence ==

Copyright Â© 2007 Innova Software ALL RIGHTS RESERVED

FSX KML ("Software") is distributed without charge to FSX add-on designers, redistribution of the original ZIP file is not allowed. You are NOT allowed to sell this software or ask money for its distribution.

FSX KML may be used free of charge for the production of both freeware and commercial add-ons (including sceneries,missions,aircraft) subject to the following terms and conditions:-
* You notify Innova Software of the use of FSX KML in your add-on
* You give Innova Software a free copy of your add-on (and any updates)
* In your readme file you say that FSX KML was used to help with the production of your add-on
* The copyright and any intellectual property relating to the FSX KML software shall remain the property of Innova Software
* LIMITED WARRANTY - INNOVA SOFTWARE SHALL NOT BE RESPONSIBLE IN TORT OR IN CONTRACT FOR ANY LOSS OR DAMAGE HOWSOEVER CAUSED TO THE PROPERTY OR PERSON OF YOURSELF OR ANY THIRD PARTY AS A RESULT OF ANY DEFECT IN THE SOFTWARE WHETHER PATENT OR LATENT OR AS A RESULT OF ANY FAULT, NEGLIGENCE, WRONGFUL ACT OR OMISSION OF INNOVA SOFTWARE OR ANY OF ITS SERVANTS, EMPLOYEES, CONTRACTS AND AGENTS, AND YOU INDEMNIFY INNOVA SOFTWARE AGAINST ANY CLAIMS MADE AGAINST IT BY ANY THIRD PARTY ARISING OUT OF ANY SUCH DEFAULT OR FAULT, NEGLIGENCE, WRONGFUL ACT OR OMISSION AND IN NO EVENT SHALL INNOVA SOFTWARE BE LIABLE FOR ANY CLAIMS OR DAMAGES INCLUDING, BUT NOT LIMITED TO CLAIMS OF FAULTY DESIGN, NEGLIGENT OR MISLEADING ADVICE, DAMAGES ARISING FROM LOSS OR USE OF THE SOFTWARE AND/OR SUPPLY OF SERVICES; AND ANY INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES OR INJURY TO ANY PERSON, CORPORATION OR OTHER ENTITY BY REASON OF THE PROVISION OF THE SOFTWARE AND/OR PROVISION OF SERVICES PURSUANT TO THESE TERMS AND CONDITIONS

Developers can email acceptance of these terms and conditions to fsx_kml@innovasoftware.com.

== Release History ==

=== v1.00 Beta - 19th 0ct 2006 ===

This is first beta release of FSX KML

=== v1.01 Beta - 19th 0ct 2006 ===

Issues resolved:-
* Fixed error with FSX_KML_TAGS.XML file not found

=== v1.02 Beta - 21st 0ct 2006 ===

Issues resolved:-
* Fixed error reading polygon/poylines. FSX KML could sometimes insert an erroneous point of 0,0

=== v1.03 Beta - 28th 0ct 2006 ===

New features and issues resolved:-
* Better handle tags in description field. Be less strict about "whitespace" and cr/lf
* Better handle international settings for decimals
* Add more excludes to fsx_kml_tags.xml (see tags starting with "exclude__")
* Add support for moving kml items up/down
* Add support for moving kml items via drag drop
* Add support for creating new kml folder
* Create shapes in order they appear in the KML
* Assign UUID (starting at 1) to each shape in the KML based on its order in the KML

Known issues (Features not implemented in this release):-
* Freeway tags (moving traffic) - in v1.03 you must manually edit the FW .DBF file to set traffic density and direction

=== v1.04 Beta - 20th Jan 2007 ===

New features and issues resolved:-

* Use INI file (FSX_KML.INI) to remember settings including list of KML files and FSX folder settings
* Allow multi select of KML files in Add KML file dialog
* Display points for selected polygon/polyline
* Add REVERSE POINTS button to allow direction of polygon/polyline to be reversed
* Add POLYGONHOLE tag to support "holes" in polygons, eg for making islands in rivers
* Add LEGACY_LANDWATERMASK_WATER_NOFLATTEN tag for water polygons that "cling" to mesh
* Default freeway traffic to one lane of traffic

=== v1.05 Beta - 21st Jan 2007 ===

New features and issues resolved:-

* Added "Automatically Reverse Points In Polygon Holes" build option. This option will auto reverse points for polygon holes when creating the shape file. Apparently Google Earth always writes polygons in a clockwise fashion to the KML file irrespective of which way they are actually drawn in Google Earth. This option simplifies the creation of polygon holes because you no longer need to manually reverse point order in FSX KML. Option is on by default.
* Added "Output Folder" build option. This lets you specify the folder where files are written during the build process
* Fixed error when loading the saved list of KML files and a KML file can longer be found.

=== v1.05.1 Beta - 21st Jan 2007 ===

Issues resolved:-

* Fixed bug where directory would not be changed prior to running the RUN_SDK_TOOLS batch file

=== v1.06 Beta - 14th Apr 2007 ===

New features:-

* Added grid to allow manual editing of polygon/polyline points (longitude,latitude,elevation)
* Added button for setting all points in polygon/polyline to a specific elevation
* Added support for tag parameters (eg freeway traffic data and hydro poly slopeX/Y)
* Added option to save backups to backup subdirectory (on by default).
* Added XML tab to show XML for highlighted node
* Remember window size and position

Issues resolved:-

* Changed tag name of "Park" to "LandClassPoly" since landclass polys can be used for more than just parks! Existing "Park" tags are automatically renamed to "LandClassPoly"
* Handle extra '.' in filenames

=== v1.07 Beta - 25th Apr 2007 ===

New features:-

* Added "Shape" tab with support for shape viewing. Select single (or multiple) polygon/polylines to see its shape. Selecting a folder will show all shapes in that folder and any sub folders.
* Added "Select All" function (Ctrl A) to select all polylines/polygons
* Added "New" button to Vertices form to insert vertice.
* Added "Copy" button to Vertices form to copy the selected vertice.
* Added "Delete" button to Vertices form to delete selected vertice.
* Added "Move Up" and "Move Down" button to Vertices form to move selected vertice up or down in list.
* Added Options menu to main form. Moved "Save Backups" to this menu
* Added "Remember Window Position and Size" to the options menu

Issues resolved:-

* Updated the "About" form to credit the 3rd party development libraries used (eg Shapelib)
* Fixed misplaced longitude and latitude labels on vertice grid

=== v1.08 Beta - 18th May 2007 ===

New features:-

* Add BGLCOMP support for placing of FSX library objects along polyline. The use of "Variance" parameters below helps create more naturalistic looking scenery by applying random variance to object positioning. Support the following parameters:-
** Altitude AGL or MSL
** Altitude variance - Random variance in meters applied to alitude (use 0 for no variance)
** Pitch (0 - 360)
** Pitch variance - Random variance in degrees (0 - 180) applied to pitch (use 0 for no variance)
** Bank (0 - 360)
** Bank variance - Random variance in degrees (0 - 180) applied to bank (use 0 for no variance)
** HeadingType
*** Track - Heading of each object follows the direction of each polyline segment
*** Fixed - Heading of all objects is specified by Heading parameter
*** Random - Heading is random for each object
*** Elevation - Heading for each object is specified by elevation of associated polyline vertice
** Heading (0 - 360) - Used when HeadingType = Fixed
** Heading variance - Random variance in degrees (0 - 180) applied to heading (use 0 for no variance)
** Scale - Scale multiply of object (defaults to 1.0)
** ScaleVariance - Random variance in scale to apply to objects. (use 0 for no variance)
** ImageComplexity - VerySparse, Sparse, Normal, Dense, VeryDense, ExtremelyDense
* FSX_KML_Tags tab - Add tags for all default FSX scenery library objects
* Build tab - Add button for setting BGLComp SDK path
* Build tab - Add "Open" button for output folder path to open Windows Explorer on that folder

Issues resolved:-

* Fixed issue with copy button

=== v1.09 Beta - 23rd June 2007 ===

New features:-

* Added BGLCOMP support for scenery exclusion rectangles ("ExclusionRectangle" tag). The exclusion rectangle will be defined by the "bounding" rectangle of the polyline/polygon. Supports the following parameters
** ExcludeAllObjects
** ExcludeBeaconObjects
** ExcludeEffectObjects
** ExcludeGenericBuildingObjects
** ExcludeLibraryObjects
** ExcludeTaxiwaySignObjects
** ExcludeTriggerObjects
** ExcludeWindsockObjects
** ImageComplexity - VerySparse, Sparse, Normal, Dense, VeryDense, ExtremelyDense
* Added BGLCOMP support for Extrusion Bridges ("ExtrusionBridge" tag). Draw a polyline and tag it with "ExclusionBridge", then use the vertice editor to set the height of each bridge segment.
* Added "Change to" button on the Vertice Editor to change shape type from polygon to polyline and vice versa
* Enhanced polygons holes so that if a polygon cannot be found in the same folder as polygon hole ("polygon folder") then the parent folder is searched for the first polygon preceding the polygon folder. This makes it possible to better organize a project by placing polygon holes (i.e islands) in a sub folder and still have them associated with a water polygon in a parent folder

=== v1.10 Beta - 19th August 2007 ===

New features:-

* Land class tiles
* Water class tiles

== Development Roadmap ==

The following features are planned for upcoming releases:-

=== Future releases ===
* Update this manual :)
* Add 10 minute autosave
* Add following params to BGLCOMP support:-
** Heading Type
*** FixedTrack - Heading of all objects is fixed to the direction of first polyline segment
** Divergence - Random divergence (in meters) from vertice. Applied in direction which is perpendicular to direction of polyline segment (use 0 for no variance)
* Add "AutoPolygonHole" to polygon properties sheet. This allows a polygon hole to be automatically created in the shape of the polygon, and removes the need manually create a hole (by copying and tagging as hole)
* Fix - Ensure lon/lat uses '.' and not ','
* FSX_KML_Tags tab - Add support for tag groups
* Add BGLCOMP support for Tag Groups. Tag grouping allows the scenery designer to group together similar scenery library objects into a single group. For example, when populating a car park the designer could use a tag group containing a variety of car models. This would result in car models being chosen at random from the tag group.
* Add shape viewer to Vertice Editor form and have it refresh as vertices are edited.
* Add "Fly to" button to Vertices Editor form to move FSX aircraft to the selected vertice
* Add "Paste Aircraft pos" button to Vertices Editor form to paste the current location of aircraft (longtitude, latitude, and optionally altitude) into the list of Vertices.
* Export - Ability to export selected polygons/polylines to a CSV file, with option for long/lat/elevation ordering
* Scenery Placer - Add support for dynamically previewing scenery objects while FSX is running. This allows very precise and interactive control over the objects placement and orientation without the need to build a BGL and reload FSX.
* Placing FSX library objects inside a polygon. Allow number of objects and elevation to be specified. Objects will be distributed randomly within the polygon. This can be used to populate livestock, wildlife, boats/ships in harbors, people on beaches, birds, hot air balloons etc
* FSX_KML_Tags tab - Texture preview for land class polygons and tiles tags
* FSX_KML_Tags tab - Scenery object preview for default FSX scenery objects
* Ability to inject a QMID 11 grid into the KML to aid with visualization of exclusion areas
* New, Open and Save project buttons to support multiple projects.
* "Check for Update" menu option to check online for updates.

* If possible conditional display of FSX scenery library objects based on various triggers such as date/time, weather conditions and probability factor. For example, this would allow harbors to be populated with pleasure craft on sunny warm days, but not at night or in cold weather. Would allow forest fires to be generated in hot, windy conditions.
* If possible ability to animate FSX scenery library objects along a polyline
* "Photo scenery" ground textures
* Flight plan generation along polyline


== Software by this author ==
[http://fsdeveloper.com/wiki/index.php?title=FSX_KML FSX_KML]

[http://fsdeveloper.com/wiki/index.php?title=FSX_Photoscene FSX_PhotoScene]

[http://fsdeveloper.com/wiki/index.php?title=SRTM_To_BGL SRTM_To_BGL]

[[Category:Manuals]]
[[Category:Tools]]
[[category:Scenery_Design]]

Converting AI aircraft to FSX with Model Converter X

2014-03-20T18:11:53Z

Heretic: Created page with "{{Infobox-Applicable-FSVersion | P3D = true | FSXA = true | FSX = true | FS2004 = false | FS2002 = false | FS2000 = false | FS98 = false }} This article gives a short overvie..."

{{Infobox-Applicable-FSVersion
| P3D = true
| FSXA = true
| FSX = true
| FS2004 = false
| FS2002 = false
| FS2000 = false
| FS98 = false
}}

This article gives a short overview of the requirements and information about the conversion process. It is by no means a full blown tutorial and users are encouraged (and required) to do some research on their own if they do not know their way around Model Converter X, the SDK or else.

= Introduction =

Most AI aircraft were designed and compiled for FS9. They work fine in FSX, but use the rather inefficient compatibility rendering scheme which prevents their usage in DX10 mode and poses a heavier drain on computer resources. 
The available options to alleviate this problem would be the purchase of a payware AI traffic package containing FSX native models or only flying in DX9 rendering mode or the conversion of AI models with [[ModelConverterX]]. 
The first option is nod valid if the user uses self-assembled AI traffic or does not wish to spend any money. The second option is not valid if the user wishes to experience FSX in DX10 mode. This basically only leaves the third option, which is the subject of this article and possesses the following advantages and disadvantages:

=== Advantages ===
* Does not require any monetary investments.
* A great way to kill a lot time.
* Improved framerates at busy airports.
* AI traffic can be used in DX10 mode.
* Basic animations are retained.
* LODs still work.

=== Disadvantages ===
* Parts with visibility conditions attached to them, e.g. prop disks will be lost in the conversion process. (This is a current ModelConverterX limitation.)
* Animations will sometimes not play properly in FSX.
* Lightmaps from repaints made for FS9 are not properly displayed in FSX.
* Models using custom XML coded animations will lose said animations unless you replace them with a FSX standard animation or some custom code.
* The MCX export will screw up the bounding and radius boxes within the model file, so they'll have to be fixed by the user.
* Conversion of a lot of models is '''very''' time intensive. Depending on available spare time and amount of models installed, it will take anywhere from one to two days to several weeks.

The value of a slight gain in performance at big airports versus the incurred disadvantages is left to be decided individually.
 
 
= Licensing and disclaimer =

Before continuing on, it has to be noted that '''this is an experimental procedure''' so no warranty of any kind is given. 
More importantly, converting AI models from other authors may only be done for personal usage (or not at all, depending on how strict the license is interpreted on an individual basis). 
In any case: '''Do not distribute converted models.'''
They are for '''personal use only'''!
 
 
= Requirements =

*A development release of [http://www.scenerydesign.org/development-releases/ ModelConverterX]
*An installation of the [http://www.fsdeveloper.com/wiki/index.php?title=SDK_Installation_%28FSX%29 FSX SP2/Acc SDK]
*A release of [http://www.scenerydesign.org/raditor/ RADItor]
 
= Basics =

Some basic acquaintance with ModelConverterX, especially its animation editor, is required. It is also strongly advised that users export an aircraft model with a name different to the original model (i.e. ''B737-200X'' instead of ''B737-200'') and adapt the model.cfg file accordingly. This allows a quick reversal to the original model in case the conversation produces an undesirable result in FSX.
 
=== AI Aaardvark ===
Users wishing to convert their freeware AI traffic may start out with AI Aardvark's FSX native models, especially those with [http://www.world-of-ai.com/ World Of AI] packages installed. 
The models are available at Avsim or Flightsim in a file called ''aiafsx01.zip''.
 
'''The readme and .pdf contained in the download also explain some of the disadvantages mentioned in the last section in a bit more detail, so reading it is highly recommended!'''
 
=== Workflow ===

The basic workflow for a conversion is the following:

# Open the model with ModelConverterX
# Launch MCX' animation editor and replace animations with ones read from the modeldef.xml in the SDK
# Export model as a FSX native model
#* (Open model in MCX and check it)
# Adapt model.cfg (see "Basics" above)
# Open exported model file with RADItor and assign model radius and bounding box values
It is of course possible to adapt said workflow to individual needs.
 
 
= Tips & Hints =

These are some tips and hints to facilitate the conversion process or create a better understanding of disadvantages.

=== Auto-assigning animations upon export ===

ModelConverterX allows auto-assigning animations during export based on animation tag name in the modeldef.xml file. If there's an animation named ''reverser0'' in MCX, MCX' exporter will look for said animation in the modeldef.xml during export. If an animation named ''reverser0'' is found, the model will be compiled using said animation.
This can be used to facilitate the compilation of aircraft by creating modeldef.xml entries for the most common animations.

A collection of animation codes for '''jet aircraft''' is available [http://www.fsdeveloper.com/forum/threads/fs9-fsx-aircraft-model-conversion-an-experiment.427512/#post-657654 here]. The code can be copied and pasted into the modeldef.xml file '''above''' the closing ''</ModelInfo>'' tag at its end. 
Propeller aircraft require an extra step for the propellers by manually assigning ''prop_blurred'' or ''prop_slow'' animations for the props.

=== Unknown animations ===

Many models come with animations controlled by custom XML code, mostly for slats and flaps. Depending on the laziness of the end user, it is perfectly possible to preserve said animations by writing custom animation code or simply assigning the default animations to the parts in question. 
The animation editor in MCX makes it possible to isolate animations piece by piece by unchecking known ones and moving the animation slider while observing the rendering window. Albeit tedious, it is a perfectly fine method to identify a good part of 'unknown' animations. 
It should be kept in kind though, that some animations are dependent on each other to display properly, such as animated flap canoes and flaps. 
If an animation can not be idnetified or is deemed redundant or unnecessary, it is possible to discard it from the model by using the ''Fix Animation'' button.

=== Handling visibility tag incompatibility ===

ModelConverter's (current) visibility tag incompatibility currently affects the display of ground equipment (if present in the model file) and, more importantly, prop disks and possibly rolling wheels. 
Currently, the only ways to alleviate this drawback are either a full blown export and modification of the model in GMax as described [http://www.fsdeveloper.com/forum/threads/fs9-fsx-aircraft-model-conversion-an-experiment.427512/page-3#post-665407 here] or a simply assigning ''prop_slow'' or ''prop_blurred'' animation tags to the propeller model.
Same applies to the wheels.

=== Bounding box and model radius ===

Editing the bounding box and model radius of each converted model is '''mandatory''', as MCX does not include realistic values for these upon exporting. Using RADItor, the user can set the values to his/her liking. 
The model radius determines the parking spot usage of a model. If a parking spot with a radius of 20m is used in an AFX (airport layout) file, a model with a radius of 25m will not be assigned to use said spot by FSX. A value of half the wingspan of an aircraft plus 1 or 2m usually works for the radius, but users are encouraged to use values that work best for them. 
The bounding box is generally used to determine a 'crash into aircraft' event. If crashes are enabled in FSX and an AI aircraft possesses a bounding box of several kilometers length, width and height, the user will receive a 'Crash!' event by taxiiing around an airport. It is therefor advisable to set said bounding box to decently realistic values. 
''X-values'' are used for the wingspan and can thus be set to half the wingspan each. 
''Y-values'' cobnstitute the fuselage length. Dependiung on where the original model designer placed the model origin, these values will be, in most cases not entirely symmetrical. For simplicity's sake, however, it can be assumed that the model origin is present at half the fuselage length and thus, values for half the fuselage length can be used to set the bounding box in this axis. 
''Z-Values'' determine the height of the bounding box. As the model origin is most likely '''not''' located at ground level with landing gear extended, a generic ratio has to be applied for this value. Something along the lines of 'one third of the aircraft height' works for the negative z-value while the remaining two thirds can be applied to the positive value. The stance of the aircraft model on the ground is '''not''' affected by this as it is entirely determined by the 'contact points' in the aircraft.cfg. 
As usual, it is of course possible to use more elaborate methods for defining the bounding box and model radius.

=== Tweaked animations ===

Tweaked animations for the rudder and the nose wheel can be found [http://www.fsdeveloper.com/forum/threads/fs9-fsx-aircraft-model-conversion-an-experiment.427512/page-3#post-662497 here]. It has to be noted that these have to be assigned manually unless the names are edited to enable them for automatic assignment (see 'Auto Assigning' above). In the latter case, it has to be made sure that the tweaked animations are not conflicting with the ones present in the collection of auto-assignable animations (by deleting the old ones).

=== Possible night texture fix ===

An untested fix for the overly bright night textures in FSX can possibly be achieved with MCX' material editor. While the .pdf included in AI Aardvark's model package (mentioned above) shows a fix based on individual repaints, it is very, very time consuming to apply. Setting the 'Emissive Properties' in the editor to ''Multiplay Blend'' or ''User Multiply Blend'' might tell FSX to revert back to the lightmap behaviour from FS9.
Users are encouraged to test this.

=== Full blown model edits in GMax ===

By using ModelConverterX' 'export to .3DS' export function, AI models can also be imported into GMax, as outlined for scenery models [http://www.fsdeveloper.com/forum/threads/fs9-fsx-aircraft-model-conversion-an-experiment.427512/page-3#post-665407 here]. 
The model will, however, be imported with temporary materials and will be missing all of its mesh smoothing and all of its animations, including keyframes. 
Despite the extra work required, it enables the user to recreate the prop disks and other parts requiring visibility conditions.

= References =

Reference thread:
http://www.fsdeveloper.com/forum/threads/fs9-fsx-aircraft-model-conversion-an-experiment.427512/

[[category:Living World]]
[[Category:Aircraft Design]]

Makemdl

2014-02-18T14:49:41Z

Heretic:

{{Infobox-Applicable-FSVersion
| P3D = false
| FSXA = false
| FSX = false
| FS2004 = true
| FS2002 = true
| FS2000 = false
| FS98 = false
}}

MakeMDL is the primary compiler for objects created for Microsoft's Flight Simulator 9

In its latest iteration, available in the MakeMDL SDK [http://download.microsoft.com/download/1/1/8/1181a250-ac2c-43fa-b35b-bfd7b87934ad/makemdl_sdk_setup.exe] for FS9, it supports input commands via a file named "makemdl.cfg".
Normally, this file is located in the same folder in which MakeMDL.exe resides, e.g. "C:\gmax\gamepacks\fs2004\plugins"
 
== Sample MakeMDL.cfg ==

[Settings] 
LastDir= 
SaveDir=''C:\gmax\GAMEPA~1\FS2004\plugins'' 

[Options] 
Debug=1 
ViewLog=0 
KeepErrorLog=1 
Keep=0 
I8=1 
I=0 
FullMat=1 
Deffallback=1 
WeldPoints=0 
Optimize=0 
Flatten=0 
NoAnimate=0 
HasReflectMap=1 
HasNightMap=0 
HasLightMap=1 
HasDamageMap=0 
NegateZ=1 
NoLeftToRight=0 
SwapBH=0 
Vis=0 
Crash=0 
XML=1 
 
== Makemdl.cfg options explained ==

Of special interest to avid modellers for FS9 are the "Debug", "KeepErrorLog", "WeldPoints", "Optimize" and "Flatten" settings. 
;Debug: Set to "1" (no quote marks) to enable debug functionality 
;ViewLog: Automatically opens the log file after compilation if set to "1" 
;KeepErrorLog: Does not delete the log file if set to "1"; useful for finding erroneous parts or animations 
;Keep: Does not delete temporary files created during compilation if set to "1" 
;I8: ??? 
;I: ??? 
;FullMat: ??? 
;Deffallback: ??? 
 
The next three settings can be a cure to the 4mm vertex weld issue otherwise present for FS9 models (very notable and annoying in virtual cockpits)! 

;WeldPoints: Disable vertex welding when set to "0". 
;Optimize: Optimizes code (grouping of parts with same materials and removing unnecessary translate/rotate animation tags) 
;Flatten: Set to "0" to disable flattening of the hierarchy tree 
;NoAnimate: Does not parse animations during compilation if set to "1" 
;HasReflectMap: Set to "1" to enable reflectivity for the model. Make sure to put a "_t" suffix into the texture's file name, e.g. "fuselage_t.bmp" and make sure "Reflections" is enabled in FS9's "display" menu.
;HasNightMap: Enables use of auto-enabled night textures ("_lm" suffix, i.e. "tower_lm.bmp") if set to "1". You won't need to fill the "self-illumination" slot of the material in GMax. Useful for scenery design!
;HasLightMap: Enables use of self-illumination night textures ("_l" suffix, i.e. "fuselage_l.bmp") if set to "1". You won't need to fill the "self-illumination" slot of the material in GMax. Useful for aircraft design!
;HasDamageMap: Enables damage textures if set to "1". Not needed for FS9.
;NegateZ: If your object appears upside down in FS9, set this to "1".
;NoLeftToRight: Set this to "1" to invert the left/right coordinate axis
;SwapBH: When set to "1", the bank and heading axis of the model will be swapped
;Vis: ???
;Crash: Set to "1" to enable crash detection when compiling a scenery object.
;XML: Produces a sample placement XML file for a scenery object when set to "1"

[[category:Modeling]]

Rendering with GMax

2013-08-02T03:34:05Z

Heretic:

{{Infobox-Applicable-FSVersion
| P3D2 = true
| P3D = true
| FSXI = true
| FSXA = true
| FSX = true
| FS2004 = true
| FS2002 = true
| XP10 = unknown
| XP9 = unknown
}}
One of the advantages of using 3D Studio Max over GMax has always been the capability of the former to perform a quick or full rendering of the model one is working on. 
Yet, with the right plugins and a bit of effort, one can add such a rendering function to GMax. 
 
This article gives instructions on how to set up and the basic usage of such a plugin.

=== Prerequisites ===
* An installation of GMax 1.2 (installed gamepack does not matter)
 
=== Download ===
[http://www.ppmsite.com/forum/download.php?id=44398&sid=5f064355c02c38dcb5cba130c15354fb Here]
 
=== Installation of the rendering plugin ===
# Unzip the downloaded plugin
# Rername the folder "RenderSuite" or similar
# Running RenderSuiteInstall.exe from the folder and follow the instructions
# Delete the .bat file the installer creates on your desktop
# Inside your main GMax Folder, create an empty text file
# Put these lines inside said text file:
#*For FS9:
#:echo on
#:cd %cd%\RenderSuite 
#:start GmaxRender.exe 
#:cd.. 
#:start gmax.exe -p gamepacks\FS2004\plugin.ini
#: 
#*For FSX:
#:echo on
#:cd %cd%\RenderSuite 
#:start GmaxRender.exe 
#:cd.. 
#:start gmax.exe -i gamepacks\FSX_GMaxGamepack\gmax.ini -p gamepacks\FSX_GMaxGamepack\plugin.ini
#: 
# Save the text file as "GMax with Render.bat" or similar. When asked to change file type, say "Yes"
#* Create a shortcut to the batch file for the desktop, if so desired
# Start GMax with the .bat file or the shortcut leading to it
# There should be a "Rendering" entry in the main menu bar. If not, refer to the [[#Troubleshooting | troubleshooting]] section
 
=== Using the RenderSuite ===
General setup and usage of the render suite is fairly easy as outlined in the following general procedure.
 
 
:'''Warning: FSX Materials'''
:The RenderingSuite (or the contained YAFRAY render engine to be more specific) can't use FSX materials, so either:
:*don't use RenderSuite for rendering FSX models in GMax or
:* use RenderSuite for models in very early stages, i.e. without textures or temporary textures, etc... or
:* set up standard materials with textures and then run the [http://www.fsdeveloper.com/forum/showpost.php?p=624227&postcount=15 "Select By Materials" script] to mass assign the render-friendly textures to your scene objects
 
* Put some lights into your scene. Spots, Omnis, anything that will properly light the object. Default properties are okay for a start
* Put a camera into your scene. Free or Target
* Adjust the angle and position of the camera, so that the desired objects are rougly in focus
** Make sure to tick "Manual Clipping" in the camera options!
*** For interior spaces, a 15mm lens and 0.1m near clipping treshhold works well
* Click any viewport's name, then go to "Views" and select "Camera01". The viewport should now show what the camera is seeing
* The custom camera can be controlled like the default camera in the "Perspective" or "User" viewport mode. Fine tune, if needed
* When ready, select "Rendering" from the menu
* Select any of the two clients
** YAGMAX seems to work best for the author
** RenderSuite output an untextured model and requires that any scene object has a material applied
* Rendering options should be left at default for now
* Make sure that the active viewport is set to "Camera01"
* Click YAFRAY Render
** Note: Depending on the number of objects and polygons visible in the scene and selected rendering resolution, the following can take some time
* Wait. There should be activity in the listener window on the bottom left of GMax' main screen
* After a moment, a window labeled "RenderSuite" should pop up, in which the rendered content of the "Camera01" viewport is slowly drawn
** In case no window pops up, refer to the second entry in the [[#Troubleshooting | troubleshooting]] section
* In case of a pleasing rendering result, clicking the disk icon will save the output image in Windows Bitmap format to the "RenderSuite" folder
* This is the basic process. Plaing with the options for the camera, lights and YAFRAY can yield better results. The worst that can happen is a weird looking or empty render image
 
=== Example Render Images ===
[[image:732.jpg | thumb | none | Boeing 737-200 rendered with RenderSuite's YAGMAX mode]]
 
=== Troubleshooting ===
# No "Rendering" menu
#* Redownload RenderSuite, if the .zip file is not present anymore and extract the "Maxmenus.mnu" file from it
#* Copy the .mnu file to "Gmax\RenderSuite"
#* While in GMax, go to "Customize", then "LoadCustomUI scheme"
#* Browse to the "RenderSuite" folder, then select "Menu File (.mnu)" from the dropdown box above "Open"
#* Select the "Maxmenus.mnu" file and click "Open"
#* You should now have a "Rendering" menu item. if not, restart GMax or repeat the procedure
#: 
# No rendering window after clicking "Render"
#* Open Windows task manager (CTRL+Shift+ESC)
#* Select "GMaxRender.exe" in the process list
#* Click "End Process"
#* Browse to your RenderSuite folder in Windows Explorer
#* Start GMaxRender.exe
#* The rendering window should now pop up and start to display the rendered image. If not, restart the rendering process
#: 
# YAFRAY crashes upon rendering
#* Don't use FSX materials
#* Make sure to hide any objects not visible in the render image, such as those behind the camera
#: 
# When using RenderSuite for rendering, it displays an error about empty objects and/oror objects without materials
#* Assign temporary materials to the object(s) in question. They won't need to have a diffuse map
#* Hide any dummies from the scene
#: 
# Untextured objects on the render image
#* Don't use FSX materials, use standard ones instead

Rendering with GMax

2013-08-02T03:18:06Z

Heretic: /* Troubleshooting */

{{Infobox-Applicable-FSVersion
| P3D2 = false
| P3D = false
| FSXI = false
| FSXA = false
| FSX = false
| FS2004 = true
| FS2002 = true
| XP10 = unknown
| XP9 = unknown
}}
One of the advantages of using 3D Studio Max over GMax has always been the capability of the former to perform a quick or full rendering of the model one is working on. 
Yet, with the right plugins and a bit of effort, one can add such a rendering function to GMax. 
 
This article gives instructions on how to set up and the basic usage of such a plugin.

=== Prerequisites ===
* An installation of GMax 1.2 (installed gamepack does not matter)
* A GMax model with '''standard''' materials, i.e. '''*no* FSX materials'''.
**Using FSX Materials *will* result in untextured models!

=== Download ===
[http://www.ppmsite.com/forum/download.php?id=44398&sid=5f064355c02c38dcb5cba130c15354fb Here]
 
=== Installation of the rendering plugin ===
# Unzip the downloaded plugin
# Rername the folder "RenderSuite" or similar
# Running RenderSuiteInstall.exe from the folder and follow the instructions
# Delete the .bat file the installer creates on your desktop
# Inside your main GMax Folder, create an empty text file
# Put these lines inside said text file:
#*For FS9:
#:echo on
#:cd %cd%\RenderSuite 
#:start GmaxRender.exe 
#:cd.. 
#:start gmax.exe -p gamepacks\FS2004\plugin.ini
#: 
# Save the text file as "GMax with Render.bat" or similar. When asked to change file type, say "Yes"
#* Create a shortcut to the batch file for the desktop, if so desired
# Start GMax with the .bat file or the shortcut leading to it
# There should be a "Rendering" entry in the main menu bar. If not, refer to the [[#Troubleshooting | troubleshooting]] section
 
=== Using the RenderSuite ===
General usage of the render suite is as follows.
 
* Put some lights into your scene. Spots, Omnis, anything that will properly light the object. Default properties are okay for a start
* Put a camera into your scene. Free or Target
* Adjust the angle and position of the camera, so that the desired objects are rougly in focus
** Make sure to tick "Manual Clipping" in the camera options!
*** For interior spaces, a 15mm lens and 0.1m near clipping treshhold works well
* Click any viewport's name, then go to "Views" and select "Camera01". The viewport should now show what the camera is seeing
* The custom camera can be controlled like the default camera in the "Perspective" or "User" viewport mode. Fine tune, if needed
* When ready, select "Rendering" from the menu
* Select any of the two clients
** YAGMAX seems to work best for the author
** RenderSuite output an untextured model and requires that any scene object has a material applied
* Rendering options should be left at default for now
* Make sure that the active viewport is set to "Camera01"
* Click YAFRAY Render
** Note: Depending on the number of objects and polygons visible in the scene and selected rendering resolution, the following can take some time
* Wait. There should be activity in the listener window on the bottom left of GMax' main screen
* After a moment, a window labeled "RenderSuite" should pop up, in which the rendered content of the "Camera01" viewport is slowly drawn
** In case no window pops up, refer to the second entry in the [[#Troubleshooting | troubleshooting]] section
* In case of a pleasing rendering result, clicking the disk icon will save the output image in Windows Bitmap format to the "RenderSuite" folder
* This is the basic process. Plaing with the options for the camera, lights and YAFRAY can yield better results. The worst that can happen is a weird looking or empty render image
 

=== Example Render Images ===

[[image:732.jpg | thumb | none | Boeing 737-200 rendered with RenderSuite's YAGMAX mode]]
[[image:580vc.jpg | thumb | none | Convair 580 cockpit model rendered with RenderSuite's YAGMAX mode]]
 
=== Troubleshooting ===
# No "Rendering" menu
#* Redownload RenderSuite, if the .zip file is not present anymore and extract the "Maxmenus.mnu" file from it
#* Copy the .mnu file to "Gmax\RenderSuite"
#* While in GMax, go to "Customize", then "LoadCustomUI scheme"
#* Browse to the "RenderSuite" folder, then select "Menu File (.mnu)" from the dropdown box above "Open"
#* Select the "Maxmenus.mnu" file and click "Open"
#* You should now have a "Rendering" menu item. if not, restart GMax or repeat the procedure
#: 
# No rendering window after clicking "Render"
#* Open Windows task manager (CTRL+Shift+ESC)
#* Select "GMaxRender.exe" in the process list
#* Click "End Process"
#* Browse to your RenderSuite folder in Windows Explorer
#* Start GMaxRender.exe
#* The rendering window should now pop up and start to display the rendered image. If not, restart the rendering process
#: 
# YAFRAY crashes upon rendering
#* Don't use FSX materials
#* Make sure to hide any objects not visible in the render image, such as those behind the camera
#: 
# When using RenderSuite for rendering, it displays an error about empty objects and/oror objects without materials
#* Assign temporary materials to the object(s) in question. They won't need to have a diffuse map
#* Hide any dummies from the scene
#: 
# Untextured objects on the render image
#* Don't use FSX materials, use standard ones instead

Rendering with GMax

2013-08-02T03:16:49Z

Heretic: /* Troubleshooting */

{{Infobox-Applicable-FSVersion
| P3D2 = false
| P3D = false
| FSXI = false
| FSXA = false
| FSX = false
| FS2004 = true
| FS2002 = true
| XP10 = unknown
| XP9 = unknown
}}
One of the advantages of using 3D Studio Max over GMax has always been the capability of the former to perform a quick or full rendering of the model one is working on. 
Yet, with the right plugins and a bit of effort, one can add such a rendering function to GMax. 
 
This article gives instructions on how to set up and the basic usage of such a plugin.

=== Prerequisites ===
* An installation of GMax 1.2 (installed gamepack does not matter)
* A GMax model with '''standard''' materials, i.e. '''*no* FSX materials'''.
**Using FSX Materials *will* result in untextured models!

=== Download ===
[http://www.ppmsite.com/forum/download.php?id=44398&sid=5f064355c02c38dcb5cba130c15354fb Here]
 
=== Installation of the rendering plugin ===
# Unzip the downloaded plugin
# Rername the folder "RenderSuite" or similar
# Running RenderSuiteInstall.exe from the folder and follow the instructions
# Delete the .bat file the installer creates on your desktop
# Inside your main GMax Folder, create an empty text file
# Put these lines inside said text file:
#*For FS9:
#:echo on
#:cd %cd%\RenderSuite 
#:start GmaxRender.exe 
#:cd.. 
#:start gmax.exe -p gamepacks\FS2004\plugin.ini
#: 
# Save the text file as "GMax with Render.bat" or similar. When asked to change file type, say "Yes"
#* Create a shortcut to the batch file for the desktop, if so desired
# Start GMax with the .bat file or the shortcut leading to it
# There should be a "Rendering" entry in the main menu bar. If not, refer to the [[#Troubleshooting | troubleshooting]] section
 
=== Using the RenderSuite ===
General usage of the render suite is as follows.
 
* Put some lights into your scene. Spots, Omnis, anything that will properly light the object. Default properties are okay for a start
* Put a camera into your scene. Free or Target
* Adjust the angle and position of the camera, so that the desired objects are rougly in focus
** Make sure to tick "Manual Clipping" in the camera options!
*** For interior spaces, a 15mm lens and 0.1m near clipping treshhold works well
* Click any viewport's name, then go to "Views" and select "Camera01". The viewport should now show what the camera is seeing
* The custom camera can be controlled like the default camera in the "Perspective" or "User" viewport mode. Fine tune, if needed
* When ready, select "Rendering" from the menu
* Select any of the two clients
** YAGMAX seems to work best for the author
** RenderSuite output an untextured model and requires that any scene object has a material applied
* Rendering options should be left at default for now
* Make sure that the active viewport is set to "Camera01"
* Click YAFRAY Render
** Note: Depending on the number of objects and polygons visible in the scene and selected rendering resolution, the following can take some time
* Wait. There should be activity in the listener window on the bottom left of GMax' main screen
* After a moment, a window labeled "RenderSuite" should pop up, in which the rendered content of the "Camera01" viewport is slowly drawn
** In case no window pops up, refer to the second entry in the [[#Troubleshooting | troubleshooting]] section
* In case of a pleasing rendering result, clicking the disk icon will save the output image in Windows Bitmap format to the "RenderSuite" folder
* This is the basic process. Plaing with the options for the camera, lights and YAFRAY can yield better results. The worst that can happen is a weird looking or empty render image
 

=== Example Render Images ===

[[image:732.jpg | thumb | none | Boeing 737-200 rendered with RenderSuite's YAGMAX mode]]
[[image:580vc.jpg | thumb | none | Convair 580 cockpit model rendered with RenderSuite's YAGMAX mode]]
 
=== Troubleshooting ===
# No "Rendering" menu
#* Redownload RenderSuite, if the .zip file is not present anymore and extract the "Maxmenus.mnu" file from it
#* Copy the .mnu file to "Gmax\RenderSuite"
#* While in GMax, go to "Customize", then "LoadCustomUI scheme"
#* Browse to the "RenderSuite" folder, then select "Menu File (.mnu)" from the dropdown box above "Open"
#* Select the "Maxmenus.mnu" file and click "Open"
#* You should now have a "Rendering" menu item. if not, restart GMax or repeat the procedure
#: 
# No rendering window after clicking "Render"
#* Open Windows task manager (CTRL+Shift+ESC)
#* Select "GMaxRender.exe" in the process list
#* Click "End Process"
#* Browse to your RenderSuite folder in Windows Explorer
#* Start GMaxRender.exe
#* The rendering window should now pop up and start to display the rendered image. If not, restart the rendering process
#: 
# YAFRAY crashes upon rendering
#* This might be an overload error with very large meshes
#* Make sure to hide any objects not visible in the render image, such as those behind the camera
#: 
# When using RenderSuite for rendering, it displays an error about empty objects and/oror objects without materials
#* Assign temporary materials to the object(s) in question. They won't need to have a diffuse map
#* Hide any dummies from the scene
#: 
# Untextured objects on the render image
#* Don't use FSX materials, use standard ones instead

Rendering with GMax

2013-08-02T03:07:32Z

Heretic:

{{Infobox-Applicable-FSVersion
| P3D2 = false
| P3D = false
| FSXI = false
| FSXA = false
| FSX = false
| FS2004 = true
| FS2002 = true
| XP10 = unknown
| XP9 = unknown
}}
One of the advantages of using 3D Studio Max over GMax has always been the capability of the former to perform a quick or full rendering of the model one is working on. 
Yet, with the right plugins and a bit of effort, one can add such a rendering function to GMax. 
 
This article gives instructions on how to set up and the basic usage of such a plugin.

=== Prerequisites ===
* An installation of GMax 1.2 (installed gamepack does not matter)
* A GMax model with '''standard''' materials, i.e. '''*no* FSX materials'''.
**Using FSX Materials *will* result in untextured models!

=== Download ===
[http://www.ppmsite.com/forum/download.php?id=44398&sid=5f064355c02c38dcb5cba130c15354fb Here]
 
=== Installation of the rendering plugin ===
# Unzip the downloaded plugin
# Rername the folder "RenderSuite" or similar
# Running RenderSuiteInstall.exe from the folder and follow the instructions
# Delete the .bat file the installer creates on your desktop
# Inside your main GMax Folder, create an empty text file
# Put these lines inside said text file:
#*For FS9:
#:echo on
#:cd %cd%\RenderSuite 
#:start GmaxRender.exe 
#:cd.. 
#:start gmax.exe -p gamepacks\FS2004\plugin.ini
#: 
# Save the text file as "GMax with Render.bat" or similar. When asked to change file type, say "Yes"
#* Create a shortcut to the batch file for the desktop, if so desired
# Start GMax with the .bat file or the shortcut leading to it
# There should be a "Rendering" entry in the main menu bar. If not, refer to the [[#Troubleshooting | troubleshooting]] section
 
=== Using the RenderSuite ===
General usage of the render suite is as follows.
 
* Put some lights into your scene. Spots, Omnis, anything that will properly light the object. Default properties are okay for a start
* Put a camera into your scene. Free or Target
* Adjust the angle and position of the camera, so that the desired objects are rougly in focus
** Make sure to tick "Manual Clipping" in the camera options!
*** For interior spaces, a 15mm lens and 0.1m near clipping treshhold works well
* Click any viewport's name, then go to "Views" and select "Camera01". The viewport should now show what the camera is seeing
* The custom camera can be controlled like the default camera in the "Perspective" or "User" viewport mode. Fine tune, if needed
* When ready, select "Rendering" from the menu
* Select any of the two clients
** YAGMAX seems to work best for the author
** RenderSuite output an untextured model and requires that any scene object has a material applied
* Rendering options should be left at default for now
* Make sure that the active viewport is set to "Camera01"
* Click YAFRAY Render
** Note: Depending on the number of objects and polygons visible in the scene and selected rendering resolution, the following can take some time
* Wait. There should be activity in the listener window on the bottom left of GMax' main screen
* After a moment, a window labeled "RenderSuite" should pop up, in which the rendered content of the "Camera01" viewport is slowly drawn
** In case no window pops up, refer to the second entry in the [[#Troubleshooting | troubleshooting]] section
* In case of a pleasing rendering result, clicking the disk icon will save the output image in Windows Bitmap format to the "RenderSuite" folder
* This is the basic process. Plaing with the options for the camera, lights and YAFRAY can yield better results. The worst that can happen is a weird looking or empty render image
 

=== Example Render Images ===

[[image:732.jpg | thumb | none | Boeing 737-200 rendered with RenderSuite's YAGMAX mode]]
[[image:580vc.jpg | thumb | none | Convair 580 cockpit model rendered with RenderSuite's YAGMAX mode]]
 
=== Troubleshooting ===
# No "Rendering" menu
#* Redownload RenderSuite, if the .zip file is not present anymore and extract the "Maxmenus.mnu" file from it
#* Copy the .mnu file to "Gmax\RenderSuite"
#* While in GMax, go to "Customize", then "LoadCustomUI scheme"
#* Browse to the "RenderSuite" folder, then select "Menu File (.mnu)" from the dropdown box above "Open"
#* Select the "Maxmenus.mnu" file and click "Open"
#* You should now have a "Rendering" menu item. if not, restart GMax or repeat the procedure
#: 
# No rendering window after clicking "Render"
#* Open Windows task manager (CTRL+Shift+ESC)
#* Select "GMaxRender.exe" in the process list
#* Click "End Process"
#* Browse to your RenderSuite folder in Windows Explorer
#* Start GMaxRender.exe
#* The rendering window should now pop up and start to display the rendered image. If not, restart the rendering process
#: 
# YAFRAY crashes upon rendering
#* This might be an overload error with very large meshes
#* Make sure to hide any objects not visible in the render image, such as those behind the camera
#: 
# When using RenderSuite for rendering, it displays an error about empty objects and/oror objects without materials
#* Assign temporary materials to the object(s) in question. They won't need to have a diffuse map
#* Hide any dummies from the scene
#: 
# Untextured objects on the render image
#* Don't use FSX materials, use a standard one instead

Rendering with GMax

2013-08-02T01:36:02Z

Heretic: /* Troubleshooting */

{{Infobox-Applicable-FSVersion
| P3D2 = true
| P3D = true
| FSXI = true
| FSXA = true
| FSX = true
| FS2004 = true
| FS2002 = true
| XP10 = unknown
| XP9 = unknown
}}
One of the advantages of using 3D Studio Max over GMax has always been the capability of the former to perform a quick or full rendering of the model one is working on. 
Yet, with the right plugins and a bit of effort, one can add such a rendering function to GMax. 
 
This article gives instructions on how to set up and the basic usage of such a plugin.

=== Prerequisites ===
* An installation of GMax 1.2 (installed gamepack does not matter)
* Download GMax Rendering Suite from [http://www.ppmsite.com/forum/download.php?id=44398&sid=5f064355c02c38dcb5cba130c15354fb here]
 
=== Installation of the rendering plugin ===
# Unzip the downloaded plugin
# Rername the folder "RenderSuite" or similar
# Running RenderSuiteInstall.exe from the folder and follow the instructions
# Delete the .bat file the installer creates on your desktop
# Inside your main GMax Folder, create an empty text file
# Put these lines inside said text file:
#*For FS9:
#:echo on
#:cd %cd%\RenderSuite 
#:start GmaxRender.exe 
#:cd.. 
#:start gmax.exe -p gamepacks\FS2004\plugin.ini
#: 
#*For FSX
#:echo on 
#:cd %cd%\RenderSuite 
#:start GmaxRender.exe 
#:cd.. 
#:start gmax.exe -i gamepacks\FSX_GMaxGamepack\gmax.ini -p gamepacks\FSX_GMaxGamepack\plugin.ini
#: 
# Save the text file as "GMax with Render.bat" or similar. When asked to change file type, say "Yes"
#* Create a shortcut to the batch file for the desktop, if so desired
# Start GMax with the .bat file or the shortcut leading to it
# There should be a "Rendering" entry in the main menu bar. If not, refer to the [[#Troubleshooting | troubleshooting]] section
 
=== Using the RenderSuite ===
General usage of the render suite is as follows.
 
* Put some lights into your scene. Spots, Omnis, anything that will properly light the object. Default properties are okay for a start
* Put a camera into your scene. Free or Target
* Adjust the angle and position of the camera, so that the desired objects are rougly in focus
** Make sure to tick "Manual Clipping" in the camera options!
*** For interior spaces, a 15mm lens and 0.1m near clipping treshhold works well
* Click any viewport's name, then go to "Views" and select "Camera01". The viewport should now show what the camera is seeing
* The custom camera can be controlled like the default camera in the "Perspective" or "User" viewport mode. Fine tune, if needed
* When ready, select "Rendering" from the menu
* Select any of the two clients
** YAGMAX seems to work best for the author
** RenderSuite output an untextured model and requires that any scene object has a material applied
* Rendering options should be left at default for now
* Make sure that the active viewport is set to "Camera01"
* Click YAFRAY Render
** Note: Depending on the number of objects and polygons visible in the scene and selected rendering resolution, the following can take some time
* Wait. There should be activity in the listener window on the bottom left of GMax' main screen
* After a moment, a window labeled "RenderSuite" should pop up, in which the rendered content of the "Camera01" viewport is slowly drawn
** In case no window pops up, refer to the second entry in the [[#Troubleshooting | troubleshooting]] section
* In case of a pleasing rendering result, clicking the disk icon will save the output image in Windows Bitmap format to the "RenderSuite" folder
* This is the basic process. Plaing with the options for the camera, lights and YAFRAY can yield better results. The worst that can happen is a weird looking or empty render image
 

=== Example Render Images ===

[[image:732.jpg | thumb | none | Boeing 737-200 rendered with RenderSuite's YAGMAX mode]]
[[image:580vc.jpg | thumb | none | Convair 580 cockpit model rendered with RenderSuite's YAGMAX mode]]
 
=== Troubleshooting ===
# No "Rendering" menu
#* Redownload RenderSuite, if the .zip file is not present anymore and extract the "Maxmenus.mnu" file from it
#* Copy the .mnu file to "Gmax\RenderSuite"
#* While in GMax, go to "Customize", then "LoadCustomUI scheme"
#* Browse to the "RenderSuite" folder, then select "Menu File (.mnu)" from the dropdown box above "Open"
#* Select the "Maxmenus.mnu" file and click "Open"
#* You should now have a "Rendering" menu item. if not, restart GMax or repeat the procedure
#: 
# No rendering window after clicking "Render"
#* Open Windows task manager (CTRL+Shift+ESC)
#* Select "GMaxRender.exe" in the process list
#* Click "End Process"
#* Browse to your RenderSuite folder in Windows Explorer
#* Start GMaxRender.exe
#* The rendering window should now pop up and start to display the rendered image. If not, restart the rendering process
#: 
# YAFRAY crashes upon rendering
#* This might be an overload error with very large meshes
#* Make sure to hide any objects not visible in the render image, such as those behind the camera
#: 
# When using RenderSuite for rendering, it displays an error about empty objects and/oror objects without materials
#* Assign temporary materials to the object(s) in question. They won't need to have a diffuse map
#* Hide any dummies from the scene

Rendering with GMax

2013-08-02T00:49:34Z

Heretic: /* Using the RenderSuite */

{{Infobox-Applicable-FSVersion
| P3D2 = true
| P3D = true
| FSXI = true
| FSXA = true
| FSX = true
| FS2004 = true
| FS2002 = true
| XP10 = unknown
| XP9 = unknown
}}
One of the advantages of using 3D Studio Max over GMax has always been the capability of the former to perform a quick or full rendering of the model one is working on. 
Yet, with the right plugins and a bit of effort, one can add such a rendering function to GMax. 
 
This article gives instructions on how to set up and the basic usage of such a plugin.

=== Prerequisites ===
* An installation of GMax 1.2 (installed gamepack does not matter)
* Download GMax Rendering Suite from [http://www.ppmsite.com/forum/download.php?id=44398&sid=5f064355c02c38dcb5cba130c15354fb here]
 
=== Installation of the rendering plugin ===
# Unzip the downloaded plugin
# Rername the folder "RenderSuite" or similar
# Running RenderSuiteInstall.exe from the folder and follow the instructions
# Delete the .bat file the installer creates on your desktop
# Inside your main GMax Folder, create an empty text file
# Put these lines inside said text file:
#*For FS9:
#:echo on
#:cd %cd%\RenderSuite 
#:start GmaxRender.exe 
#:cd.. 
#:start gmax.exe -p gamepacks\FS2004\plugin.ini
#: 
#*For FSX
#:echo on 
#:cd %cd%\RenderSuite 
#:start GmaxRender.exe 
#:cd.. 
#:start gmax.exe -i gamepacks\FSX_GMaxGamepack\gmax.ini -p gamepacks\FSX_GMaxGamepack\plugin.ini
#: 
# Save the text file as "GMax with Render.bat" or similar. When asked to change file type, say "Yes"
#* Create a shortcut to the batch file for the desktop, if so desired
# Start GMax with the .bat file or the shortcut leading to it
# There should be a "Rendering" entry in the main menu bar. If not, refer to the [[#Troubleshooting | troubleshooting]] section
 
=== Using the RenderSuite ===
General usage of the render suite is as follows.
 
* Put some lights into your scene. Spots, Omnis, anything that will properly light the object. Default properties are okay for a start
* Put a camera into your scene. Free or Target
* Adjust the angle and position of the camera, so that the desired objects are rougly in focus
** Make sure to tick "Manual Clipping" in the camera options!
*** For interior spaces, a 15mm lens and 0.1m near clipping treshhold works well
* Click any viewport's name, then go to "Views" and select "Camera01". The viewport should now show what the camera is seeing
* The custom camera can be controlled like the default camera in the "Perspective" or "User" viewport mode. Fine tune, if needed
* When ready, select "Rendering" from the menu
* Select any of the two clients
** YAGMAX seems to work best for the author
** RenderSuite output an untextured model and requires that any scene object has a material applied
* Rendering options should be left at default for now
* Make sure that the active viewport is set to "Camera01"
* Click YAFRAY Render
** Note: Depending on the number of objects and polygons visible in the scene and selected rendering resolution, the following can take some time
* Wait. There should be activity in the listener window on the bottom left of GMax' main screen
* After a moment, a window labeled "RenderSuite" should pop up, in which the rendered content of the "Camera01" viewport is slowly drawn
** In case no window pops up, refer to the second entry in the [[#Troubleshooting | troubleshooting]] section
* In case of a pleasing rendering result, clicking the disk icon will save the output image in Windows Bitmap format to the "RenderSuite" folder
* This is the basic process. Plaing with the options for the camera, lights and YAFRAY can yield better results. The worst that can happen is a weird looking or empty render image
 

=== Example Render Images ===

[[image:732.jpg | thumb | none | Boeing 737-200 rendered with RenderSuite's YAGMAX mode]]
[[image:580vc.jpg | thumb | none | Convair 580 cockpit model rendered with RenderSuite's YAGMAX mode]]
 
=== Troubleshooting ===
# No "Rendering" menu
#* Redownload RenderSuite, if the .zip file is not present anymore and extract the "Maxmenus.mnu" file from it
#* Copy the .mnu file to "Gmax\RenderSuite"
#* While in GMax, go to "Customize", then "LoadCustomUI scheme"
#* Browse to the "RenderSuite" folder, then select "Menu File (.mnu)" from the dropdown box above "Open"
#* Select the "Maxmenus.mnu" file and click "Open"
#* You should now have a "Rendering" menu item. if not, restart GMax or repeat the procedure
#: 
# No rendering window after clicking "Render"
#* Open Windows task manager (CTRL+Shift+ESC)
#* Select "GMaxRender.exe" in the process list
#* Click "End Process"
#* Browse to your RenderSuite folder in Windows Explorer
#* Start GMaxRender.exe
#* The rendering window should now pop up and start to display the rendered image. If not, restart the rendering process

Rendering with GMax

2013-08-02T00:39:55Z

Heretic:

{{Infobox-Applicable-FSVersion
| P3D2 = true
| P3D = true
| FSXI = true
| FSXA = true
| FSX = true
| FS2004 = true
| FS2002 = true
| XP10 = unknown
| XP9 = unknown
}}
One of the advantages of using 3D Studio Max over GMax has always been the capability of the former to perform a quick or full rendering of the model one is working on. 
Yet, with the right plugins and a bit of effort, one can add such a rendering function to GMax. 
 
This article gives instructions on how to set up and the basic usage of such a plugin.

=== Prerequisites ===
* An installation of GMax 1.2 (installed gamepack does not matter)
* Download GMax Rendering Suite from [http://www.ppmsite.com/forum/download.php?id=44398&sid=5f064355c02c38dcb5cba130c15354fb here]
 
=== Installation of the rendering plugin ===
# Unzip the downloaded plugin
# Rername the folder "RenderSuite" or similar
# Running RenderSuiteInstall.exe from the folder and follow the instructions
# Delete the .bat file the installer creates on your desktop
# Inside your main GMax Folder, create an empty text file
# Put these lines inside said text file:
#*For FS9:
#:echo on
#:cd %cd%\RenderSuite 
#:start GmaxRender.exe 
#:cd.. 
#:start gmax.exe -p gamepacks\FS2004\plugin.ini
#: 
#*For FSX
#:echo on 
#:cd %cd%\RenderSuite 
#:start GmaxRender.exe 
#:cd.. 
#:start gmax.exe -i gamepacks\FSX_GMaxGamepack\gmax.ini -p gamepacks\FSX_GMaxGamepack\plugin.ini
#: 
# Save the text file as "GMax with Render.bat" or similar. When asked to change file type, say "Yes"
#* Create a shortcut to the batch file for the desktop, if so desired
# Start GMax with the .bat file or the shortcut leading to it
# There should be a "Rendering" entry in the main menu bar. If not, refer to the [[#Troubleshooting | troubleshooting]] section
 
=== Using the RenderSuite ===
General usage of the render suite is as follows.
 
* Put some lights into your scene. Spots, Omnis, anything that will properly light the object. Default properties are okay for a start
* Put a camera into your scene. Free or Target
* Adjust the angle and position of the camera, so that the desired objects are rougly in focus
** Make sure to tick "Manual Clipping" in the camera options!
*** For interior spaces, a 15mm lens and 0.0m near clipping treshhold works well
* Click any viewport's name, then go to "Views" and select "Camera01". The viewport should now show what the camera is seeing
* The custom camera can be controlled like the default camera in the "Perspective" or "User" viewport mode. Fine tune, if needed
* When ready, select "Rendering" from the menu
* Select any of the two clients
** YAGMAX seems to work best for the author
** RenderSuite output an untextured model and requires that any scene object has a material applied
* Rendering options should be left at default for now
* Make sure that the active viewport is set to "Camera01"
* Click YAFRAY Render
** Note: Depending on the number of objects and polygons visible in the scene and selected rendering resolution, the following can take some time
* Wait. There should be activity in the listener window on the bottom left of GMax' main screen
* After a moment, a window labeled "RenderSuite" should pop up, in which the rendered content of the "Camera01" viewport is slowly drawn
** In case no window pops up, refer to the second entry in the [[#Troubleshooting | troubleshooting]] section
* In case of a pleasing rendering result, clicking the disk icon will save the output image in Windows Bitmap format to the "RenderSuite" folder
* This is the basic process. Plaing with the options for the camera, lights and YAFRAY can yield better results. The worst that can happen is a weird looking or empty render image
 
=== Example Render Images ===

[[image:732.jpg | thumb | none | Boeing 737-200 rendered with RenderSuite's YAGMAX mode]]
[[image:580vc.jpg | thumb | none | Convair 580 cockpit model rendered with RenderSuite's YAGMAX mode]]
 
=== Troubleshooting ===
# No "Rendering" menu
#* Redownload RenderSuite, if the .zip file is not present anymore and extract the "Maxmenus.mnu" file from it
#* Copy the .mnu file to "Gmax\RenderSuite"
#* While in GMax, go to "Customize", then "LoadCustomUI scheme"
#* Browse to the "RenderSuite" folder, then select "Menu File (.mnu)" from the dropdown box above "Open"
#* Select the "Maxmenus.mnu" file and click "Open"
#* You should now have a "Rendering" menu item. if not, restart GMax or repeat the procedure
#: 
# No rendering window after clicking "Render"
#* Open Windows task manager (CTRL+Shift+ESC)
#* Select "GMaxRender.exe" in the process list
#* Click "End Process"
#* Browse to your RenderSuite folder in Windows Explorer
#* Start GMaxRender.exe
#* The rendering window should now pop up and start to display the rendered image. If not, restart the rendering process

Rendering with GMax

2013-08-02T00:39:20Z

Heretic:

{{Infobox-Applicable-FSVersion
| P3D2 = true
| P3D = true
| FSXI = true
| FSXA = true
| FSX = true
| FS2004 = true
| FS2002 = true
| XP10 = unknown
| XP9 = unknown
}}
One of the advantages of using 3D Studio Max over GMax has always been the capability of the former to perform a quick or full rendering of the model one is working on. 
Yet, with the right plugins and a bit of effort, one can add such a rendering function to GMax. 
 
This article gives instructions on how to set up and the basic usage of such a plugin.
 
 
=== Prerequisites ===
* An installation of GMax 1.2 (installed gamepack does not matter)
* Download GMax Rendering Suite from [http://www.ppmsite.com/forum/download.php?id=44398&sid=5f064355c02c38dcb5cba130c15354fb here]
 
=== Installation of the rendering plugin ===
# Unzip the downloaded plugin
# Rername the folder "RenderSuite" or similar
# Running RenderSuiteInstall.exe from the folder and follow the instructions
# Delete the .bat file the installer creates on your desktop
# Inside your main GMax Folder, create an empty text file
# Put these lines inside said text file:
#*For FS9:
#:echo on
#:cd %cd%\RenderSuite 
#:start GmaxRender.exe 
#:cd.. 
#:start gmax.exe -p gamepacks\FS2004\plugin.ini
#: 
#*For FSX
#:echo on 
#:cd %cd%\RenderSuite 
#:start GmaxRender.exe 
#:cd.. 
#:start gmax.exe -i gamepacks\FSX_GMaxGamepack\gmax.ini -p gamepacks\FSX_GMaxGamepack\plugin.ini
#: 
# Save the text file as "GMax with Render.bat" or similar. When asked to change file type, say "Yes"
#* Create a shortcut to the batch file for the desktop, if so desired
# Start GMax with the .bat file or the shortcut leading to it
# There should be a "Rendering" entry in the main menu bar. If not, refer to the [[#Troubleshooting | troubleshooting]] section
 
=== Using the RenderSuite ===
General usage of the render suite is as follows.
 
* Put some lights into your scene. Spots, Omnis, anything that will properly light the object. Default properties are okay for a start
* Put a camera into your scene. Free or Target
* Adjust the angle and position of the camera, so that the desired objects are rougly in focus
** Make sure to tick "Manual Clipping" in the camera options!
*** For interior spaces, a 15mm lens and 0.0m near clipping treshhold works well
* Click any viewport's name, then go to "Views" and select "Camera01". The viewport should now show what the camera is seeing
* The custom camera can be controlled like the default camera in the "Perspective" or "User" viewport mode. Fine tune, if needed
* When ready, select "Rendering" from the menu
* Select any of the two clients
** YAGMAX seems to work best for the author
** RenderSuite output an untextured model and requires that any scene object has a material applied
* Rendering options should be left at default for now
* Make sure that the active viewport is set to "Camera01"
* Click YAFRAY Render
** Note: Depending on the number of objects and polygons visible in the scene and selected rendering resolution, the following can take some time
* Wait. There should be activity in the listener window on the bottom left of GMax' main screen
* After a moment, a window labeled "RenderSuite" should pop up, in which the rendered content of the "Camera01" viewport is slowly drawn
** In case no window pops up, refer to the second entry in the [[#Troubleshooting | troubleshooting]] section
* In case of a pleasing rendering result, clicking the disk icon will save the output image in Windows Bitmap format to the "RenderSuite" folder
* This is the basic process. Plaing with the options for the camera, lights and YAFRAY can yield better results. The worst that can happen is a weird looking or empty render image
 
=== Example Render Images ===

[[image:732.jpg | thumb | none | Boeing 737-200 rendered with RenderSuite's YAGMAX mode]]
[[image:580vc.jpg | thumb | none | Convair 580 cockpit model rendered with RenderSuite's YAGMAX mode]]
 
=== Troubleshooting ===
# No "Rendering" menu
#* Redownload RenderSuite, if the .zip file is not present anymore and extract the "Maxmenus.mnu" file from it
#* Copy the .mnu file to "Gmax\RenderSuite"
#* While in GMax, go to "Customize", then "LoadCustomUI scheme"
#* Browse to the "RenderSuite" folder, then select "Menu File (.mnu)" from the dropdown box above "Open"
#* Select the "Maxmenus.mnu" file and click "Open"
#* You should now have a "Rendering" menu item. if not, restart GMax or repeat the procedure
#: 
# No rendering window after clicking "Render"
#* Open Windows task manager (CTRL+Shift+ESC)
#* Select "GMaxRender.exe" in the process list
#* Click "End Process"
#* Browse to your RenderSuite folder in Windows Explorer
#* Start GMaxRender.exe
#* The rendering window should now pop up and start to display the rendered image. If not, restart the rendering process

Rendering with GMax

2013-08-02T00:37:57Z

Heretic: /* Troubleshooting */

One of the advantages of using 3D Studio Max over GMax has always been the capability of the former to perform a quick or full rendering of the model one is working on. 
Yet, with the right plugins and a bit of effort, one can add such a rendering function to GMax. 
 
This article gives instructions on how to set up and the basic usage of such a plugin.
 
 
=== Prerequisites ===
* An installation of GMax 1.2 (installed gamepack does not matter)
* Download GMax Rendering Suite from [http://www.ppmsite.com/forum/download.php?id=44398&sid=5f064355c02c38dcb5cba130c15354fb here]
 
=== Installation of the rendering plugin ===
# Unzip the downloaded plugin
# Rername the folder "RenderSuite" or similar
# Running RenderSuiteInstall.exe from the folder and follow the instructions
# Delete the .bat file the installer creates on your desktop
# Inside your main GMax Folder, create an empty text file
# Put these lines inside said text file:
#*For FS9:
#:echo on
#:cd %cd%\RenderSuite 
#:start GmaxRender.exe 
#:cd.. 
#:start gmax.exe -p gamepacks\FS2004\plugin.ini
#: 
#*For FSX
#:echo on 
#:cd %cd%\RenderSuite 
#:start GmaxRender.exe 
#:cd.. 
#:start gmax.exe -i gamepacks\FSX_GMaxGamepack\gmax.ini -p gamepacks\FSX_GMaxGamepack\plugin.ini
#: 
# Save the text file as "GMax with Render.bat" or similar. When asked to change file type, say "Yes"
#* Create a shortcut to the batch file for the desktop, if so desired
# Start GMax with the .bat file or the shortcut leading to it
# There should be a "Rendering" entry in the main menu bar. If not, refer to the [[#Troubleshooting | troubleshooting]] section
 
=== Using the RenderSuite ===
General usage of the render suite is as follows.
 
* Put some lights into your scene. Spots, Omnis, anything that will properly light the object. Default properties are okay for a start
* Put a camera into your scene. Free or Target
* Adjust the angle and position of the camera, so that the desired objects are rougly in focus
** Make sure to tick "Manual Clipping" in the camera options!
*** For interior spaces, a 15mm lens and 0.0m near clipping treshhold works well
* Click any viewport's name, then go to "Views" and select "Camera01". The viewport should now show what the camera is seeing
* The custom camera can be controlled like the default camera in the "Perspective" or "User" viewport mode. Fine tune, if needed
* When ready, select "Rendering" from the menu
* Select any of the two clients
** YAGMAX seems to work best for the author
** RenderSuite output an untextured model and requires that any scene object has a material applied
* Rendering options should be left at default for now
* Make sure that the active viewport is set to "Camera01"
* Click YAFRAY Render
** Note: Depending on the number of objects and polygons visible in the scene and selected rendering resolution, the following can take some time
* Wait. There should be activity in the listener window on the bottom left of GMax' main screen
* After a moment, a window labeled "RenderSuite" should pop up, in which the rendered content of the "Camera01" viewport is slowly drawn
** In case no window pops up, refer to the second entry in the [[#Troubleshooting | troubleshooting]] section
* In case of a pleasing rendering result, clicking the disk icon will save the output image in Windows Bitmap format to the "RenderSuite" folder
* This is the basic process. Plaing with the options for the camera, lights and YAFRAY can yield better results. The worst that can happen is a weird looking or empty render image
 
=== Example Render Images ===

[[image:732.jpg | thumb | none | Boeing 737-200 rendered with RenderSuite's YAGMAX mode]]
[[image:580vc.jpg | thumb | none | Convair 580 cockpit model rendered with RenderSuite's YAGMAX mode]]
 
=== Troubleshooting ===
# No "Rendering" menu
#* Redownload RenderSuite, if the .zip file is not present anymore and extract the "Maxmenus.mnu" file from it
#* Copy the .mnu file to "Gmax\RenderSuite"
#* While in GMax, go to "Customize", then "LoadCustomUI scheme"
#* Browse to the "RenderSuite" folder, then select "Menu File (.mnu)" from the dropdown box above "Open"
#* Select the "Maxmenus.mnu" file and click "Open"
#* You should now have a "Rendering" menu item. if not, restart GMax or repeat the procedure
#: 
# No rendering window after clicking "Render"
#* Open Windows task manager (CTRL+Shift+ESC)
#* Select "GMaxRender.exe" in the process list
#* Click "End Process"
#* Browse to your RenderSuite folder in Windows Explorer
#* Start GMaxRender.exe
#* The rendering window should now pop up and start to display the rendered image. If not, restart the rendering process

Rendering with GMax

2013-08-02T00:36:48Z

Heretic: New page: One of the advantages of using 3D Studio Max over GMax has always been the capability of the former to perform a quick or full rendering of the model one is working on. Yet, with the r...

File:732.jpg

2013-08-01T23:51:21Z

Heretic: 732 rendered in RenderSuite for Gmax

732 rendered in RenderSuite for Gmax

List of Open Source Projects for MSFS

2013-08-01T22:16:13Z

Heretic: /* Aircraft */

{{Infobox-Applicable-FSVersion
| FSXI = false
| FSXA = true
| FSX = true
| FS2004 = true
| FS2002 = true
| FS2000 = true
| FS98 = true
}}

= About =

This is a list of open source projects for FS 98 and beyond.

"Open Source" means that the source files of these projects are readily available for everyone to download and use for a variety of purposes, such as case studies, compilation and use or further development.

However, '''any restrictions imposed by the original author concerning use and distribution and specified on the project page or in "readme" files enclosed in the downloads are to be respected at all times!'''

'''Participation in expanding this list is endorsed. Please keep the formatting of the entries standardized.'''

= Aircraft =

#
#* Aircraft: '''Dornier 328-130/-310'''
#* Original simulator: FSX SP2/Acc
#* Project page/download: [http://code.google.com/p/fsx-dornier-328/]
#* License: [http://code.google.com/p/fsx-dornier-328/wiki/License]
#* Modeling tool: 3DS Max 9
#* Notes: Still in development by the original author; albeit slow progress
#
#* Aircraft: '''Boeing 737-200ADV'''
#* Original Simulator: FS9
#* Project page/download: [http://www.fsdeveloper.com/forum/showthread.php?t=299224]
#* License: Enclosed in Download
#* Modeling tool: GMax 1.2
#* Notes: Still in development, uses panels from the TinMouse 2 project (with permission)

= Sceneries =

#
#*Airport: Düsseldorf (EDDL)
#*Original simulator: FSX SP2/Acc
#*Project page/download: [http://www.flightsim.com/kdl.php?fid=157557]
#*License: See readme.
#*Modeling tool: GMax
#*Notes: Finished scenery available here [http://www.flightsim.com/kdl.php?fid=157549]

= Tools =

None at this time.

List of Open Source Projects for MSFS

2013-08-01T22:13:48Z

Heretic: /* Aircraft */

{{Infobox-Applicable-FSVersion
| FSXI = false
| FSXA = true
| FSX = true
| FS2004 = true
| FS2002 = true
| FS2000 = true
| FS98 = true
}}

= About =

This is a list of open source projects for FS 98 and beyond.

"Open Source" means that the source files of these projects are readily available for everyone to download and use for a variety of purposes, such as case studies, compilation and use or further development.

However, '''any restrictions imposed by the original author concerning use and distribution and specified on the project page or in "readme" files enclosed in the downloads are to be respected at all times!'''

'''Participation in expanding this list is endorsed. Please keep the formatting of the entries standardized.'''

= Aircraft =

#
#* Aircraft: '''Dornier 328-130/-310'''
#* Original simulator: FSX SP2/Acc
#* Project page/download: [http://code.google.com/p/fsx-dornier-328/]
#* License: [http://code.google.com/p/fsx-dornier-328/wiki/License]
#* Modeling tool: 3DS Max 9
#* Notes: Still in development by the original author; albeit slow progress

##
#* Aircraft: '''Boeing 737-200ADV'''
#* Original Simulator: FS9
#* Project page/download: [http://www.fsdeveloper.com/forum/showthread.php?t=299224]
#* License: Enclosed in Download
#* Modeling tool: GMax 1.2
#* Notes: Still in development, uses panels from the TinMouse 2 project (with permission)

= Sceneries =

#
#*Airport: Düsseldorf (EDDL)
#*Original simulator: FSX SP2/Acc
#*Project page/download: [http://www.flightsim.com/kdl.php?fid=157557]
#*License: See readme.
#*Modeling tool: GMax
#*Notes: Finished scenery available here [http://www.flightsim.com/kdl.php?fid=157549]

= Tools =

None at this time.

List of Open Source Projects for MSFS

2013-08-01T22:13:39Z

Heretic: /* Aircraft */

{{Infobox-Applicable-FSVersion
| FSXI = false
| FSXA = true
| FSX = true
| FS2004 = true
| FS2002 = true
| FS2000 = true
| FS98 = true
}}

= About =

This is a list of open source projects for FS 98 and beyond.

"Open Source" means that the source files of these projects are readily available for everyone to download and use for a variety of purposes, such as case studies, compilation and use or further development.

However, '''any restrictions imposed by the original author concerning use and distribution and specified on the project page or in "readme" files enclosed in the downloads are to be respected at all times!'''

'''Participation in expanding this list is endorsed. Please keep the formatting of the entries standardized.'''

= Aircraft =

#
#* Aircraft: '''Dornier 328-130/-310'''
#* Original simulator: FSX SP2/Acc
#* Project page/download: [http://code.google.com/p/fsx-dornier-328/]
#* License: [http://code.google.com/p/fsx-dornier-328/wiki/License]
#* Modeling tool: 3DS Max 9
#* Notes: Still in development by the original author; albeit slow progress

#* Aircraft: '''Boeing 737-200ADV'''
#* Original Simulator: FS9
#* Project page/download: [http://www.fsdeveloper.com/forum/showthread.php?t=299224]
#* License: Enclosed in Download
#* Modeling tool: GMax 1.2
#* Notes: Still in development, uses panels from the TinMouse 2 project (with permission)

= Sceneries =

#
#*Airport: Düsseldorf (EDDL)
#*Original simulator: FSX SP2/Acc
#*Project page/download: [http://www.flightsim.com/kdl.php?fid=157557]
#*License: See readme.
#*Modeling tool: GMax
#*Notes: Finished scenery available here [http://www.flightsim.com/kdl.php?fid=157549]

= Tools =

None at this time.

List of Open Source Projects for MSFS

2013-08-01T22:13:26Z

Heretic: /* Aircraft */

{{Infobox-Applicable-FSVersion
| FSXI = false
| FSXA = true
| FSX = true
| FS2004 = true
| FS2002 = true
| FS2000 = true
| FS98 = true
}}

= About =

This is a list of open source projects for FS 98 and beyond.

"Open Source" means that the source files of these projects are readily available for everyone to download and use for a variety of purposes, such as case studies, compilation and use or further development.

However, '''any restrictions imposed by the original author concerning use and distribution and specified on the project page or in "readme" files enclosed in the downloads are to be respected at all times!'''

'''Participation in expanding this list is endorsed. Please keep the formatting of the entries standardized.'''

= Aircraft =

#
#* Aircraft: '''Dornier 328-130/-310'''
#* Original simulator: FSX SP2/Acc
#* Project page/download: [http://code.google.com/p/fsx-dornier-328/]
#* License: [http://code.google.com/p/fsx-dornier-328/wiki/License]
#* Modeling tool: 3DS Max 9
#* Notes: Still in development by the original author; albeit slow progress

#
#* Aircraft: '''Boeing 737-200ADV'''
#* Original Simulator: FS9
#* Project page/download: [http://www.fsdeveloper.com/forum/showthread.php?t=299224]
#* License: Enclosed in Download
#* Modeling tool: GMax 1.2
#* Notes: Still in development, uses panels from the TinMouse 2 project (with permission)

= Sceneries =

#
#*Airport: Düsseldorf (EDDL)
#*Original simulator: FSX SP2/Acc
#*Project page/download: [http://www.flightsim.com/kdl.php?fid=157557]
#*License: See readme.
#*Modeling tool: GMax
#*Notes: Finished scenery available here [http://www.flightsim.com/kdl.php?fid=157549]

= Tools =

None at this time.

XML: Refreshing Panels in FS9 & FSX

2013-06-03T15:55:50Z

Heretic:

{{Infobox-Applicable-FSVersion
| FSXI = false
| FSXA = false
| FSX = false
| FS2004 = true
| FS2002 = true
| FS2000 = false
| FS98 = false
}}

Unlike FSX, FS9 does not offer the possibility to assign a key combination for refreshin an aircraft's panel in the UI.
Therefor, one has to resort to one of three methods to avoid reloading the whole aircraft every time a gauge or its placement properties are changed.

=== Method 1: A clickable button on the panel ===

Similar to the default SimIcons, this small button forces a refresh of the panel (panel.cfg and all gauges used by it).
It can be downloaded [http://www.fsdeveloper.com/forum/showpost.php?p=630731&postcount=4 here] and can be placed whereever desired.

=== Method 2: Reload by fs9.cfg and keystroke ===

Add this under <nowiki>"[KEYBOARD_MAIN]"</nowiki> to the FS9.cfg: 
RELOAD_PANELS=121,11
 
This should make CTRL+SHIFT+F10 reload the panel.

'Beware:' There might be a chance that this key assignment will be deleted if you change something from FS9's UI and FS9 saves the changes to the .cfg file!

=== Method 3: Reload by gauge and keystroke ===

While method #2 above offers universal way to assign a keystroke combination to force a gauge refresh, this can also be achieved on a per-aicraft basis by means of a custom gauge.

Create a new gauge in the aircraft's "panel folder" and name it, e.g. "Reload_Panel.xml".
Then copy&paste in the following code into the xml:

<?xml version="1.0" encoding="UTF-8"?>
<Gauge Name="Reload Panel" Version="1.0">
<Keys>
<On Key="889">
(>K:RELOAD_PANELS)
</On>
</Keys>
</Gauge>

Finally, alias the gauge to the panel by putting the following line into <nowiki>[Window00]</nowiki> or <nowiki>[VCockpit01]</nowiki> sections.
 
gaugeXX=Reload_Panel,1,1,1,1
 
Make sure to keep the gauge in sequence with the already existant ones! 
This places a 1-by-1 pixel sized gauge at position 1,1 on the main panel or in the VC.

References for key codes and further applications for controlling custom gauge variables by key can be found [http://www.fsdeveloper.com/forum/showpost.php?p=631147&postcount=5 here] and [http://www.fsdeveloper.com/forum/showpost.php?p=631148&postcount=6 here].

[[Category:Aircraft Design]]
[[Category:Panel and Gauge Design]]

XML: Refreshing Panels in FS9 & FSX

2013-03-11T19:47:01Z

Heretic:

{{Infobox-Applicable-FSVersion
| FSXI = false
| FSXA = false
| FSX = false
| FS2004 = true
| FS2002 = true
| FS2000 = false
| FS98 = false
}}

Unlike FSX, FS9 does not offer the possibility to assign a key combination for refreshin an aircraft's panel in the UI.
Therefor, one has to resort to one of three methods to avoid reloading the whole aircraft every time a gauge or its placement properties are changed.

=== Method 1: A clickable button on the panel ===

Similar to the default SimIcons, this small button forces a refresh of the panel (panel.cfg and all gauges used by it).
It can be downloaded [http://www.fsdeveloper.com/forum/showpost.php?p=630731&postcount=4 here] and can be placed whereever desired.

=== Method 2: Reload by fs9.cfg and keystroke ===

Add this under <nowiki>"[KEYBOARD_MAIN]"</nowiki> to the FS9.cfg: 
RELOAD_PANELS=121,11
 
This should make CTRL+SHIFT+F10 reload the panel.

'Beware:' There might be a chance that this key assignment will be deleted if you change something from FS9's UI and FS9 saves the changes to the .cfg file!

=== Method 3: Reload by gauge and keystroke ===

While method #2 above offers universal way to assign a keystroke combination to force a gauge refresh, this can also be achieved on a per-aicraft basis by means of a custom gauge.

Create a new gauge in the aircraft's "panel folder" and name it, e.g. "Reload_Panel.xml".
Then copy&paste in the following code into the xml:

<?xml version="1.0" encoding="UTF-8"?>
<Gauge Name="Reload Panel" Version="1.0">
<Keys>
<On Key="889">
(>K:RELOAD_PANELS)
</On>
</Keys>
</Gauge>

Finally, alias the gauge to the panel by putting the following line into <nowiki>[Window00]</nowiki> or <nowiki>[VCockpit01]</nowiki> sections.
 
gaugeXX=Reload_Panel,1,1,1,1</nowiki>
 
Make sure to keep the gauge in sequence with the already existant ones! 
This places a 1-by-1 pixel sized gauge at position 1,1 on the main panel or in the VC.

References for key codes and further applications for controlling custom gauge variables by key can be found [http://www.fsdeveloper.com/forum/showpost.php?p=631147&postcount=5 here] and [http://www.fsdeveloper.com/forum/showpost.php?p=631148&postcount=6 here].

[[Category:Aircraft Design]]
[[Category:Panel and Gauge Design]]

XML: Refreshing Panels in FS9 & FSX

2013-03-11T19:46:40Z

Heretic: /* Method 3: Reload by gauge and keystroke */

{{Infobox-Applicable-FSVersion
| FSXI = false
| FSXA = false
| FSX = false
| FS2004 = true
| FS2002 = false
| FS2000 = false
| FS98 = false
}}

Unlike FSX, FS9 does not offer the possibility to assign a key combination for refreshin an aircraft's panel in the UI.
Therefor, one has to resort to one of three methods to avoid reloading the whole aircraft every time a gauge or its placement properties are changed.

=== Method 1: A clickable button on the panel ===

Similar to the default SimIcons, this small button forces a refresh of the panel (panel.cfg and all gauges used by it).
It can be downloaded [http://www.fsdeveloper.com/forum/showpost.php?p=630731&postcount=4 here] and can be placed whereever desired.

=== Method 2: Reload by fs9.cfg and keystroke ===

Add this under <nowiki>"[KEYBOARD_MAIN]"</nowiki> to the FS9.cfg: 
RELOAD_PANELS=121,11
 
This should make CTRL+SHIFT+F10 reload the panel.

'Beware:' There might be a chance that this key assignment will be deleted if you change something from FS9's UI and FS9 saves the changes to the .cfg file!

=== Method 3: Reload by gauge and keystroke ===

While method #2 above offers universal way to assign a keystroke combination to force a gauge refresh, this can also be achieved on a per-aicraft basis by means of a custom gauge.

Create a new gauge in the aircraft's "panel folder" and name it, e.g. "Reload_Panel.xml".
Then copy&paste in the following code into the xml:

<?xml version="1.0" encoding="UTF-8"?>
<Gauge Name="Reload Panel" Version="1.0">
<Keys>
<On Key="889">
(>K:RELOAD_PANELS)
</On>
</Keys>
</Gauge>

Finally, alias the gauge to the panel by putting the following line into <nowiki>[Window00]</nowiki> or <nowiki>[VCockpit01]</nowiki> sections.
 
gaugeXX=Reload_Panel,1,1,1,1</nowiki>
 
Make sure to keep the gauge in sequence with the already existant ones! 
This places a 1-by-1 pixel sized gauge at position 1,1 on the main panel or in the VC.

References for key codes and further applications for controlling custom gauge variables by key can be found [http://www.fsdeveloper.com/forum/showpost.php?p=631147&postcount=5 here] and [http://www.fsdeveloper.com/forum/showpost.php?p=631148&postcount=6 here].

[[Category:Aircraft Design]]
[[Category:Panel and Gauge Design]]

XML: Refreshing Panels in FS9 & FSX

2013-03-11T19:46:22Z

Heretic:

{{Infobox-Applicable-FSVersion
| FSXI = false
| FSXA = false
| FSX = false
| FS2004 = true
| FS2002 = false
| FS2000 = false
| FS98 = false
}}

Unlike FSX, FS9 does not offer the possibility to assign a key combination for refreshin an aircraft's panel in the UI.
Therefor, one has to resort to one of three methods to avoid reloading the whole aircraft every time a gauge or its placement properties are changed.

=== Method 1: A clickable button on the panel ===

Similar to the default SimIcons, this small button forces a refresh of the panel (panel.cfg and all gauges used by it).
It can be downloaded [http://www.fsdeveloper.com/forum/showpost.php?p=630731&postcount=4 here] and can be placed whereever desired.

=== Method 2: Reload by fs9.cfg and keystroke ===

Add this under <nowiki>"[KEYBOARD_MAIN]"</nowiki> to the FS9.cfg: 
RELOAD_PANELS=121,11
 
This should make CTRL+SHIFT+F10 reload the panel.

'Beware:' There might be a chance that this key assignment will be deleted if you change something from FS9's UI and FS9 saves the changes to the .cfg file!

=== Method 3: Reload by gauge and keystroke ===

While method #2 above offers universal way to assign a keystroke combination to force a gauge refresh, this can also be achieved on a per-aicraft basis by means of a custom gauge.

Create a new gauge in the aircraft's "panel folder" and name it, e.g. "Reload_Panel.xml".
Then copy&paste in the following code into the xml:

<?xml version="1.0" encoding="UTF-8"?>
<Gauge Name="Reload Panel" Version="1.0">
<Keys>
<On Key="889">
(>K:RELOAD_PANELS)
</On>
</Keys>
</Gauge>

Finally, alias the gauge to the panel by putting the following line into <nowiki>[Window00]</nowiki> or <nowiki>[VCockpit01]</nowiki> sections.
 
gaugeXX=Reload_Panel,1,1,1,1</nowiki>
 
Make sure to keep the gauge in sequence with the already existant ones! 
This places a 1-by-1 pixel sized gauge at position 1,1 on the main panel or in the VC.

References for key codes and further applications for controlling custom gauge variables by key can be found [[http://www.fsdeveloper.com/forum/showpost.php?p=631147&postcount=5 here]] and [[http://www.fsdeveloper.com/forum/showpost.php?p=631148&postcount=6 here]].

[[Category:Aircraft Design]]
[[Category:Panel and Gauge Design]]

XML: Refreshing Panels in FS9 & FSX

2013-03-11T19:44:05Z

Heretic: /* Method 1: A clickable button on the panel */

{{Infobox-Applicable-FSVersion
| FSXI = false
| FSXA = false
| FSX = false
| FS2004 = true
| FS2002 = false
| FS2000 = false
| FS98 = false
}}

Unlike FSX, FS9 does not offer the possibility to assign a key combination for refreshin an aircraft's panel in the UI.
Therefor, one has to resort to one of three methods to avoid reloading the whole aircraft every time a gauge or its placement properties are changed.

=== Method 1: A clickable button on the panel ===

Similar to the default SimIcons, this small button forces a refresh of the panel (panel.cfg and all gauges used by it).
It can be downloaded [http://www.fsdeveloper.com/forum/showpost.php?p=630731&postcount=4 here] and can be placed whereever desired.

=== Method 2: Reload by fs9.cfg and keystroke ===

Add this under <nowiki>"[KEYBOARD_MAIN]"</nowiki> to the FS9.cfg: 
RELOAD_PANELS=121,11
 
This should make CTRL+SHIFT+F10 reload the panel.

'Beware:' There might be a chance that this key assignment will be deleted if you change something from FS9's UI and FS9 saves the changes to the .cfg file!

=== Method 3: Reload by gauge and keystroke ===

While method #2 above offers universal way to assign a keystroke combination to force a gauge refresh, this can also be achieved on a per-aicraft basis by means of a custom gauge.

Create a new gauge in the aircraft's "panel folder" and name it, e.g. "Reload_Panel.xml".
Then copy&paste in the following code into the xml:

<?xml version="1.0" encoding="UTF-8"?>
<Gauge Name="Reload Panel" Version="1.0">
<Keys>
<On Key="889">
(>K:RELOAD_PANELS)
</On>
</Keys>
</Gauge>

Finally, alias the gauge to the panel by putting the following line into <nowiki>[Window00]</nowiki> or <nowiki>[VCockpit01]</nowiki> sections.
 
gaugeXX=Reload_Panel,1,1,1,1</nowiki>
 
Make sure to keep the gauge in sequence with the already existant ones! 
This places a 1-by-1 pixel sized gauge at position 1,1 on the main panel or in the VC.

[[Category:Aircraft Design]]
[[Category:Panel and Gauge Design]]

XML: Refreshing Panels in FS9 & FSX

2013-03-11T19:43:46Z

Heretic:

{{Infobox-Applicable-FSVersion
| FSXI = false
| FSXA = false
| FSX = false
| FS2004 = true
| FS2002 = false
| FS2000 = false
| FS98 = false
}}

Unlike FSX, FS9 does not offer the possibility to assign a key combination for refreshin an aircraft's panel in the UI.
Therefor, one has to resort to one of three methods to avoid reloading the whole aircraft every time a gauge or its placement properties are changed.

=== Method 1: A clickable button on the panel ===

Similar to the default SimIcons, this small button forces a refresh of the panel (panel.cfg and all gauges used by it).
It can be downloaded [http://www.fsdeveloper.com/forum/showpost.php?p=630731&postcount=4 here] and can be placed whereever so desired.

=== Method 2: Reload by fs9.cfg and keystroke ===

Add this under <nowiki>"[KEYBOARD_MAIN]"</nowiki> to the FS9.cfg: 
RELOAD_PANELS=121,11
 
This should make CTRL+SHIFT+F10 reload the panel.

'Beware:' There might be a chance that this key assignment will be deleted if you change something from FS9's UI and FS9 saves the changes to the .cfg file!

=== Method 3: Reload by gauge and keystroke ===

While method #2 above offers universal way to assign a keystroke combination to force a gauge refresh, this can also be achieved on a per-aicraft basis by means of a custom gauge.

Create a new gauge in the aircraft's "panel folder" and name it, e.g. "Reload_Panel.xml".
Then copy&paste in the following code into the xml:

<?xml version="1.0" encoding="UTF-8"?>
<Gauge Name="Reload Panel" Version="1.0">
<Keys>
<On Key="889">
(>K:RELOAD_PANELS)
</On>
</Keys>
</Gauge>

Finally, alias the gauge to the panel by putting the following line into <nowiki>[Window00]</nowiki> or <nowiki>[VCockpit01]</nowiki> sections.
 
gaugeXX=Reload_Panel,1,1,1,1</nowiki>
 
Make sure to keep the gauge in sequence with the already existant ones! 
This places a 1-by-1 pixel sized gauge at position 1,1 on the main panel or in the VC.

[[Category:Aircraft Design]]
[[Category:Panel and Gauge Design]]

XML: Refreshing Panels in FS9 & FSX

2013-03-11T19:43:22Z

Heretic:

{{:Ambox-Content-WIP}}
{{Infobox-Applicable-FSVersion
| FSXI = false
| FSXA = false
| FSX = false
| FS2004 = true
| FS2002 = false
| FS2000 = false
| FS98 = false
}}
{{:Transclusion-Keys_Mapping_Flyers}}

Unlike FSX, FS9 does not offer the possibility to assign a key combination for refreshin an aircraft's panel in the UI.
Therefor, one has to resort to one of three methods to avoid reloading the whole aircraft every time a gauge or its placement properties are changed.

=== Method 1: A clickable button on the panel ===

Similar to the default SimIcons, this small button forces a refresh of the panel (panel.cfg and all gauges used by it).
It can be downloaded [http://www.fsdeveloper.com/forum/showpost.php?p=630731&postcount=4 here] and can be placed whereever so desired.

=== Method 2: Reload by fs9.cfg and keystroke ===

Add this under <nowiki>"[KEYBOARD_MAIN]"</nowiki> to the FS9.cfg: 
RELOAD_PANELS=121,11
 
This should make CTRL+SHIFT+F10 reload the panel.

'Beware:' There might be a chance that this key assignment will be deleted if you change something from FS9's UI and FS9 saves the changes to the .cfg file!

=== Method 3: Reload by gauge and keystroke ===

While method #2 above offers universal way to assign a keystroke combination to force a gauge refresh, this can also be achieved on a per-aicraft basis by means of a custom gauge.

Create a new gauge in the aircraft's "panel folder" and name it, e.g. "Reload_Panel.xml".
Then copy&paste in the following code into the xml:

<?xml version="1.0" encoding="UTF-8"?>
<Gauge Name="Reload Panel" Version="1.0">
<Keys>
<On Key="889">
(>K:RELOAD_PANELS)
</On>
</Keys>
</Gauge>

Finally, alias the gauge to the panel by putting the following line into <nowiki>[Window00]</nowiki> or <nowiki>[VCockpit01]</nowiki> sections.
 
gaugeXX=Reload_Panel,1,1,1,1</nowiki>
 
Make sure to keep the gauge in sequence with the already existant ones! 
This places a 1-by-1 pixel sized gauge at position 1,1 on the main panel or in the VC.

[[Category:Aircraft Design]]
[[Category:Panel and Gauge Design]]

XML: Refreshing Panels in FS9 & FSX

2013-03-11T19:41:40Z

Heretic: /* Method 2: Reload by keystroke */

Unlike FSX, FS9 does not offer the possibility to assign a key combination for refreshin an aircraft's panel in the UI.
Therefor, one has to resort to one of three methods to avoid reloading the whole aircraft every time a gauge or its placement properties are changed.

=== Method 1: A clickable button on the panel ===

Similar to the default SimIcons, this small button forces a refresh of the panel (panel.cfg and all gauges used by it).
It can be downloaded [http://www.fsdeveloper.com/forum/showpost.php?p=630731&postcount=4 here] and can be placed whereever so desired.

=== Method 2: Reload by fs9.cfg and keystroke ===

Add this under <nowiki>"[KEYBOARD_MAIN]"</nowiki> to the FS9.cfg: 
RELOAD_PANELS=121,11
 
This should make CTRL+SHIFT+F10 reload the panel.

'Beware:' There might be a chance that this key assignment will be deleted if you change something from FS9's UI and FS9 saves the changes to the .cfg file!

=== Method 3: Reload by gauge and keystroke ===

While method #2 above offers universal way to assign a keystroke combination to force a gauge refresh, this can also be achieved on a per-aicraft basis by means of a custom gauge.

Create a new gauge in the aircraft's "panel folder" and name it, e.g. "Reload_Panel.xml".
Then copy&paste in the following code into the xml:

<?xml version="1.0" encoding="UTF-8"?>
<Gauge Name="Reload Panel" Version="1.0">
<Keys>
<On Key="889">
(>K:RELOAD_PANELS)
</On>
</Keys>
</Gauge>

Finally, alias the gauge to the panel by putting the following line into <nowiki>[Window00]</nowiki> or <nowiki>[VCockpit01]</nowiki> sections.
 
gaugeXX=Reload_Panel,1,1,1,1</nowiki>
 
Make sure to keep the gauge in sequence with the already existant ones! 
This places a 1-by-1 pixel sized gauge at position 1,1 on the main panel or in the VC.

XML: Refreshing Panels in FS9 & FSX

2013-03-11T19:41:28Z

Heretic: /* Method 3: Reload by gauge */

Unlike FSX, FS9 does not offer the possibility to assign a key combination for refreshin an aircraft's panel in the UI.
Therefor, one has to resort to one of three methods to avoid reloading the whole aircraft every time a gauge or its placement properties are changed.

=== Method 1: A clickable button on the panel ===

Similar to the default SimIcons, this small button forces a refresh of the panel (panel.cfg and all gauges used by it).
It can be downloaded [http://www.fsdeveloper.com/forum/showpost.php?p=630731&postcount=4 here] and can be placed whereever so desired.

=== Method 2: Reload by keystroke ===

Add this under <nowiki>"[KEYBOARD_MAIN]"</nowiki> to the FS9.cfg: 
RELOAD_PANELS=121,11
 
This should make CTRL+SHIFT+F10 reload the panel.

'Beware:' There might be a chance that this key assignment will be deleted if you change something from FS9's UI and FS9 saves the changes to the .cfg file!

=== Method 3: Reload by gauge and keystroke ===

While method #2 above offers universal way to assign a keystroke combination to force a gauge refresh, this can also be achieved on a per-aicraft basis by means of a custom gauge.

Create a new gauge in the aircraft's "panel folder" and name it, e.g. "Reload_Panel.xml".
Then copy&paste in the following code into the xml:

<?xml version="1.0" encoding="UTF-8"?>
<Gauge Name="Reload Panel" Version="1.0">
<Keys>
<On Key="889">
(>K:RELOAD_PANELS)
</On>
</Keys>
</Gauge>

Finally, alias the gauge to the panel by putting the following line into <nowiki>[Window00]</nowiki> or <nowiki>[VCockpit01]</nowiki> sections.
 
gaugeXX=Reload_Panel,1,1,1,1</nowiki>
 
Make sure to keep the gauge in sequence with the already existant ones! 
This places a 1-by-1 pixel sized gauge at position 1,1 on the main panel or in the VC.

XML: Refreshing Panels in FS9 & FSX

2013-03-11T19:41:06Z

Heretic: New page: Unlike FSX, FS9 does not offer the possibility to assign a key combination for refreshin an aircraft's panel in the UI. Therefor, one has to resort to one of three methods to avoid reloadi...

Unlike FSX, FS9 does not offer the possibility to assign a key combination for refreshin an aircraft's panel in the UI.
Therefor, one has to resort to one of three methods to avoid reloading the whole aircraft every time a gauge or its placement properties are changed.

=== Method 1: A clickable button on the panel ===

Similar to the default SimIcons, this small button forces a refresh of the panel (panel.cfg and all gauges used by it).
It can be downloaded [http://www.fsdeveloper.com/forum/showpost.php?p=630731&postcount=4 here] and can be placed whereever so desired.

=== Method 2: Reload by keystroke ===

Add this under <nowiki>"[KEYBOARD_MAIN]"</nowiki> to the FS9.cfg: 
RELOAD_PANELS=121,11
 
This should make CTRL+SHIFT+F10 reload the panel.

'Beware:' There might be a chance that this key assignment will be deleted if you change something from FS9's UI and FS9 saves the changes to the .cfg file!

=== Method 3: Reload by gauge ===

While method #2 above offers universal way to assign a keystroke combination to force a gauge refresh, this can also be achieved on a per-aicraft basis by means of a custom gauge.

Create a new gauge in the aircraft's "panel folder" and name it, e.g. "Reload_Panel.xml".
Then copy&paste in the following code into the xml:

<?xml version="1.0" encoding="UTF-8"?>
<Gauge Name="Reload Panel" Version="1.0">
<Keys>
<On Key="889">
(>K:RELOAD_PANELS)
</On>
</Keys>
</Gauge>

Finally, alias the gauge to the panel by putting the following line into <nowiki>[Window00]</nowiki> or <nowiki>[VCockpit01]</nowiki> sections.
 
gaugeXX=Reload_Panel,1,1,1,1</nowiki>
 
Make sure to keep the gauge in sequence with the already existant ones! 
This places a 1-by-1 pixel sized gauge at position 1,1 on the main panel or in the VC.

Makemdl

2012-12-20T23:27:45Z

Heretic:

{{Infobox-Applicable-FSVersion
| P3D = false
| FSXA = false
| FSX = false
| FS2004 = true
| FS2002 = true
| FS2000 = false
| FS98 = false
}}

MakeMDL is the primary compiler for objects created for Microsoft's Flight Simulator 9

In its latest iteration, available in the MakeMDL SDK [http://download.microsoft.com/download/1/1/8/1181a250-ac2c-43fa-b35b-bfd7b87934ad/makemdl_sdk_setup.exe] for FS9, it supports input commands via a file named "makemdl.cfg".
Normally, this file is located in the same folder in which MakeMDL.exe resides, e.g. "C:\gmax\gamepacks\fs2004\plugins"
 
== Sample MakeMDL.cfg ==

[Settings] 
LastDir= 
SaveDir=''C:\gmax\GAMEPA~1\FS2004\plugins'' 

[Options] 
Debug=1 
ViewLog=0 
KeepErrorLog=1 
Keep=0 
I8=1 
I=0 
FullMat=1 
Deffallback=1 
WeldPoints=0 
Optimize=0 
Flatten=0 
NoAnimate=0 
HasReflectMap=1 
HasNightMap=0 
HasLightMap=1 
HasDamageMap=0 
NegateZ=1 
NoLeftToRight=0 
SwapBH=0 
Vis=0 
Crash=0 
XML=1 
 
== Makemdl.cfg options explained ==

Of special interest to avid modellers for FS9 are the "Debug", "KeepErrorLog", "WeldPoints", "Optimize" and "Flatten" settings. 
;Debug: Set to "1" (no quote marks) to enable debug functionality 
;ViewLog: Automatically opens the log file after compilation if set to "1" 
;KeepErrorLog: Does not delete the log file if set to "1"; useful for finding erroneous parts or animations 
;Keep: Does not delete temporary files created during compilation if set to "1" 
;I8: ??? 
;I: ??? 
;FullMat: ??? 
;Deffallback: ??? 
 
The next three settings can be a cure to the 4mm vertex weld issue otherwise present for FS9 models (very notable and annoying in virtual cockpits)! 

;WeldPoints: Disable vertex welding when set to "0". 
;Optimize: Disables mesh optimization set to "0" 
;Flatten: Set to "0" to disable flattening of the hierarchy tree 
;NoAnimate: Does not parse animations during compilation if set to "1" 
;HasReflectMap: Set to "1" to enable reflectivity for the model. Make sure to put a "_t" suffix into the texture's file name, e.g. "fuselage_t.bmp" and make sure "Reflections" is enabled in FS9's "display" menu.
;HasNightMap: Enables use of auto-enabled night textures ("_lm" suffix, i.e. "tower_lm.bmp") if set to "1". You won't need to fill the "self-illumination" slot of the material in GMax. Useful for scenery design!
;HasLightMap: Enables use of self-illumination night textures ("_l" suffix, i.e. "fuselage_l.bmp") if set to "1". You won't need to fill the "self-illumination" slot of the material in GMax. Useful for aircraft design!
;HasDamageMap: Enables damage textures if set to "1". Not needed for FS9.
;NegateZ: If your object appears upside down in FS9, set this to "1".
;NoLeftToRight: Set this to "1" to invert the left/right coordinate axis
;SwapBH: When set to "1", the bank and heading axis of the model will be swapped
;Vis: ???
;Crash: Set to "1" to enable crash detection when compiling a scenery object.
;XML: Produces a sample placement XML file for a scenery object when set to "1"

[[category:Modeling]]

Makemdl

2012-12-20T23:26:02Z

Heretic:

MakeMDL is the primary compiler for objects created for Microsoft's Flight Simulator 9

In its latest iteration, available in the MakeMDL SDK [http://download.microsoft.com/download/1/1/8/1181a250-ac2c-43fa-b35b-bfd7b87934ad/makemdl_sdk_setup.exe] for FS9, it supports input commands via a file named "makemdl.cfg".
Normally, this file is located in the same folder in which MakeMDL.exe resides, e.g. "C:\gmax\gamepacks\fs2004\plugins"
 
== Sample MakeMDL.cfg ==

[Settings] 
LastDir= 
SaveDir=''C:\gmax\GAMEPA~1\FS2004\plugins'' 

[Options] 
Debug=1 
ViewLog=0 
KeepErrorLog=1 
Keep=0 
I8=1 
I=0 
FullMat=1 
Deffallback=1 
WeldPoints=0 
Optimize=0 
Flatten=0 
NoAnimate=0 
HasReflectMap=1 
HasNightMap=0 
HasLightMap=1 
HasDamageMap=0 
NegateZ=1 
NoLeftToRight=0 
SwapBH=0 
Vis=0 
Crash=0 
XML=1 
 
== Makemdl.cfg options explained ==

Of special interest to avid modellers for FS9 are the "Debug", "KeepErrorLog", "WeldPoints", "Optimize" and "Flatten" settings. 
;Debug: Set to "1" (no quote marks) to enable debug functionality 
;ViewLog: Automatically opens the log file after compilation if set to "1" 
;KeepErrorLog: Does not delete the log file if set to "1"; useful for finding erroneous parts or animations 
;Keep: Does not delete temporary files created during compilation if set to "1" 
;I8: ??? 
;I: ??? 
;FullMat: ??? 
;Deffallback: ??? 
 
The next three settings can be a cure to the 4mm vertex weld issue otherwise present for FS9 models (very notable and annoying in virtual cockpits)! 

;WeldPoints: Disable vertex welding when set to "0". 
;Optimize: Disables mesh optimization set to "0" 
;Flatten: Set to "0" to disable flattening of the hierarchy tree 
;NoAnimate: Does not parse animations during compilation if set to "1" 
;HasReflectMap: Set to "1" to enable reflectivity for the model. Make sure to put a "_t" suffix into the texture's file name, e.g. "fuselage_t.bmp" and make sure "Reflections" is enabled in FS9's "display" menu.
;HasNightMap: Enables use of auto-enabled night textures ("_lm" suffix, i.e. "tower_lm.bmp") if set to "1". You won't need to fill the "self-illumination" slot of the material in GMax. Useful for scenery design!
;HasLightMap: Enables use of self-illumination night textures ("_l" suffix, i.e. "fuselage_l.bmp") if set to "1". You won't need to fill the "self-illumination" slot of the material in GMax. Useful for aircraft design!
;HasDamageMap: Enables damage textures if set to "1". Not needed for FS9.
;NegateZ: If your object appears upside down in FS9, set this to "1".
;NoLeftToRight: Set this to "1" to invert the left/right coordinate axis
;SwapBH: When set to "1", the bank and heading axis of the model will be swapped
;Vis: ???
;Crash: Set to "1" to enable crash detection when compiling a scenery object.
;XML: Produces a sample placement XML file for a scenery object when set to "1"

[[category:Modeling]]

Makemdl

2012-12-20T23:24:54Z

Heretic: /* Makemdl.cfg options explained */

Makemdl

2012-12-20T23:23:39Z

Heretic:

MakeMDL is the primary compiler for objects created for Microsoft's Flight Simulator 9

In its latest iteration, available in the MakeMDL SDK [http://download.microsoft.com/download/1/1/8/1181a250-ac2c-43fa-b35b-bfd7b87934ad/makemdl_sdk_setup.exe] for FS9, it supports input commands via a file named "makemdl.cfg".
Normally, this file is located in the same folder in which MakeMDL.exe resides, e.g. "C:\gmax\gamepacks\fs2004\plugins"
 
== Sample MakeMDL.cfg ==

[Settings] 
LastDir= 
SaveDir=''C:\gmax\GAMEPA~1\FS2004\plugins'' 

[Options] 
Debug=1 
ViewLog=0 
KeepErrorLog=1 
Keep=0 
I8=1 
I=0 
FullMat=1 
Deffallback=1 
WeldPoints=0 
Optimize=0 
Flatten=0 
NoAnimate=0 
HasReflectMap=1 
HasNightMap=0 
HasLightMap=1 
HasDamageMap=0 
NegateZ=1 
NoLeftToRight=0 
SwapBH=0 
Vis=0 
Crash=0 
XML=1 
 
== Makemdl.cfg options explained ==

Of special interest to avid modellers for FS9 are the "Debug", "KeepErrorLog", "WeldPoints", "Optimize" and "Flatten" settings. 
;Debug: Set to "1" (no quote marks) to enable debug functionality 
;ViewLog: Automatically opens the log file after compilation if set to "1" 
;KeepErrorLog: Does not delete the log file if set to "1"; useful for finding erroneous parts or animations 
;Keep: Does not delete temporary files created during compilation if set to "1" 
;I8: ??? 
;I: ??? 
;FullMat: ??? 
;Deffallback: ??? 
 
The next three settings can be a cure to the 4mm vertex weld issue otherwise present for FS9 models (very notable and annoying in virtual cockpits)! 

;WeldPoints: Disable vertex welding if set to "1". 
;Optimize: Does not optimize the mesh if set to "0" 
;Flatten: Set to "0" 
;NoAnimate: Does not parse animations during compilation if set to "1" 
;HasReflectMap: Set to "1" to enable reflectivity for the model. Make sure to put a "_t" suffix into the texture's file name, e.g. "fuselage_t.bmp" and make sure "Reflections" is enabled in FS9's "display" menu.
;HasNightMap: Enables use of auto-enabled night textures ("_lm" suffix, i.e. "tower_lm.bmp") if set to "1". You won't need to fill the "self-illumination" slot of the material in GMax. Useful for scenery design!
;HasLightMap: Enables use of self-illumination night textures ("_l" suffix, i.e. "fuselage_l.bmp") if set to "1". You won't need to fill the "self-illumination" slot of the material in GMax. Useful for aircraft design!
;HasDamageMap: Enables damage textures if set to "1". Not needed for FS9.
;NegateZ: If your object appears upside down in FS9, set this to "1".
;NoLeftToRight: Set this to "1" to invert the left/right coordinate axis
;SwapBH: When set to "1", the bank and heading axis of the model will be swapped
;Vis: ???
;Crash: Set to "1" to enable crash detection when compiling a scenery object.
;XML: Produces a sample placement XML file for a scenery object when set to "1"

[[category:Modelling]]

Makemdl

2012-12-20T23:23:14Z

Heretic:

MakeMDL is the primary compiler for objects created for Microsoft's Flight Simulator 9

In its latest iteration, available in the MakeMDL SDK [http://download.microsoft.com/download/1/1/8/1181a250-ac2c-43fa-b35b-bfd7b87934ad/makemdl_sdk_setup.exe] for FS9, it supports input commands via a file named "makemdl.cfg".
Normally, this file is located in the same folder in which MakeMDL.exe resides, e.g. "C:\gmax\gamepacks\fs2004\plugins"
 
== Sample MakeMDL.cfg ==

[Settings] 
LastDir= 
SaveDir=''C:\gmax\GAMEPA~1\FS2004\plugins'' 

[Options] 
Debug=1 
ViewLog=0 
KeepErrorLog=1 
Keep=0 
I8=1 
I=0 
FullMat=1 
Deffallback=1 
WeldPoints=0 
Optimize=0 
Flatten=0 
NoAnimate=0 
HasReflectMap=1 
HasNightMap=0 
HasLightMap=1 
HasDamageMap=0 
NegateZ=1 
NoLeftToRight=0 
SwapBH=0 
Vis=0 
Crash=0 
XML=1 
 
== Makemdl.cfg options explained ==

Of special interest to avid modellers for FS9 are the "Debug", "KeepErrorLog", "WeldPoints", "Optimize" and "Flatten" settings. 
;Debug: Set to "1" (no quote marks) to enable debug functionality 
;ViewLog: Automatically opens the log file after compilation if set to "1" 
;KeepErrorLog: Does not delete the log file if set to "1"; useful for finding erroneous parts or animations 
;Keep: Does not delete temporary files created during compilation if set to "1" 
;I8: ??? 
;I: ??? 
;FullMat: ??? 
;Deffallback: ??? 
 
The next three settings can be a cure to the 4mm vertex weld issue otherwise present for FS9 models (very notable and annoying in virtual cockpits)! 

;WeldPoints: Disable vertex welding if set to "1". 
;Optimize: Does not optimize the mesh if set to "0" 
;Flatten: Set to "0" 
;NoAnimate: Does not parse animations during compilation if set to "1" 
;HasReflectMap: Set to "1" to enable reflectivity for the model. Make sure to put a "_t" suffix into the texture's file name, e.g. "fuselage_t.bmp" and make sure "Reflections" is enabled in FS9's "display" menu.
;HasNightMap: Enables use of auto-enabled night textures ("_lm" suffix, i.e. "tower_lm.bmp") if set to "1". You won't need to fill the "self-illumination" slot of the material in GMax. Useful for scenery design!
;HasLightMap: Enables use of self-illumination night textures ("_l" suffix, i.e. "fuselage_l.bmp") if set to "1". You won't need to fill the "self-illumination" slot of the material in GMax. Useful for aircraft design!
;HasDamageMap: Enables damage textures if set to "1". Not needed for FS9.
;NegateZ: If your object appears upside down in FS9, set this to "1".
;NoLeftToRight: Set this to "1" to invert the left/right coordinate axis
;SwapBH: When set to "1", the bank and heading axis of the model will be swapped
;Vis: ???
;Crash: Set to "1" to enable crash detection when compiling a scenery object.
;XML: Produces a sample placement XML file for a scenery object when set to "1"

[[category:Modelling]]

Makemdl

2012-12-20T23:18:35Z

Heretic: /* Makemdl.cfg entries explained */

MakeMDL is the primary compiler for objects created for Microsoft's Flight Simulator 9

In its latest iteration, available in the MakeMDL SDK [http://download.microsoft.com/download/1/1/8/1181a250-ac2c-43fa-b35b-bfd7b87934ad/makemdl_sdk_setup.exe] for FS9, it supports input commands via a file named "makemdl.cfg".
Normally, this file is located in the same folder in which MakeMDL.exe resides, e.g. "C:\gmax\gamepacks\fs2004\plugins"
 
== Sample MakeMDL.cfg ==

[Settings] 
LastDir= 
SaveDir=''C:\gmax\GAMEPA~1\FS2004\plugins''''' 

[Options] 
Debug=1 
ViewLog=0 
KeepErrorLog=1 
Keep=0 
I8=1 
I=0 
FullMat=1 
Deffallback=1 
WeldPoints=0 
Optimize=0 
Flatten=0 
NoAnimate=0 
HasReflectMap=1 
HasNightMap=0 
HasLightMap=1 
HasDamageMap=0 
NegateZ=1 
NoLeftToRight=0 
SwapBH=0 
Vis=0 
Crash=0 
XML=1 
 
== Makemdl.cfg entries explained ==

Of special interest to avid modellers for FS9 are the "Debug", "KeepErrorLog", "WeldPoints", "Optimize" and "Flatten" settings. 
;Debug: Set to "1" (no quote marks) to enable debug functionality 
;ViewLog: Automatically opens the log file after compilation if set to "1" 
;KeepErrorLog: Does not delete the log file if set to "1"; useful for finding erroneous parts or animations 
;Keep: Does not delete temporary files created during compilation if set to "1" 
;I8: ??? 
;I: ??? 
;FullMat: ??? 
;Deffallback: ??? 
 
The next three settings can be a cure to the 4mm vertex weld issue otherwise present for FS9 models (very notable and annoying in virtual cockpits)! 

;WeldPoints: Disable vertex welding if set to "1". 
;Optimize: Does not optimize the mesh if set to "0" 
;Flatten: Set to "0" 
;NoAnimate: Does not parse animations during compilation if set to "1" 
;HasReflectMap: Set to "1" to enable reflectivity for the model. Make sure to put a "_t" suffix into the texture's file name, e.g. "fuselage_t.bmp" and make sure "Reflections" is enabled in FS9's "display" menu.
;HasNightMap: Enables use of auto-enabled night textures ("_lm" suffix, i.e. "tower_lm.bmp") if set to "1". You won't need to fill the "self-illumination" slot of the material in GMax. Useful for scenery design!
;HasLightMap: Enables use of self-illumination night textures ("_l" suffix, i.e. "fuselage_l.bmp") if set to "1". You won't need to fill the "self-illumination" slot of the material in GMax. Useful for aircraft design!
;HasDamageMap: Enables damage textures if set to "1". Not needed for FS9.
;NegateZ: If your object appears upside down in FS9, set this to "1"
;NoLeftToRight: ???
;SwapBH: ???
;Vis: ???
;Crash: Set to "1" to enable

[[category:Modelling]]

Mapping and texturing models in 3DS Max

2012-12-20T18:22:45Z

Heretic: /* In GIMP */

{{Infobox-Applicable-FSVersion
| FSXI = false
| FSXA = true
| FSX = true
| FS2004 = true
| FS2002 = true
| FS2000 = false
| FS98 = false
}}

= Introduction =

First of all, the steps covered in this tutorial are very similar to the ones decribed in "[[Texturing complex models in GMAX]]".
The difference is, that this workflow example makes use of 3DS Max superior UVW Unwrapper functionality which makes for easy and accurate part projections for texture creation.

Being a non-illustrated workflow based article, knowledge of basic 3DS Max and Image Editor functionality is required for understanding.
The programs used in this method are 3DS Max 9 and GIMP 2.6.11.

This method follows the creation of an untextured and unmapped model in 3DS Max.

= Workflow =

The section is divided into two parts, one for everything related to steps in 3DS Max and another for everything in GIMP.

== In 3DS Max ==

# First, a FSX-compilant material with a simple, single colored 2048*2048 px (or more/less resolution) diffuse map should be created. The texture should be saved in .psd format as it allows better editing.
# This material is then assigned to the first object to be textured, e.g. the fuselage.
# Then, a "UVW Map" modifier is used on the object. The settings are kept at default. (This step is probably redundant)
#* If one wants to map subparts or limited areas of the part, these should now be selected via "Edit Mesh" or "Edit Poly"
# An "Unwrap UVW" modifier is added to the stack and the UVW Unwrapper is entered
# By default, the editor should be in "Vertex" mode. In "Poly" mode (in the row of buttons below the Unwrapper window), all polys in the Unwrapper window should be selected.
# The next step is using "Tools -> Normal Mapping". The settings to choose (which side to render from) depend on the orientation of the part's pivot point, but one can try multiple times to find a useful solution. In any case,''' "Rotate Clusters" should be unticked''', as it makes things unnecessarily difficult.
# The result should be a perfect projection of the parts. They have to be scaled and moved until they are located within the bitmap boundaries (the thickly outlined blue frame).
#* Hint: "Uniform Scaling" is to be used on both parts of the projections if the parts need to be scaled. Moving or mirroring can be done independently for each part, but anything that's related to sizing has to be done for both sides as once, e.g. to line up a pattern of stripes in the nose or tail area of a fuselage. Having both parts in exactly the same scale also makes paining patterns and liveries a lot easier later on as one can just mirror the left side texture and fit it exactly to the right side with little to no scaling or further adjustment!
# Once the fitting the UVW Maps of parts to the texture or at least within the image boundaries is done, "Render UVW Texture" comes into use. In the settings dialog, it is of '''utmost importance to select "2048" for X and Y size of the texture'''. Pressing "Render" or "Go" will result in the part projection on a black texture. Selecting "Save" and ".png" and a 100% image quality as output format results in a convienient image, in which all the black parts of the texture are regarded as transparent. This, in turn, makes magic wand selection of the wireframe projection in GIMP much easier. Save the image in your project folder.

== In GIMP ==

# After the master texture file from step one above is opened in GIMP, the image file saved in step seven above is imported (opened) as a layer. It should be put above the background layer.
# A new layer for the base color should be created on top of the layer stack.
# The "Magic Wand" tool is now used on the layer with the imported wireframe of the part to be textured. Inverting the selection should have the outline of the part selected. Growing the selection by 2 to 3 pixels creates a "safety zone" to make sure that polygons at the edge will be properly textured as well.
# With the selection left intact, switching to the topmost layer in the stack and filling the selection with a simple color (a highly visible one if so desired) will create a base color for the part that can be further enhanced later on.
# After deselecting everything and saving (exporting, if using GIMP 2.8) the texture, a switch back to 3DS Max should reveal the now colored part, as Max has real-time texture file reading capabilities.
#* Should the texture change not be displayed, the texture file will have to be reloaded in the Material Editor.
# UVW map other parts using the same method.

As the texture map fills up, wireframe layers in your main texture file can be unified to a single one containing every part.
They should be left in though, as they are a great and highly accurate (+/- 1 to 2 pixels) reference for third party painters!

= Source =
http://www.fsdeveloper.com/forum/showthread.php?t=44026

[[Category:Modeling]]
[[Category:Texturing]]
[[Category:Aircraft Design]]
[[Category:Scenery Design]]

Mapping and texturing models in 3DS Max

2012-12-20T18:15:53Z

Heretic: /* In GIMP */

{{Infobox-Applicable-FSVersion
| FSXI = false
| FSXA = true
| FSX = true
| FS2004 = true
| FS2002 = true
| FS2000 = false
| FS98 = false
}}

= Introduction =

First of all, the steps covered in this tutorial are very similar to the ones decribed in "[[Texturing complex models in GMAX]]".
The difference is, that this workflow example makes use of 3DS Max superior UVW Unwrapper functionality which makes for easy and accurate part projections for texture creation.

Being a non-illustrated workflow based article, knowledge of basic 3DS Max and Image Editor functionality is required for understanding.
The programs used in this method are 3DS Max 9 and GIMP 2.6.11.

This method follows the creation of an untextured and unmapped model in 3DS Max.

= Workflow =

The section is divided into two parts, one for everything related to steps in 3DS Max and another for everything in GIMP.

== In 3DS Max ==

# First, a FSX-compilant material with a simple, single colored 2048*2048 px (or more/less resolution) diffuse map should be created. The texture should be saved in .psd format as it allows better editing.
# This material is then assigned to the first object to be textured, e.g. the fuselage.
# Then, a "UVW Map" modifier is used on the object. The settings are kept at default. (This step is probably redundant)
#* If one wants to map subparts or limited areas of the part, these should now be selected via "Edit Mesh" or "Edit Poly"
# An "Unwrap UVW" modifier is added to the stack and the UVW Unwrapper is entered
# By default, the editor should be in "Vertex" mode. In "Poly" mode (in the row of buttons below the Unwrapper window), all polys in the Unwrapper window should be selected.
# The next step is using "Tools -> Normal Mapping". The settings to choose (which side to render from) depend on the orientation of the part's pivot point, but one can try multiple times to find a useful solution. In any case,''' "Rotate Clusters" should be unticked''', as it makes things unnecessarily difficult.
# The result should be a perfect projection of the parts. They have to be scaled and moved until they are located within the bitmap boundaries (the thickly outlined blue frame).
#* Hint: "Uniform Scaling" is to be used on both parts of the projections if the parts need to be scaled. Moving or mirroring can be done independently for each part, but anything that's related to sizing has to be done for both sides as once, e.g. to line up a pattern of stripes in the nose or tail area of a fuselage. Having both parts in exactly the same scale also makes paining patterns and liveries a lot easier later on as one can just mirror the left side texture and fit it exactly to the right side with little to no scaling or further adjustment!
# Once the fitting the UVW Maps of parts to the texture or at least within the image boundaries is done, "Render UVW Texture" comes into use. In the settings dialog, it is of '''utmost importance to select "2048" for X and Y size of the texture'''. Pressing "Render" or "Go" will result in the part projection on a black texture. Selecting "Save" and ".png" and a 100% image quality as output format results in a convienient image, in which all the black parts of the texture are regarded as transparent. This, in turn, makes magic wand selection of the wireframe projection in GIMP much easier. Save the image in your project folder.

== In GIMP ==

# After the master texture file from step one above is opened in GIMP, the image file saved in step seven above is imported (opened) as a layer. It should be put above the background layer.
# A new layer for the base color should be created on top of the layer stack.
# The "Magic Wand" tool is now used on the layer with the imported wireframe of the part to be textured. Inverting the selection should have the outline of the part selected. Growing the selection by 2 to 3 pixels creates a "safety zone" to make sure that polygons at the edge will be properly textured as well.
# With the selection left intact, switching to the topmost layer in the stack and filling the selection with a simple color (a highly visible one if so desired) will create a base color for the part that can be further enhanced later on.
# After deselecting everything and saving the texture, a switch back to 3DS Max should reveal the now colored part, as Max has real-time texture file reading capabilities.
#* Should the texture change not be displayed, the texture file will have to be reloaded in the Material Editor.
# UVW map other parts using the same method.

As the texture map fills up, wireframe layers in your main texture file can be unified to a single one containing every part.
They should be left in though, as they are a great and highly accurate (+/- 1 to 2 pixels) reference for third party painters!

= Source =
http://www.fsdeveloper.com/forum/showthread.php?t=44026

[[Category:Modeling]]
[[Category:Texturing]]
[[Category:Aircraft Design]]
[[Category:Scenery Design]]

Makemdl

2012-12-20T17:59:48Z

Heretic:

MakeMDL is the primary compiler for objects created for Microsoft's Flight Simulator 9

In its latest iteration, available in the MakeMDL SDK [http://download.microsoft.com/download/1/1/8/1181a250-ac2c-43fa-b35b-bfd7b87934ad/makemdl_sdk_setup.exe] for FS9, it supports input commands via a file named "makemdl.cfg".
Normally, this file is located in the same folder in which MakeMDL.exe resides, e.g. "C:\gmax\gamepacks\fs2004\plugins"
 
== Sample MakeMDL.cfg ==

[Settings] 
LastDir= 
SaveDir=''C:\gmax\GAMEPA~1\FS2004\plugins''''' 

[Options] 
Debug=1 
ViewLog=0 
KeepErrorLog=1 
Keep=0 
I8=1 
I=0 
FullMat=1 
Deffallback=1 
WeldPoints=0 
Optimize=0 
Flatten=0 
NoAnimate=0 
HasReflectMap=1 
HasNightMap=0 
HasLightMap=1 
HasDamageMap=0 
NegateZ=1 
NoLeftToRight=0 
SwapBH=0 
Vis=0 
Crash=0 
XML=1 
 
== Makemdl.cfg entries explained ==

Of special interest to avid modellers for FS9 are the "Debug", "KeepErrorLog", "WeldPoints", "Optimize" and "Flatten" settings. 
;Debug: Set to "1" (no quote marks) to enable debug functionality 
;ViewLog: Automatically opens the log file after compilation if set to "1" 
;KeepErrorLog: Does not delete the log file if set to "1"; useful for finding erroneous parts or animations 
;Keep: Does not delete temporary files created during compilation if set to "1" 
;I8: ??? 
;I: ??? 
;FullMat: ??? 
;Deffallback: ??? 
 
The next three settings can be a cure to the 4mm vertex weld issue otherwise present for FS9 models (very notable and annoying in virtual cockpits)! 

;WeldPoints: Disable vertex welding if set to "1". 
;Optimize: Does not optimize the mesh if set to "0" 
;Flatten: Set to "0" 
;NoAnimate: Does not parse animations during compilation if set to "1" 
;HasReflectMap: Set to "1" to enable reflectivity for the model. Make sure to put a "_t" suffix into the texture's file name, e.g. "fuselage_t.bmp" and make sure "Reflections" is enabled in FS9's "display" menu.
;HasNightMap: Enables use of auto-enabled night textures ("_lm" suffix, i.e. "tower_lm.bmp") if set to "1". You won't need to fill the "self-illumination" slot of the material in GMax. Useful for scenery design!
;HasLightMap: Enables use of self-illumination night textures ("_l" suffix, i.e. "fuselage_l.bmp") if set to "1". You won't need to fill the "self-illumination" slot of the material in GMax. Useful for aircraft design!
;HasDamageMap: Enables damage textures if set to "1". Not needed for FS9.
;NegateZ: If your object appears upside down in FS9, set this to "1"
;NoLeftToRight: ???
;SwapBH: ???
;Vis: ???
;Crash: ???

[[category:Modelling]]

Makemdl

2012-12-20T17:59:29Z

Heretic:

MakeMDL is the primary compiler for objects created for Microsoft's Flight Simulator 9

In its latest iteration, available in the MakeMDL SDK [http://download.microsoft.com/download/1/1/8/1181a250-ac2c-43fa-b35b-bfd7b87934ad/makemdl_sdk_setup.exe] for FS9, it supports input commands via a file named "makemdl.cfg".
Normally, this file is located in the same folder in which MakeMDL.exe resides, e.g. "C:\gmax\gamepacks\fs2004\plugins"

== Sample MakeMDL.cfg ==

[Settings] 
LastDir= 
SaveDir=''C:\gmax\GAMEPA~1\FS2004\plugins''''' 

[Options] 
Debug=1 
ViewLog=0 
KeepErrorLog=1 
Keep=0 
I8=1 
I=0 
FullMat=1 
Deffallback=1 
WeldPoints=0 
Optimize=0 
Flatten=0 
NoAnimate=0 
HasReflectMap=1 
HasNightMap=0 
HasLightMap=1 
HasDamageMap=0 
NegateZ=1 
NoLeftToRight=0 
SwapBH=0 
Vis=0 
Crash=0 
XML=1 
 
 

== Makemdl.cfg entries explained ==

Of special interest to avid modellers for FS9 are the "Debug", "KeepErrorLog", "WeldPoints", "Optimize" and "Flatten" settings. 
;Debug: Set to "1" (no quote marks) to enable debug functionality 
;ViewLog: Automatically opens the log file after compilation if set to "1" 
;KeepErrorLog: Does not delete the log file if set to "1"; useful for finding erroneous parts or animations 
;Keep: Does not delete temporary files created during compilation if set to "1" 
;I8: ??? 
;I: ??? 
;FullMat: ??? 
;Deffallback: ??? 
 
The next three settings can be a cure to the 4mm vertex weld issue otherwise present for FS9 models (very notable and annoying in virtual cockpits)! 

;WeldPoints: Disable vertex welding if set to "1". 
;Optimize: Does not optimize the mesh if set to "0" 
;Flatten: Set to "0" 
;NoAnimate: Does not parse animations during compilation if set to "1" 
;HasReflectMap: Set to "1" to enable reflectivity for the model. Make sure to put a "_t" suffix into the texture's file name, e.g. "fuselage_t.bmp" and make sure "Reflections" is enabled in FS9's "display" menu.
;HasNightMap: Enables use of auto-enabled night textures ("_lm" suffix, i.e. "tower_lm.bmp") if set to "1". You won't need to fill the "self-illumination" slot of the material in GMax. Useful for scenery design!
;HasLightMap: Enables use of self-illumination night textures ("_l" suffix, i.e. "fuselage_l.bmp") if set to "1". You won't need to fill the "self-illumination" slot of the material in GMax. Useful for aircraft design!
;HasDamageMap: Enables damage textures if set to "1". Not needed for FS9.
;NegateZ: If your object appears upside down in FS9, set this to "1"
;NoLeftToRight: ???
;SwapBH: ???
;Vis: ???
;Crash: ???

[[category:Modelling]]

Makemdl

2012-12-20T17:58:57Z

Heretic:

== Basics ==

MakeMDL is the primary compiler for objects created for Microsoft's Flight Simulator 9

In its latest iteration, available in the MakeMDL SDK [http://download.microsoft.com/download/1/1/8/1181a250-ac2c-43fa-b35b-bfd7b87934ad/makemdl_sdk_setup.exe] for FS9, it supports input commands via a file named "makemdl.cfg".
Normally, this file is located in the same folder in which MakeMDL.exe resides, e.g. "C:\gmax\gamepacks\fs2004\plugins"

== Sample MakeMDL.cfg ==

[Settings] 
LastDir= 
SaveDir=''C:\gmax\GAMEPA~1\FS2004\plugins''''' 

[Options] 
Debug=1 
ViewLog=0 
KeepErrorLog=1 
Keep=0 
I8=1 
I=0 
FullMat=1 
Deffallback=1 
WeldPoints=0 
Optimize=0 
Flatten=0 
NoAnimate=0 
HasReflectMap=1 
HasNightMap=0 
HasLightMap=1 
HasDamageMap=0 
NegateZ=1 
NoLeftToRight=0 
SwapBH=0 
Vis=0 
Crash=0 
XML=1 

----
 
 

== Makemdl.cfg entries explained ==

Of special interest to avid modellers for FS9 are the "Debug", "KeepErrorLog", "WeldPoints", "Optimize" and "Flatten" settings. 
;Debug: Set to "1" (no quote marks) to enable debug functionality 
;ViewLog: Automatically opens the log file after compilation if set to "1" 
;KeepErrorLog: Does not delete the log file if set to "1"; useful for finding erroneous parts or animations 
;Keep: Does not delete temporary files created during compilation if set to "1" 
;I8: ??? 
;I: ??? 
;FullMat: ??? 
;Deffallback: ??? 
 
The next three settings can be a cure to the 4mm vertex weld issue otherwise present for FS9 models (very notable and annoying in virtual cockpits)! 

;WeldPoints: Disable vertex welding if set to "1". 
;Optimize: Does not optimize the mesh if set to "0" 
;Flatten: Set to "0" 
;NoAnimate: Does not parse animations during compilation if set to "1" 
;HasReflectMap: Set to "1" to enable reflectivity for the model. Make sure to put a "_t" suffix into the texture's file name, e.g. "fuselage_t.bmp" and make sure "Reflections" is enabled in FS9's "display" menu.
;HasNightMap: Enables use of auto-enabled night textures ("_lm" suffix, i.e. "tower_lm.bmp") if set to "1". You won't need to fill the "self-illumination" slot of the material in GMax. Useful for scenery design!
;HasLightMap: Enables use of self-illumination night textures ("_l" suffix, i.e. "fuselage_l.bmp") if set to "1". You won't need to fill the "self-illumination" slot of the material in GMax. Useful for aircraft design!
;HasDamageMap: Enables damage textures if set to "1". Not needed for FS9.
;NegateZ: If your object appears upside down in FS9, set this to "1"
;NoLeftToRight: ???
;SwapBH: ???
;Vis: ???
;Crash: ???

[[category:Modelling]]

Makemdl

2012-12-20T17:48:34Z

Heretic: /* Sample MakeMDL.cfg */

== Basics ==

MakeMDL is the primary compiler for objects created for Microsoft's Flight Simulator 9

In its latest iteration, available in the MakeMDL SDK [http://download.microsoft.com/download/1/1/8/1181a250-ac2c-43fa-b35b-bfd7b87934ad/makemdl_sdk_setup.exe] for FS9, it supports input commands via a file named "makemdl.cfg".
Normally, this file is located in the same folder in which MakeMDL.exe resides, e.g. "C:\gmax\gamepacks\fs2004\plugins"

== Sample MakeMDL.cfg ==

[Settings] 
LastDir= 
SaveDir=''C:\gmax\GAMEPA~1\FS2004\plugins''''' 

[Options] 
Debug=1 
ViewLog=0 
KeepErrorLog=1 
Keep=0 
I8=1 
I=0 
FullMat=1 
Deffallback=1 
WeldPoints=0 
Optimize=0 
Flatten=0 
NoAnimate=0 
HasReflectMap=1 
HasNightMap=0
;HasLightMap=1
;HasDamageMap=0
;NegateZ=1
;NoLeftToRight=0
;SwapBH=0
;Vis=0
;Crash=0
;XML=1

----
=== Installation ===

== Makemdl.cfg entries explained ==

Of special interest to avid modellers for FS9 are the "Debug", "KeepErrorLog", "WeldPoints", "Optimize" and "Flatten" settings. 
;Debug: Set to "1" (no quote marks) to enable debug functionality 
;ViewLog: Automatically opens the log file after compilation if set to "1" 
;KeepErrorLog: Does not delete the log file if set to "1"; useful for finding erroneous parts or animations 
;Keep: Does not delete temporary files created during compilation if set to "1" 
;I8: ??? 
;I: ??? 
;FullMat: ??? 
;Deffallback: ??? 
 
The next three settings can be a cure to the 4mm vertex weld issue otherwise present for FS9 models (very notable and annoying in virtual cockpits)! 

;WeldPoints: Disable vertex welding if set to "1". 
;Optimize: Does not optimize the mesh if set to "0" 
;Flatten: Set to "0" 
;NoAnimate: Does not parse animations during compilation if set to "1" 
;HasReflectMap: Set to "1" to enable reflectivity for the model. Make sure to put a "_t" suffix into the texture's file name, e.g. "fuselage_t.bmp" and make sure "Reflections" is enabled in FS9's "display" menu.
;HasLightMap: Enables use of self-illumination night textures ("_l" suffix, i.e. "fuselage_l.bmp") if set to "1". You won't need to fill the "self-illumination" slot of the material in GMax.

[[category:Modelling]]

Makemdl

2012-12-20T17:39:58Z

Heretic: /* MakeMDL.cfg */

== Basics ==

MakeMDL is the primary compiler for objects created for Microsoft's Flight Simulator 9

In its latest iteration, available in the MakeMDL SDK [http://download.microsoft.com/download/1/1/8/1181a250-ac2c-43fa-b35b-bfd7b87934ad/makemdl_sdk_setup.exe] for FS9, it supports input commands via a file named "makemdl.cfg".
Normally, this file is located in the same folder in which MakeMDL.exe resides, e.g. "C:\gmax\gamepacks\fs2004\plugins"

== Sample MakeMDL.cfg ==

[Settings] 
LastDir= 
SaveDir=''C:\gmax\GAMEPA~1\FS2004\plugins''''' 

[Options] 
Debug=1 
ViewLog=0 
KeepErrorLog=1 
Keep=0 
I8=1 
I=0 
FullMat=1 
Deffallback=1 
WeldPoints=0 
Optimize=0 
Flatten=0 
NoAnimate=0 
HasReflectMap=1 
;HasNightMap=0
;HasLightMap=1
;HasDamageMap=0
;NegateZ=1
;NoLeftToRight=0
;SwapBH=0
;Vis=0
;Crash=0
;XML=1

Of special interest to avid modellers for FS9 are the "Debug", "KeepErrorLog", "WeldPoints", "Optimize" and "Flatten" settings. 
;Debug: Set to "1" (no quote marks) to enable debug functionality 
;ViewLog: Automatically opens the log file after compilation if set to "1" 
;KeepErrorLog: Does not delete the log file if set to "1"; useful for finding erroneous parts or animations 
;Keep: Does not delete temporary files created during compilation if set to "1" 
;I8: ??? 
;I: ??? 
;FullMat: ??? 
;Deffallback: ??? 

; 
The next three settings can be a cure to the 4mm vertex weld issue otherwise present for FS9 models (very notable and annoying in virtual cockpits)

;WeldPoints: Disable vertex welding if set to "1". 
;Optimize: Does not optimize the mesh if set to "0" 
;Flatten: Set to "0" 
 
;NoAnimate: Does not parse animations during compilation if set to "1" 
;HasReflectMap: Set to "1" to enable reflectivity for the model. Make sure to put a "_t" suffix into the texture's file name, e.g. "fuselage_t.bmp" and make sure "Reflections" is enabled in FS9's "display" menu.

[[category:Modelling]]

Makemdl

2012-12-20T17:28:30Z

Heretic: /* MakeMDL.cfg */

Makemdl

2012-12-20T17:22:48Z

Heretic: /* Basics */