Hi allI know this might sound trivial but this problem has been bugging me a bit lately - the textures seem to have disappeared on my rwy12 static aircraft (the ones made by the late Seev Kahn) and these appear grey. It seems to mainly be a problem in the addon scenery from John B Loney for some reason, although all the other objects are fine as are the AI aircraft. This is annoying me a bit and, much as though I would like to, I can't ignore it, but have failed to find a solution. Has anyone had a similar problem or can anyone help please?BillWindows XP Pro SP2; Intel Core 2 Duo E6850 3.0Ghz CPU; Arctic Cool 7Pro; ASUS P5N-E-SLI Motherboard; 2GB Corsair 800Mhz DDR2 RAM; 768MB nVidia GeForce 8800GTX Dual VGA Graphics card; 2x 500GB SATA 7200RPM Hard Drive; 650W (2 x 12V) PSU; 1000GB Western Digital External Hard Drive; 150GB Western Digital External Hard Drive; CH Pro Yoke and PedalsAll powering 240GB of fs9 escapism!

Library objects being displayed without textures is commonly the result of having the object library located in an active scenery folder without the textures in the associated texture folder.Developers will include library object .bgl files and not include all the textures without realizing this can have a negative impact on sceneries beyond theirs.You need to search your system for two files.add_SeevKahn.BGL andga planes.bglEvery instance you find of either of those files should have 53 textures in the associated texture folder. They all have filenames something like sk_aircrafttype_*.bmpYou only need one copy of each .bgl and a texture set for each, in an active scenery folder. Preferably not in a local scenery folder that you might someday delete.Search for those files and post back with your results.regards,Joe

I had this same problem long ago and solved it by copy/pasting ALL textures from the "Static Object Library" texture folder to the main FS9 texture folder. Overwrite ? Yes. However, for safety reasons you may want to backup your main FS9 texture folder first.Yes, it means creating duplicate textures within your FS9 but it also means that you can now transfer (cut/paste) your newly created rwy12 .bgl file(s) from your "Static Object Library" scenery folder to the specific airport's (where you wanted the rwy12 objects to appear) scenery folder(s). Be careful though because if by chance, the to be transferred .bgl file name already exists in the destination scenery folder, then DO NOT overwrite it but rename it or the to be transferred file name first.When you're done and ALL your objects are displayed correctly, you can now also delete the remaining .xml file (created by rwy12) from the same "Static Object Library" scenery folder.I've been doing this routinely for years.Good luckHans

I had this same problem long ago and solved it by copy/pasting ALL textures from the "Static Object Library" texture folder to the main FS9 texture folder. Overwrite ? Yes. However, for safety reasons you may want to backup your main FS9 texture folder first.Yes, it means creating duplicate textures within your FS9 but it also means that you can now transfer (cut/paste) your newly created rwy12 .bgl file(s) from your "Static Object Library" scenery folder to the specific airport's (where you wanted the rwy12 objects to appear) scenery folder(s). Be careful though because if by chance, the to be transferred .bgl file name already exists in the destination scenery folder, then DO NOT overwrite it but rename it or the to be transferred file name first.When you're done and ALL your objects are displayed correctly, you can now also delete the remaining .xml file (created by rwy12) from the same "Static Object Library" scenery folder.I've been doing this routinely for years.Good luckHans

Thanks guys - I really appreciate your help! Joe, I did a search for the 2 files (add_SeevKahn and ga planes) and found that there were a lot of them in various active scenery folders. Rather than copying the 53 texture files into each of these active scenery folders, I copied them into the fs9 main texture folder, as suggested by Hans, and this has solved the problem - the static aircraft are now in colour again rather than boring grey!My thanks again to both of you for your very helpful replies!Kind regards,Bill

MS says it's dangerous to have more than one given library BGL file loaded into the sim at once (something about identical GUID numbers), but I haven't seen any problems. But I do try to weed them out as I find them - you only need one.Hope this helps,

While dumping all the texture files into ...\FS9\Texture will solve the issue it does open the door to a different one.Object libraries call for textures by filename.Windows will only allow one file in a folder with any given filename.Different objects use textures with the same filename.So which one do you use?

...just to continue my post above...While the shipping container doesn't look too bad with the wrong texture......the container ship looks mighty odd......and finally, yes, today I have too much time on my hands.regards,Joe

...just to continue my post above...While the shipping container doesn't look too bad with the wrong texture......the container ship looks mighty odd......and finally, yes, today I have too much time on my hands.regards,Joe

Hi JoeI see the problem! Hopefully however it will not cause me too much trouble as the only textures I put in the fs9 texture folder were the Seev Kahn aircraft (sk_aircrafttype_*.bmp) textures - fingers crossed!Wish I had time to play around with containers and container ships too - I need to retire!!Kind regards,Bill

MS says it's dangerous to have more than one given library BGL file loaded into the sim at once (something about identical GUID numbers), but I haven't seen any problems. But I do try to weed them out as I find them - you only need one.Hope this helps,

That's not so much of a problem if the two .bgls are identical (although it can cause difficulties as first raised in this discussion) but different .bgl files using the same GUID can cause interesting results - I had some sceneries where huge jetways appeared in place of the boundary fence!But I absolutely agree it is sensible to weed duplicates out. Personally, I keep all "common" library files in their own communal directory structure and delete them from the sceneries that so many designers distribute them with.John