On or about 12-21-04, the first day of winter, my fs9 refused to load. first time that has ever happened. When loading, the ctd would occur while loading terrain, somewhere in the 50 to 60 percent loading range.This remained for two weeks, in which i unistalled and reinstalled fs9 twice, same result.I followed the post of babewatcher 12-27-04, and from that I deleted usa roads. Guess what, fs9 is working perfectly, as it did before 12-21-04. This worked for me and i will post a message with folks of usa roads to see what they say. Some kind of conflict somewhere which may or may not have something to do with the winter textures?

Hi rgr.Why not create a saved flight of that event? Set your date and time, use a default aircraft, no AI traffic, any AFCAD or other addon scenery deactivated. Save the FLT file as a zip, and attach it here. Then others can confirm or deny the cause of the CTD.This is exactly the method used to verify the original seasonal CTD problem.Dick

The cause is definately USA Roads. I read about someone having this kind of trouble and today I tried to fly in Seattle and had the same problem with a CTD at 57% loading. After reverting to the default roads it was gone.

Hi I read your post and had to add my 2 cents worth. I believe my problem was a texture conflict with Lennarts textures and US Roads. Since uninstalling lennarts Tex's I have had no more CTDS with US ROads installed and active. The CTD;s you are experiencing sound exactly the same as mine. Do you have Lennarts textures installed by any chance.Don

Hi all.Again, if you do not save and share a FLT file, the problem cannot be verified. As noted above, it may not be USA roads at all, it may be missing textures, or an improper landclass setup, or an errant AFCAD file.USA roads puts a BIG memory load on the sim... if something else is causing memory problems, the USA Roads addon will definitely aggravate that problem... but may not be the root cause.Dick

I too had roughly the same experience, suspecting USA Roads. I also had nuroads (NuRoad10.zip) installed to soften the USA roads textures. I disabled NuRoads first and had no more crashes.(BTW, no Lennarts textures used here) Can't explain it, just know it worked for me.

>Hi all.>>Again, if you do not save and share a FLT file, the problem>cannot be verified. As noted above, it may not be USA roads at>all, it may be missing textures, or an improper landclass>setup, or an errant AFCAD file.>>USA roads puts a BIG memory load on the sim... if something>else is causing memory problems, the USA Roads addon will>definitely aggravate that problem... but may not be the root>cause.>>DickI am reading with intrest this topic. I to have USA Roads and am wondering if my recent problems that last few months with high memory usage has to do with USA Roads? I also have the nuroads files installed as well to dampen the effect of them. Dick, I did you find that it was causing such a big memory load?

Hi Eric.The extra memory usage is caused by the number of VTP2 line segments. There's not a lot that can be done about that. You can see the effects of the memory usage by windowing FS9 with and without the roads, and running Task Manager to see the memory usage.It not just USA roads, but all road/stream/shoreline, etc... addons.If you don't have enough memory, there will be a problem... if you have an addon that is problematic, the extra memory load of USA roads might cause a CTD. But the actual problem might not be USA Roads ( or any other road package ) itself.Dick

Well, I have 1024MB of RAM but my problem may be that I am using addons in combination together that use a lot of memory. The PMDG 737 uses a ton of memory. I thought I read on this forum that someone found that if a developer uses scenery witth the VTP2 segments, the textures must be named the same as the bgl files or else a memory issue will result? Am I off base here? I read in in the scenery design forum a while ago.EDIT: I just researched the message and found out it was written by you! Here it is again:I recently looked at a problem with VTP lines and an odd memory loss connected with them.What I discovered was that when we make VTP lines or polys, and use named textures ( rather than the numbers in the terrain.cfg file ), we must be careful with the use of a twin "TEXTURE" folder... just like landclass!If our BGLs use a named texture, all the textures used must be in the local "TEXTURE" folder, or we cannot have a local "TEXTURE" folder at all! If we intend to place the named textures into "...worldtexture", that's fine, but then we can't have some in the local "TEXTURE" folder. Have them all in one folder or another.Also, we cannot have an empty "TEXTURE" folder with scenery using named textures... a memory loss will occur and will either crash or choke the sim's performance.So if your scenery is leaking memory, it's probably the fault of the local "TEXTURE" folder. Your are either missing some textures there, or you shouldn't be using the folder at all.--------------------------------------------Dick, If you look in the FS9 folder, then Scenery folder and then look at the ROAD 2004 folder. In it there resides a scenery and a texture folder. I see there are lettered and numbered bgl files. The texture folder however is empty. May this be causing the problem? I see all the other roads folders within the main scenery folder have no texture folder. Just throwing out ideas.

This thread at the Flight1 support forums might help. http://www.simforums.com/forums/forum_post...p?TID=8106&PN=1

Hi Eric.That is a good find! The "Road 2004" project folder should NOT contain the "TEXTURE" folder. That will cause a problem when using USA Roads 'default' roads. The "Road 2004" contains the default BGLs, should someone decide to use them... and using them will cause a huge memory loss. What seems to happen is the sim reserves memory for the textures, then looks in the local "Texture" folder ( if One is present ). If the local texture folder does not have the textures, it then reserves memory and looks in the default ( main ) "Texture" folder... but the original memory block was never released! With something like thousands of VTP2 lines, thousands of blocks of memory are tied up, and a resulting CTD.The cure here is to go through all the USA Roads project folders, and delete all the unwanted "Texture" subfolders.However, the problems refered to in the above posts may still not have anything to do with the CTDs, because USA Roads, even in it's correct configuration, still eats up a ton of memory. All road/rail/stream packages are memory hungry.Dick

FYINuRoads10.zip contained a file error, and was replaced soon after posting with NuRoads11.zip, available here in the Avsim Library.NuRoads 2.0 is now available. For a comparison see:If I have NuRoads 1.1 FreeWare, why purchase "NuRoads 2.0 ? http://portal.fsgenesis.net/index.php?name...iewtopic&t=2170....frank