Missing textures: Difference between revisions

From FSDeveloper Wiki
Jump to navigationJump to search
mNo edit summary
Line 1: Line 1:
{{Infobox-Applicable-FSVersion
== Overview ==
| FSXI = false
Missing textures for aircraft / scenery will impact on FSX performance.<br>
| FSXA = true
| FSX = true
| FS2004 = false
| FS2002 = false
| FS2000 = unknown
| FS98 = unknown
}}
'''Overview'''
<br>
Missing textures for aircraft / scenery will impact on FSX performance.
<br>
Possibly resulting in -
Possibly resulting in -
* Objects rendered as transparent.
* Objects rendered as transparent.
Line 17: Line 6:
* Screen artifacting
* Screen artifacting
* Reduced FPS.
* Reduced FPS.
* Font corruption on main and context menus, ATC window, kneeboard page titles.


The above issues can be caused by, (or further exacerbated),
<br>
if the -
* texture.'''EXT''' called by the model, differs from that present in the repaint folder.
* texture is of a '''non-DXT''' format.
<br>
== Causes ==
== Causes ==
* File is missing from the relevant texture folder
* File is missing from the relevant texture folder
* Missing  '''[[Texture.cfg - FSX|texture.cfg]]'''
* Missing  '''[[Texture.cfg - FSX|texture.cfg]]'''
* Incorrectly configured '''[[Texture.cfg - FSX|texture.cfg]]''' (FSX default a/c texture.cfg file is wrong)
* Incorrectly configured '''[[Texture.cfg - FSX|texture.cfg]]'''
* Model is calling a file from the common texture folder, (e.g. envmaps).


== Simobject texture search paths ==
== Identifying ==
In FSX/FSXA, the search mechanism for locating any simobject's texture
Identify the filename of missing textures for both aircraft & scenery.
<br>
behaves as follows, and continues until a matching texture is located, or the cycle is completed.
 
Entire cycle is repeated '''for every texture called by the model'''.
 
=== Searches For ===
1) '''file.ext - As explicitly defined in the model.'''
<br>
2) a matching .CAB file, (if CAB exists, will then search contents).
<br>
3) .ext of opposite type, (i.e. if 1) was a .bmp, searches for . dds, and vice-versa).
<br>
4) repeats 2) for the matching .CAB file, then searches for 3).
 
 
If not found during steps 1-4),
<br>
FSX/FSXA then repeats '''every''' step above
<br>
for each fallback path defined, in a correctly written texture.cfg
 
i.e. steps through -
<br>
fallback.1=..\texture
<br>
fallback.2=..\..\..\..\Scenery\Global\texture
<br>
fallback.3=..\..\..\..\Texture
 
 
The search sequence will repeat whenever the model requires a reload.
<br>
e.g. If the viewport is cycled from VC/2D to external.
 
=== Example ===
An IRL FSX/FSXA example for an airplane model calling a ''.bmp'' texture.
 
==== Methodology ====
For this example -
<br>
The '''FINDME.bmp''' texture was deliberately removed from the system,
<br>
to force FSX to perform a '''full search-path traverse'''.


I/O operation QueryOpen actions by fsx.exe, each resulted in a '''NAME NOT FOUND''' error.
Adding the following lines to your fsx.CFG in the section titled <nowiki>[SCENERY]</nowiki><br>
 
will display an FSX alert dialog identifiying the missing file / object, or render trigger areas.
The first 4 paths listed, are for the aircraft's ''native'' folder.
 
Each subsequent group of 4 paths,is for each of the 3 fallback paths.
 
==== Key ====
In the ''ProcMon'' logfile extract below -
* MYFSXPATH - my drive & path to FSX's root folder, (concatenated for clarity).
* TESTAIRCRAFT - The aircraft folder.
* LIVERY - The repaint folder.
* FINDME.bmp - The texture named in the model
 
==== Logfile data ====
Search path file-calls for the missing FINDME.BMP texture, (with a valid texture.cfg).
<pre>
MYFSXPATH\SimObjects\Airplanes\TESTAIRCRAFT\texture.LIVERY\FINDME.bmp
MYFSXPATH\SimObjects\Airplanes\TESTAIRCRAFT\texture.LIVERY.CAB
MYFSXPATH\SimObjects\Airplanes\TESTAIRCRAFT\texture.LIVERY\FINDME.DDS
MYFSXPATH\SimObjects\Airplanes\TESTAIRCRAFT\texture.LIVERY.CAB
 
MYFSXPATH\SimObjects\Airplanes\TESTAIRCRAFT\texture\FINDME.bmp
MYFSXPATH\SimObjects\Airplanes\TESTAIRCRAFT\texture.CAB
MYFSXPATH\SimObjects\Airplanes\TESTAIRCRAFT\texture\FINDME.DDS
MYFSXPATH\SimObjects\Airplanes\TESTAIRCRAFT\texture.CAB
 
MYFSXPATH\Scenery\Global\Texture\FINDME.bmp
MYFSXPATH\Scenery\Global\Texture.CAB
MYFSXPATH\Scenery\Global\Texture\FINDME.DDS
MYFSXPATH\Scenery\Global\Texture.CAB
 
MYFSXPATH\Texture\FINDME.bmp
MYFSXPATH\Texture.CAB
MYFSXPATH\Texture\FINDME.DDS
MYFSXPATH\Texture.CAB
</pre>
 
'''That's a lot of disk thrashing.'''
<br>
All CPU cycles utilised detract from FSX/FSXA FPS.
 
== Identifying ==
To identify the filename of missing textures, (simobject or scenery),
<br>
add the following lines to your fsx.CFG into the section titled <nowiki>[SCENERY]</nowiki>.
<pre>
<pre>
[SCENERY]
[SCENERY]
Line 136: Line 31:
ShowTriggers=1
ShowTriggers=1
</pre>
</pre>
FSX will now display an alert dialog identifiying the missing file / object, or render trigger areas.
== Related ==


=== Internal ===
== Related content ==
{{Template:Navbox-Textur-Related}}
[[Texture.cfg - FSX]]


=== External ===
== External links ==
Placeholder text
Placeholder text


[[category:Aircraft_Design]]
[[category:Aircraft Design]]
[[category:Scenery_Design]]
[[category:Scenery Design]]
[[category:Missions]]
[[category:Missions]]
[[Category:Texturing]]

Revision as of 07:36, 6 August 2009

Overview

Missing textures for aircraft / scenery will impact on FSX performance.
Possibly resulting in -

  • Objects rendered as transparent.
  • Objects rendered as disassociated components.
  • Screen artifacting
  • Reduced FPS.

Causes

Identifying

Identify the filename of missing textures for both aircraft & scenery.

Adding the following lines to your fsx.CFG in the section titled [SCENERY]
will display an FSX alert dialog identifiying the missing file / object, or render trigger areas.

[SCENERY]
// To show alerts or areas, set to = 1 
// To hide alerts or areas, set to = 0 

// Alert for missing textures
ShowMissingTextureAlert=1

// Alert for missing objects
MissingLibraryAlert=1

// Render Trigger areas as visible boxes
ShowTriggers=1	

Related content

Texture.cfg - FSX

External links

Placeholder text