Sign in to follow this  
Guest KemoF15

Long Flights

Recommended Posts

On occasion I will be in my 4th+ hour on a long haul and poof--CTD--I've read that there can be "memory leaks" etc...but the CTDs I've experienced are preceeded with absoulutely no warning--no FPS slowdown--no staggering etc...just poof. Doesn't go blue screen just back to desktop.Just curious if other long haulers/transatlantic types have had similar and is there anyway to mitigate?Thanks.KemoF15AMD FX-624GB Corsair DDRNvidia 7950 GX2 (1GB video)Raptor HDWinXP

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Missing or corrupt textures... Restore your default textures and then re-enable GE or any other texture set you use,-PPrimary RigLiquid CooledIntel C2D E6600 @3.2 gigsAsus P5N32SLI-Plus2 gigs Corsair XMS PC6400 4 4 4 12 @810Dual OC'd XFX 8800GTX @ 2 gigs24 inch Widescreen LCD 16XAA/16XAFDual 19 inch LCD'sRaid-0+1PCPower and Cooling 1k Quad SLIhttp://home.comcast.net/~psolk/3monitorsa.htmlBackup RigAMD 4000 San Diego @ 2.72 Gigs Kingston Corsair XMS CL2XFX 7900 GTX Raid-0psolk.jpg

Share this post


Link to post
Share on other sites

Hee hee...welcome to the club! I wish I had a fix for you mate but this is one of those FS9 mysteries that IMHO will never be solved. It happens to me on short-haul flights. In fact on my system its so bad that I just dont even bother flying over Poland.If I takeoff from a Polish airport I can almost TELL you when its going to happen - usually 18 minutes into the flight - POOF. Desktop. :(You will find hundreds of threads on here if you search for CTD, some great suggestions from the gurus, fixes work for some not for others.Good luck though :)

Share this post


Link to post
Share on other sites

Hahahaha, I think most of us has had this problem during our simming. It seems that it happens intermittently. I haven't checked my length of time before it CTD. My FS2004 only gets minimized, then I have to click it to get it back up. Will time it until it crashes, and I will see if it is the same as yours. I am getting it with all my planes at the moment. Maybe formatting and then testing all planes and addons for consistency will do the trick. I have too much installed on my FS2004 to really consider this option. I will bare and grate my teeth until they ache so much that I will have to format yet again.Corrie

Share this post


Link to post
Share on other sites

I figured there was no silver bullet but thought I'd give it a shot...the scenery recommendation sounds plausable but an aweful lot of work with reinstalling basic scenery, Birds Eye View, Ultimate Terrain, FSGenesis etc...I'll hold that one until/unless I get frequent CTDs.What was particularly frustrating on this flight was the fact it was being logged in FSACARS as part of my virtual airline and those 4 hours can't be used...such is the sim life I reckon.Thanks for the comments.KemoF15

Share this post


Link to post
Share on other sites

I feel for you,I had a similar problem somewhere over the Canada/NW US border. I use autosave so I was able to jump back to a minute or so before it happened, saved it and started playing around with it.I tried different :aircrafttime of dayseasonNo effect.I then started disabling sceneries until it worked. In my case (and I'm not pointing fingers here) it was Ultimate Terrain USA. I started playing around with settings and found it was the streams, then I started playing with files and identified exactly which file caused the problem. I posted a request for help on the UT forum and had a collection of things to try, they were helpful and friendly but ultimately we concluded there was some conflict with my system/scenery setup/whatever and this file. It simply didn't like it.Consequently I moved that file out of the installation and now, whenever I fly around the NW US, near to the Canada border, I've got no streams ... and do you know what ... I barely notice, all I notice is that it doesn't crash any more.Hope this gives you some ideas,Ian

Share this post


Link to post
Share on other sites

>I figured there was no silver bullet but thought I'd give it>a shot...the scenery recommendation sounds plausable but an>aweful lot of work with reinstalling basic scenery, Birds Eye>View, Ultimate Terrain, FSGenesis etc...I'll hold that one>until/unless I get frequent CTDs.>>What was particularly frustrating on this flight was the fact>it was being logged in FSACARS as part of my virtual airline>and those 4 hours can't be used...such is the sim life I>reckon.>>Thanks for the comments.>KemoF15Sympathies I am currently enjoying a long period of flights without CTDs but i sympathise with you.When you undertake a long flight, after a few hours you really become involved with it and when you are suddenly hit with the CTD you really feel cheated and VERY angry.Some things you might like to try are Pete (fsuipc)Dowsons auto record utility (free) which by default will automatically record your flight every minute(i personally have it set to record every seven minutes as there is just a little stutteret which i began to notice each minute)if you get the ctd you can resume just before the crash and if it recurs a gain at the same spot you can shove your plane along a bit on the flight plan(FSNav)and continue.Its not ideal but its better than nothing.PS if you fly with airsource there flight recorder is very good,if you get a CTD the logger will still save that flight up till that point and you can reload restart the logger and continue and not lose the hours.cheers Andy

Share this post


Link to post
Share on other sites

I too find it is hit and miss. Thus the reason I only do the odd 4+ hour flight and most I keep to an hour or two.With missing textures I think you get an OOM error and not a CTD?We ask alot of FS9, we replaced almost everything in the sim and expect it to work flawlessly.BTW, my worse case CTD flight was a CYYZ-EDDF and I was about 10 miles out from a 25R approach into EDDF then PLONK! There is my desktop.......

Share this post


Link to post
Share on other sites

Thanks for lots of good comments--this morning I flew the return routing from KSFO-KCLT and almost to the minute I had a CTD at 4hrs and 12 minutes...I was in a similar profile as yesterday--just beginning descent about 100nm out--seems too coincidental to have CTDs at almost precisely the same time on opposite sides of the USA.I run with squawkbox and FSACARS, and ASv6.5 running in the background but I've never had any real issues with CTDs--but then, I don't think I've flown 4hr plus flights till recently either.Both CTDs occured with Wilco Airbus (which is fantastic)--the first one in the 319 and the second in the 321--certainly not pointing fingers at all, but I will try PSS 757 next on the same route to see what happens before I start stripping scenery.KemoF15

Share this post


Link to post
Share on other sites

Rake; Might want to consider keeping the task manager open and monitoring memory commit rate to see if you have a memory leak issue...if you do, the commit rate will creep up steadily. Anything over about 960MB, and you're in the danger zone for an out of memory crash, which can occur with or without warning.RegardsBob ScottATP IMEL Gulfstream II-III-IV-VSantiago de Chile

Share this post


Link to post
Share on other sites

BobI monitored a flight from KSFO-KCLT here's what I found from task manager:Memory commit XP steady state (25 processes in background = 210MBLoad FS9 = 610MBLoad Squawkbox = 618MBLoad FSACARS = 625MBLoad ASv6.5 = 638MBHardware numbers:CPU usage with all above = 20%Physical memory = 2882765 = 2.8GB (although 4GB is loaded)Available memory = 1792690Cache = 809964On above flight at 1hr point:Commit = 795405Limit = 7043516 (does not change)Peak = 8479361:30Commit = 799576Peak = 8750242:00Commit = 820296Peak = 8750242:30Commit = 844820Peak = 8750243:00Commit = 847492Peak = 8750243:30Commit = 862768Peak = 9157894:00 (I did 5 minute checks here since this was when it would CTD)Commit = 882716Peak = 9157894:05Commit =8858614:10Commit = 8867084:15Commit = 885900Landed and on taxi back:Commit = 1001624Peak = 1026020Total commit charge at the bottom = 989MBSystem Cache ended at: 1185864FS9 did not CTD on this flight although the two previous flights from KSFO-KCLT crashed at almost the same point--beginning of descent (100nm out) at about the 4:10-4:15 total flight time. Both of those flights were daytime--the one that did not crash was at night--everything else was the same (equipment, squawkbox, FSACARS, ASv6.5)My initial thought is there is a leak of about 25MB/hour--but my question is--does the memory commit increase for all systems over time when using FS9?--or should it always stay at the intial level?Seems to make sense that there will be some increase in memory commit over time due to scenery cacheing etc (is that true?)Next question is, if there is a memory leak, how do you isolate it? As one of the earlier posts mentioned, Ultimate Terrain USA apparently may have some leaks with some files (enhanced streams etc)...again it seems logical that memory commit would increase if the system has to "build" each stream and that stream remains in memory cache as opposed to "going" away once it's out of system "view"Anyway-there's the data--any thoughts?ThanksRake

Share this post


Link to post
Share on other sites

You have a memory leak, all right. That steady climb...200MB in all, is not normal.It's likely the reason you didn't get an OOM crash at the end of your night flight is that FS9 didn't try to load a buttload of scenery textures when the destination airport came into view at night. That demand, with 900+ MB committed, can easily exceed the memory space afforded to an application.The most common cause of memory leakage is a scenery folder with an empty texture subfolder. It's a well-known bug in FS9. You need to scrub your entire FS9 directory for that...if a texture folder is empty, delete it.That said, there are some other causes of mem leakage...poor programming in some panel software, for example. Simple logical troubleshooting is needed in that case...does it happen with just one panel, or in one particular scenery area etc?RegardsBob ScottATP IMEL Gulfstream II-III-IV-VSantiago de Chile

Share this post


Link to post
Share on other sites

But the original poster said he got a straight CTD no error message no nothing. That points to missing or corrupt textures, not the Out of Memory error you are talking about Bob. Also, 200 megs memory usage above initial load is "normal". Actually almost all of it goes in the first 30 minutes before you even get off the ground and the last 30 minutes on approach. For example if you start with 600 megs of memory usage by the time you get off the ground you could be up to 800- 850 megs of memory usage. Then you should gain about 50-100 megs back in the air away from the scenery and then upon descent you will use that 50-100 you gained back in the air and typically lose another 100 megs for the scenery load on descent. This is with Add-on A/C and add-on scenery btw.So start with 600go to 800 on the groundgo back to 700 in the air but land with 900 megs used...It is perfectly normal for FS...I did ~ two years of research on FS memory usage. I do not think there is a memory leak here at all especially if the poster is getting a straight CTD with no error message. I originally suggested restoring default textures. Please try and report back.-PaulJust my .02Primary RigLiquid CooledIntel C2D E6600 @3.2 gigsAsus P5N32SLI-Plus2 gigs Corsair XMS PC6400 4 4 4 12 @810Dual OC'd XFX 8800GTX @ 2 gigs24 inch Widescreen LCD 16XAA/16XAFDual 19 inch LCD'sRaid-0+1PCPower and Cooling 1k Quad SLIhttp://home.comcast.net/~psolk/3monitorsa.htmlBackup RigAMD 4000 San Diego @ 2.72 Gigs Kingston Corsair XMS CL2XFX 7900 GTX Raid-0psolk.jpg

Share this post


Link to post
Share on other sites

Just completed another "test" flight from KCLT-KSFO--I saw very consistent values (600-800) the whole flight and had no CTD--I have not reinstalled default textures (yet)--once I did that I suspect I'd have to reinstall BEV, Ultimate Terrain, and FSGenesis again--is that correct? Or, is there a workaround to that?What I did in the meantime was to modify my PAGEFILE.SYS--set value to "no pagfile" in virtual memmory then rebooted, then set my inital value to 1.5 times my physical RAM--2.8 which is 4220 then set my Max value as the same (there's some good discussion on this topic--but I went with what a Microsoft XP engineer suggested). Actually, I have 4GB RAM but XP only "recognizes" 2.88 on my system (32bit-XP).Second, I defragged my PAGEFILE itself--it like the HD can get untidy--then defragged my HD (I usually do that once a week anyway). http://www.freedownloadmanager.org/downloa..._pagefile_info/Finally, I unselected enhanced streams in Ultimate Terrain USA--that was suggessted in a post above and at a minimum saves creating those buggers all over the place.2 successful transcontinental flights since I made these changes with no CTD--one at night and one during the day.If ever there was a mysterious area--it's how FS9 and FSX manage memory and what role if any virtual memory plays in the equation. The "fixes" above seemed to have work--or at least work for now before I have to cut a little deeper--reinstalling scenery etc.Thanks for the helpful comments.Rake

Share this post


Link to post
Share on other sites

I have the same pain for a long time. I did every possible way to avoid CTD. No success. Today I applied the Microsoft "The game stops responding or closes unexpectedly when you start or play a Microsoft game" problem solution. I made a long flight from KSEA to CYYZ. 134 nm to CYYZ no warning poof LDS 767 gone . I repeat the flight , after 4+ hours 130nm to CYYZ "POOF" all gone., back to desk top screen.The only thing what I noticed during these two flights GE PRO performance was detrained. GE partially was covering the surface, many squares and no clear scenery. I was wondering if GE Pro is the problem.Sanal

Share this post


Link to post
Share on other sites

I know you probably have all done this BUT just in case...make sure you have the FS9 patch installed this deals specifically with seasonal scenery CTDs .Its not a cure for all CTDs (shame)but it defiantly works.cheers Andy

Share this post


Link to post
Share on other sites

Do a Google search for "filemon". It's a very nifty little utility that monitors the HDD activity on your computer and will give you a blow by blow account of every file that is being accessed and whether or not it was read successfully. If any of your FS scenery or texture files have become corrupted this will help you track them down. A couple of weeks ago I was getting CTDs when flying around Europe. I used Filemon to help me diagnose the problem - some of my UT Europe files had become corrupted. A fairly simply reinstall of UT Europe solved the problemThere is also a fairly well known issue with landclass files being incorrectly installed. If you have any BGL files that contain landclass information, and they have a corresponding texture folder installed with them, you will get a memory leak that will eventually result in a CTD. It's worth going through your addon sceneries and just checking to see if there are any landclass files intalled incorrectly. Even though this problem has been known about for a fairly long time, I still see some third party sceneries that install landclass files into a "scenery" folder that also has a corresponding "texture" folder too. I'm not sure if this is your problem, as it usually generates an out of memory error message before quitting FS, but it won't do any harm in checking.Another possibility you might want to consider is a hardware fault. I was getting random CTDs and blue screens a few years back, and it was driving me nuts. I formatted and reinstalled Windows several times before finding the cause of the problem - a faulty RAM module!Good luck with fixing your CTDs!

Share this post


Link to post
Share on other sites

EngineRoom,The reason you might see LC files with associated texture folders is if the LC files actually call for those textures. The memory leak comes from having LC files in a scenery folder with an EMPTY texture folder. Just because a LC file has a texture folder associated with it does not necessarily mean it will cause a memory leak.As for Filemon it is the best thing to happen since sliced bread ;)-PaulPrimary RigLiquid CooledIntel C2D E6600 @3.2 gigsAsus P5N32SLI-Plus2 gigs Corsair XMS PC6400 4 4 4 12 @810Dual OC'd XFX 8800GTX @ 2 gigs24 inch Widescreen LCD 16XAA/16XAFDual 19 inch LCD'sRaid-0+1PCPower and Cooling 1k Quad SLIhttp://home.comcast.net/~psolk/3monitorsa.htmlBackup RigAMD 4000 San Diego @ 2.72 Gigs Kingston Corsair XMS CL2XFX 7900 GTX Raid-0psolk.jpg

Share this post


Link to post
Share on other sites

Engineroom--thanks for the Filemon vector--my question is which files are suspect--the failures and/or not found? or both?One file failed consistently over time--it was an FMGC file for the Airbus 320, so I put that in a temp delete folder...I did not see any addon scenery, ultimate terrain or GE Pro, or freeware scenery issues...at least in the 1hour slot I monitored--I captured every 5 minutes (there's probably a more efficient way to monitor scenery files only but I haven't figured it out).I looked in all the scenery folders to see if there were any texture/or empty texture folders--did not find any--though--in UTUSA and in the base scenery folder there are some files with a .xxx extension vice .bgl...are those redundant files?Thanks againKemo

Share this post


Link to post
Share on other sites

I think the xxx files in UT are ones that have been renamed in order to deactivate them. I would leave them be, as FS will ignore them because of the xxx extension. If you want to reactivate any of the features in UT in the future you'll probably find the UT configuration utility will probably rename these with the bgl extension.As for Filemon, files that aren't found may not necessarily cause the sim to crash, but they probably will cause stutters as FS searches for these files. The files that cannot be read are the ones that are likely to cause you headaches. A good way to find the problem is to set Filemon to real time monitoring, start FS, and recreate the situation that you know will cause a crash. Then examine the Filemon log file afterwards and if the crash is caused by a missing or damaged file you will see it in the Filemon log.

Share this post


Link to post
Share on other sites

Thanks fo that, I never realised it was landclass files with empty texture folders. I always thought it was landclass files with any associated texture folder!Cheers

Share this post


Link to post
Share on other sites

I found this interesting piece on the UTUSA--UTEurope forum; seems UT will look for an EFFECTS file that doesn't exist--I noticed this issue last night with filemon as well--most of the time folks will have OOMs or CTDs on long flights over the US/Canada because the EFFECTS file call is used for river/lake/stream coastline enhancement.There's a UTUSA patch out 1.30 that renames these files and doesn't put FS9 into a constant file search loop wasting precious memory.Anyway read for yourself:http://www.simforums.com/forums/forum_posts.asp?TID=19466Kemo

Share this post


Link to post
Share on other sites

HelloOne thing you might want to try is this...i had a the same problem as you with a CTD that occurred out of the blue and FS would shut down with no warning message or anything else.What appeared to solve it for me was emptying out my ADDON SCENERY folder,it meant losing some things that i had installed but they are easy to reinstall again and after that no more CTDs.Maybe one of the ADDONs had a bug or fault(apologies not tech wise)but it really helped me solve one of my worst bout of CTD blues chapters.I fly two three and four hour flights every day and touch wood i have not had a CTD since.cheers Andy

Share this post


Link to post
Share on other sites

>But the original poster said he got a straight CTD no error>message no nothing. That points to missing or corrupt>textures, not the Out of Memory error you are talking about>Bob.Not necessarily...an OOM can provoke a straight CTD.>Also, 200 megs memory usage above initial load is "normal". >Actually almost all of it goes in the first 30 minutes before>you even get off the ground and the last 30 minutes on>approach. But his climbed steadily through the course of the flight, to over a gig committed by the time he had it on the ground. That's nearly 400MB of steady growth, and definitely not normal. With same model, and most of the same add-ons, I see things hovering at around the 800MB mark, not climbing to over a gig.RegardsBob ScottATP IMEL Gulfstream II-III-IV-VSantiago de Chile

Share this post


Link to post
Share on other sites

Andy--were you able to isolate which addon or addon files were the culprit? Kemo

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this