ANSWERED Missing textures in FTX Global/Vector

[B77X]

Hi, why are there so many unknown files being searched for constantly?

 

[Wolter van der Spoel]

Hi David,

just blurting this out doesn't add for us to give a proper answer,

If you could be more informative about your issue we might be able to assist you better resolving your "problem"

so please state:

Which SIM are we talking about, fsX, P3dvx.x, fsX SE

Which OS you are using

info on your hardware is also beneficial

add some screenshots as to where you have an issue

looking at your screenshot you have installed something and then moved or deleted them as the system can't find them anymore

the software looks for the files as they are noted to have been installed on the listed location, otherwise it is impossible to list them at all, as simple as that

[Holger Sandmann]

Hi there,

 

actually, that's perfectly normal behavior, and those aren't textures but rather autogen placement files. In FS9 there was an issue that missing landclass textures and .agn files would cause repeated RAM allocation without release; a so-called memory leak. In FSX the code was changed so that there is an iterative search tree meaning if FSX can't find the files in the local add-on folder it'll look for it in the main folders, like \Scenery\World\texture and without allocating RAM. Thus, even if the file is logged as not found it's actually loaded from the next folder in the search hierarchy. For example, 043b2an2.agn isn't found in \ORBX\FTX_OLC\OLC_EU6\Texture but is found in \Scenery\World\Texture.

 

Moreover, another change from FS9 is that FSX assumes autogen placement files for all ground texture sets, including waterclass (!); those are the 300 series agn files. Again, if it doesn't find these files the display engine correctly assumes to not display any autogen without further consequence. It's logged as a file-not-found but isn't actually a technical or display issue, rather like a false positive in an AV checker.

 

In short, while ProcessMonitor can be a great diagnostic tool the long output logs can look rather scary if one doesn't know what the output means; as they say a little knowledge is a dangerous thing...

 

Cheers, Holger

[B77X]

Hi there,

 

actually, that's perfectly normal behavior, and those aren't textures but rather autogen placement files. In FS9 there was an issue that missing landclass textures and .agn files would cause repeated RAM allocation without release; a so-called memory leak. In FSX the code was changed so that there is an iterative search tree meaning if FSX can't find the files in the local add-on folder it'll look for it in the main folders, like \Scenery\World\texture and without allocating RAM. Thus, even if the file is logged as not found it's actually loaded from the next folder in the search hierarchy. For example, 043b2an2.agn isn't found in \ORBX\FTX_OLC\OLC_EU6\Texture but is found in \Scenery\World\Texture.

 

Moreover, another change from FS9 is that FSX assumes autogen placement files for all ground texture sets, including waterclass (!); those are the 300 series agn files. Again, if it doesn't find these files the display engine correctly assumes to not display any autogen without further consequence. It's logged as a file-not-found but isn't actually a technical or display issue, rather like a false positive in an AV checker.

 

In short, while ProcessMonitor can be a great diagnostic tool the long output logs can look rather scary if one doesn't know what the output means; as they say a little knowledge is a dangerous thing...

 

Cheers, Holger

 

Ok thanks. I am trying to fix my OOM problem but this isn't it apparently.

[B77X]

Hi there,

 

actually, that's perfectly normal behavior, and those aren't textures but rather autogen placement files. In FS9 there was an issue that missing landclass textures and .agn files would cause repeated RAM allocation without release; a so-called memory leak. In FSX the code was changed so that there is an iterative search tree meaning if FSX can't find the files in the local add-on folder it'll look for it in the main folders, like \Scenery\World\texture and without allocating RAM. Thus, even if the file is logged as not found it's actually loaded from the next folder in the search hierarchy. For example, 043b2an2.agn isn't found in \ORBX\FTX_OLC\OLC_EU6\Texture but is found in \Scenery\World\Texture.

 

Moreover, another change from FS9 is that FSX assumes autogen placement files for all ground texture sets, including waterclass (!); those are the 300 series agn files. Again, if it doesn't find these files the display engine correctly assumes to not display any autogen without further consequence. It's logged as a file-not-found but isn't actually a technical or display issue, rather like a false positive in an AV checker.

 

In short, while ProcessMonitor can be a great diagnostic tool the long output logs can look rather scary if one doesn't know what the output means; as they say a little knowledge is a dangerous thing...

 

Cheers, Holger

 

last question, why are OpenLC Europe files being called for if I am sitting at an airport in the middle east?

[wingclip]

OpenLC EU covers a vast area and if you check the manual real quick, it'll show you exactly what areas it does affect. The "Middle East" is pretty large and I can't recall how much of OpenLC EU may, or may not affect it. Perhaps you can filter that location down a little?

Rich

[Holger Sandmann]

Hi David,

 

OpenLC Europe reaches to southern Turkey and Cyprus. With FSX/P3D loading landclass files in QMID7 raster blocks or larger (which span ~200 mi on each side), I wouldn't be surprised if at least parts of the Middle East are within the "viewshed" of openLC EU. Moreover, your LOD_RADIUS setting would have an impact on how far away from the user aircraft detailed landscape components, including terrain mesh and landclass, are loaded.

 

Cheers, Holger