July 31, 200916 yr So you renamed you "Addon Scenery" folder to something different, and you created a new "Addon Scenery" folder containing an empty "Scenery" and "Texture" folder. You made a backup copy of your scenery.cfg file then removed everything in it except for the 39 default FS9 entries. You then added Gary's KLSC as I suggested in the other post and it still doesn't display correctly?OK, we're going hard core here now...do this...1 Copy everything from the "Flight Simulator 9\Addon Scenery\scenery" folder into the "Flight Simulator 9\Addon Scenery\slc\scenery" folder.2 Copy everything from the "Flight Simulator 9\Addon Scenery\texture" folder to the "Flight Simulator 9\Addon Scenery\slc\texture" folder.Start a flight at KSLC and let me know what happens. By the way, make sure this is done after you've done everything in the first paragraph of this message! Have patience, we will find out what's going on here. Like I said, I simply installed it to Gary's instruction with the exception of the effects texture being placed in the correct location. Gary messed up a bit on that.I think you may have duplicate bgl and textures in your global scenery and/or your global texture folders.Mark
July 31, 200916 yr Author Like I said, I did it a little different then the method you suggested but basically accomplished the same thing. I had already removed what items I had in Addon Scenery\Scenery and Texture and made sure no duplicate files exist.If I new which particular files were for the areas with the white boxes and the terminals I might have a better place to start. I believe Gary said the files ramp.bmp and ramp2.bmp were part of them but I have looked at those and can't see a problem.
July 31, 200916 yr Well, you really should remove everything in your scenery.cfg file except the default FS9 entries. If you do that, then the only thing between your scenery and FS9 displaying it will be the global scenery folders, the global texture folder, and your FS9.cfg file. If there is an issue after that, then you might possibly have a corrupted dll in your modules folder. I can't think of anything else it could be. The modules bit is really reaching because you're not experiencing anything in any of your other sceneries.Man, I wish you were here Sydney 'cause I'd cruise over to your place and get your system working in no time...I think?Mark
Create an account or sign in to comment