I CDT when loading scenery whenever I pick airport in the immediate vicinity of Anchorage, Alaska. CDT occurs when about 56% through scenery loading. If I pick say Fairbanks, Alaska everything is fine. I also noticed that it doesn't crash in summer but in all other annual seasons. I disabled my UT, USA Roads but it did not help. What files do you think I have corrupted and how I could get them?Michael J.WinXP-Home SP2,AMD64 3500+,Abit AV8,Radeon X800Pro,36GB Raptor,1GB PC3200,Audigy 2http://www.precisionmanuals.com/images/forum/747400.jpg

Michael,Anchorage is one of the bitmapped areas in FS, so the problem needs additional investigation. Do you have any other scenery in the region, like bush scenery. It may not be near Anchorage, but may still be within a LOD tile that is loading into memory. Make sure you have all extras removed, including any extra landclass or DEM files.Once you are sure all extras are disabled, then the problem may be a default file corruption.I would try disabling the Anchorage bitmap in the scenery config. This will determine if the associated generic BGLs are causing the CTD or the bitmap.As for knowing which one... geeze! good luck! You can use the LWMViewer to get an idea of which BGLs are active in the Anchorage area and replace them from the installation disk. It may be simpler to use the brute force method and just copy the default bgls for the NAMW area back over the originals.I've been dealing with CTDs for the past 3 months. It's part of the risk of using add-ons. I really hope that MS is able to trap the errors more gracefully in the next version so we have some clue as to where to look for the problem. For example, this week I had a CTD in the Warsaw, Poland area and the cause was a AIA 737 texture for a plane in the Baltics - not exactly a direct connection between the area of the problem and the cause. I spent one whole day looking for problems in the Warsaw area only to eliminate every possibility and still have a CTD. If an error trap could just ID the BGL as the sim goes into meltdown, we'd all have better running sims and fewer headaches.Bruce

Thanks Bruce. No, I have no sceneries installed in Alaska. But since Anchorage is one of the 'detailed' sceneries would you happen to know on what FS9 CD i could find replacement files? I would simply reinstall this whole area and see what happens. Also I was told by some scenery designers that a crash at 57% load normally indicates problem with texture, not bgl files.Michael J.WinXP-Home SP2,AMD64 3500+,Abit AV8,Radeon X800Pro,36GB Raptor,1GB PC3200,Audigy 2http://www.precisionmanuals.com/images/forum/747400.jpg

maybe render to texture is off?

>maybe render to texture is off?sorry, it has nothing to do with it ... but thanks.Michael J.WinXP-Home SP2,AMD64 3500+,Abit AV8,Radeon X800Pro,36GB Raptor,1GB PC3200,Audigy 2http://www.precisionmanuals.com/images/forum/747400.jpg

Michael,I'm at work so I can't look up the CD files right now. Perhaps someone else can respond more quickly.As I mentioned, most of my CTDs have been texture related so reloading the default textures may be the answer. It's really hard to say without having a log file that can be inspected on startup to see where the error occurs and what the program is loading at the time.Bruce

>Michael,>>I'm at work so I can't look up the CD files right now. Perhaps>someone else can respond more quickly.Bruce, this is ok, I can wait for you ..;-)I figure since the problem is limited to the narrow Anchorage area it must be Anchorage specific, hence I would like to know how to pull those files from CDs. If you were really nice you could perhaps send me the zip file through the email from your own FS9 Anchorage installation. There is an 'Anchor' folder under SceneryCities.Michael J.WinXP-Home SP2,AMD64 3500+,Abit AV8,Radeon X800Pro,36GB Raptor,1GB PC3200,Audigy 2http://www.precisionmanuals.com/images/forum/747400.jpg

Hi Mike, I'm somewhat new to the whole CTD problem because I just started using a lot of add-on scenery recently, so take my reply with some healthy skepticism.Michael J. wrote:>I figure since the problem is limited to the narrow Anchorage>area it must be Anchorage specific, hence I would like to know>how to pull those files from CDs. I don't think this is true. What's more likely is that you installed some freeware or payware scenery (the 38m Alaska mesh? fsglobal2005? *shrug*) which is for whatever reason making fs9 upset. I had a similar problem after I purchased fsglobal2005, until I was directed to their support forum and a batch-file that moved some default fs9 scenery out of the default directories. The problem I had was also strange, like yours - fs9 would CTD from Seattle-Tacoma airport but not from many other airports I tried.I haven't a clue how to identify the precise offending .bgl(s), but I should ask this question: what add-on scenery have you added recently? Think back to the last time Anchorage worked correctly and try to uninstall any add-ons you've added since then.Good luck!

The scenery files are on CD4 I believe. That's why the CD is required if you don't do a full install.Jim

Hey!I had this problem.. What was the solution? I believe it was a traffic file in connection with Frank Betts Hope airport. Try looking for traffic files before doing anything drastic. I'm not sure I remember right, but see if you have it.-Dasher7

Dunno why I just answered a half year old thread, don't bump this one folks.. :-smile12-dasher7