Hi,This has probably been covered before, but my search did not turn up anything along the lines I am looking for.I am using Flightsim Manager 2.85. I ran the "duplicate texture" thingy. It came up with a list of a bunch of duplicates. I removed them. But in the process, I found...There are a bunch of files with the same name and they look the same but some have different sizes of textures in scenerygenerictexture and in texture.What's up? Should I remove the ones from texture? I don't know if they were there from the original install, or if some scenery installed them. I tend towards that they were there, as the only files I added to texture (I think) are the novanovagoldnovasimAFW textures. I'll have to go back and look at these setups to see if I see these files. Funny thing is, FSM didn't find them all. It found sco_noaa_smokestack2b.bmp but missed sco_noaa_antenna2.bmp (different sizes) and SCO_noaa_cooltower1.bmp (same sizes).Should I leave these as is or instead remove them from the other default directories, leaving them in texture? (I'm thinking perhaps that some other scenery will need them and won't know to look in scenerygenericscenery).Ug.Is there a tool that looks for missing texture files? IOW, searches BGL's for all texture file references and looks in the appropriate directories for those files?Is there a better duplicate file finder? One that searches for files with the same names but possibly different sizes that occur in default directories and others?Is there a tool that does both of these functions?Thanks,Thomas

As an interesting note: I tried the filemon.exe program noted in another thread, started a flight in a dreamfleet pa28 at KASH (Nashu, NH - sceneryname) and found some files FS9.exe could not find were the following:006b2an7.agn006b2an6.agn006b2an5.agn006b2an4.agn006b2an2.agn006b2an1.agn141b2an1.agn139b2an1.agn136b2an1.agn140b2an1.agn142b2an1.agnAnyone recognize these files?Thanks,Thomas

To start with, I would recommend that you do not remove any texture files, even if they appear to be duplicates. When you fly into a scenery area, and FS loads an object, it will look for the textures for that object in the corresponding texture directory. If it doesn't find them, then it won't (... errr, might not) display any texture.There a few reasons that you have duplicate textures. One is that many designers share library objects, so common things like trees, or cars, or whatever might get re-used over and over again by different designers in different sceneries. Ideally, we would place all these common libraries and textures in a central location so that when a particular scenery wanted to load that tree, it would look up the guid, find it in the "global" directory, and then load it. This worked really well with Gerrish Grey's tree library which was used by many designers. It has the added benefit of reducing download times, although this isn't so much of an issue nowadays. Similarly, we used to download textures for AFW and ASD so that the designers wouldn't have to include these files with their scenery. With the release of EZ-Scenery (by Abacus), we are again confronted with the idea of downloading scenery libraries once so that they can be used by different designers who don't have to worry about distributing these files. However, sometimes it is a lot to ask an average user to go to the trouble of downloading these library and texture files seperately, and then the scenery doesn't look right in FS (not everyone reads the readme files too). This is often followed up with a nasty email to the designer complaining that the scenery doesn't work. So, to keep things simple, we usually include all necessary files with the scenery, and don't rely on the user to do any extra work. This is a long explanation as to why you have duplicate texture files, and why you might as well keep them.The other files appear to be autogen annotation files. - Martin

Hello,I use this tool for months with success but I do not remberber where I did find it !!

Hi all,>Hello,>I use this tool for months with success but I do not remberber>where I did find it !!http://library.avsim.net/esearch.php?DLID=...rand&CatID=roothttp://sales.hifisim.com/pub-download/asv6-banner-beta.jpgPatrick/EBBR

Regarding the textures - so it is your belief that having duplicate textures is not an issue?*************Regarding the missing autogen files:I checked the distrubution disks and these files don't exist there either. Does FS automatically look for autogen files for a given range, and move on if they don't exist? Is there a timeout period that is causing longer load times because it can't find these files?Is this ok, just normal action by FS, or does it cause a problem? I do notice that FS repeatedly looks for these missing files. Was it an error that they weren't put on the distribution and they should be there?the 006b2 textures look like grass or airport background textures. Probably shouldn't be autogen here. Wonder why FS is looking for them?

Oh,when I said I removed them, I meant that I made sure the duplicates existed in Texture, and then backed up the duplicates found in the addon sceneryxxxtexture directories.I'm assuming that FS first looks in the local texture directory and loads from there, but if it doesn't find them there, then looks in the texture directory and loads from there if it finds them there.Is it better just to leave the duplicate textures? Perhaps that process of looking, not finding, looking elsewhere slows the process? If multiple sceneries use the same texture, and it loads from multiple places, does FS know they are the same and not load it a second time, or is it wasting memory space by loading the same texture twice?

>Oh,>when I said I removed them, I meant that I made sure the>duplicates existed in Texture, and then backed up the>duplicates found in the addon sceneryxxxtexture>directories.>>I'm assuming that FS first looks in the local texture>directory and loads from there, but if it doesn't find them>there, then looks in the texture directory and loads from>there if it finds them there.>>Is it better just to leave the duplicate textures? Perhaps>that process of looking, not finding, looking elsewhere slows>the process? If multiple sceneries use the same texture, and>it loads from multiple places, does FS know they are the same>and not load it a second time, or is it wasting memory space>by loading the same texture twice?There shouldn't be any issue with you leaving the textures where they are, except that they will be using up extra disk space. It's just not "effecient", that's all.It is better to leave the textures due to the way that FS looks for textures when it loads objects. When FS tries to display a 3D object, it looks up the GUID (a number) for that object to see if it's already loaded into memory. If it is not, then it starts looking through your scenery folders until it finds it. When it does find it, FS searches through the associated texture folder for the textures to display on the object. It doesn't look in other texture folders for that texture, since that doesn't make sense to FS. At least, this is how it is supposed to work. There are many other issues, like what if you have two different textures but with the same name - I'm not sure if FS is ok with loading it twice.In any case, leaving the textures alone will not slow down your system, and will ensure that your scenery is displayed properly. - Martin

Thanks Patrick.

Hi!There is a very nice and powerfull program to find duplicate texture files in FS9, named JAB04, to be found on www.jacky.brouze.ch. It compares files bit by bit and not only files with same names or sizes.Try it it is free.Jean-Pierre