Steverino Posted March 7 Share Posted March 7 I’ve searched the forums for guidance and tried everything I can think of; however, I’m still getting “Out-Of-Memory” errors/popups shutting down my sim on all fights in various aircraft approaching one particular area - Illinois. This error is only generated there – the rest of the world works fine - and because it wasn’t always like this, I may have screwed something up somewhere. Not knowing what else to do I first checked for duplicate AFCADs and empty Texture folders in addon sceneries in the area. Then I disabled all addon airport sceneries and AFCADs in Illinois and surrounding states…. but, trying different flights from different directions, the problem persists when flying into the Illinois area. I don't think it's my computer. Could it be some bit of corrupted underlying scenery or something with Ultimate Terrain or Ground Environment? If anyone has a thought about what else I might check, please let me know because I have no clue what is causing this – and, if you’ve taken the time to read this far…. Thank you and God Bless!! Steve Link to comment Share on other sites More sharing options...
michaelkalinowsk Posted March 7 Share Posted March 7 It could probably be a landclass scenery folder that has an empty texture folder. Landclass scenery must not have a texture folder but only a scenery folder. Kali Link to comment Share on other sites More sharing options...
Skywatcher12 Posted March 7 Share Posted March 7 Make sure you have updated FS9 to 4gb of virtual memory. Mark Daniels Link to comment Share on other sites More sharing options...
leuen Posted March 7 Share Posted March 7 Mostly OOM messages don't mean memory lack. Generally it occurs while FS isn't able to manage a wrong or unsuitable file. Kali's advice could be one of the possibilites. Otherwise you have to deactivate all your senery entries and reactivate them step by step until the incriminated area works correctly again. At least you will know the respnsable folder. It's a quite annyoing solution, i agree, but still faster than spending hours to try all kind of things. Bernard Link to comment Share on other sites More sharing options...
chris_eve Posted March 8 Share Posted March 8 Try disabling AI traffic if you've got it running ... there may be a problem with an AI aircraft operating out of this area. If so, examine your traffic files for appropriate activity, then try looking for excessively oversize textures in the relevant aircraft folders. Having high-resolution detailed aircraft is all very nice for the aircraft you're flying, but models being used for AI can usually be significantly less detailed. Link to comment Share on other sites More sharing options...
johnhinson Posted March 8 Share Posted March 8 And . . . another issue that has cropped up before has been faulty Terrain Mesh files. If you use add-on mesh, check with the supplier for updates as I believe the issue was fixed. Otherwise, you should test with it disabled. Also, remember that some add-on sceneries include files to install elsewhere to Addon Scenery - often in amongst your default files so you may need to investigate there too. It is unfortunate there are so many different possibilities for the cause of the problem, it can take a lot of patience and time. Best regards, and good luck, John http://www.adventure-unlimited.org My co-pilot's name is Sid and he's a star! Link to comment Share on other sites More sharing options...
Steverino Posted March 8 Author Share Posted March 8 Big thanks to all of you for taking the time to reply and offer suggestions. I didn't think about AI traffic or landclass issues and will explore and test further. What's confusing me is that this area was fine for years and this problem has only appeared recently. For example, in the Chicago area, I have Fly Tampa's KMDW and have been in and out of there many times, but now if I attempt to start a flight at Midway, it's "OOM". Disabling that and other area sceneries isn't a fix. Although frustrating, perhaps with the kind and patient help of others like you who have more experience and a better understanding, we'll get this sorted out. Link to comment Share on other sites More sharing options...
Steverino Posted March 8 Author Share Posted March 8 Today's test flight No. 1 - AI Traffic at 0% - Searched Scenery for "LC" and "landclass" and deactivated several entries in area airports. Fired up my ERJ at Grand Rapids and headed WSW towards the Chicago area. I just about made it to Lake Michigan and got shut down again. Dang it. Illinois hates me. Link to comment Share on other sites More sharing options...
surrodox2001 Posted March 8 Share Posted March 8 Interesting... I've never had OOM issues with FS2004, with no enhancement patches (eg extended RAM caps) added... Hope you'll get the issue fixed. Link to comment Share on other sites More sharing options...
JSMR Posted March 8 Share Posted March 8 Have you added any airports? Regions? Scenery for that area lately? https://fshub.io/airline/RUA/overview Link to comment Share on other sites More sharing options...
Steverino Posted March 9 Author Share Posted March 9 Thanks, JSMR - I must have added or modified something that is causing this because previously, flying in this area has not generated a problem. Sorry if this is a silly question, but when trying to isolate a scenery issue, is it sufficient to uncheck/deactivate in the Scenery Library, or must it be actually deleted/removed? Link to comment Share on other sites More sharing options...
surrodox2001 Posted March 9 Share Posted March 9 3 minutes ago, Steverino said: Thanks, JSMR - I must have added or modified something that is causing this because previously, flying in this area has not generated a problem. Sorry if this is a silly question, but when trying to isolate a scenery issue, is it sufficient to uncheck/deactivate in the Scenery Library, or must it be actually deleted/removed? I think you can just disable the problematic scenery in the settings and it'd be fine. 2 Link to comment Share on other sites More sharing options...
Steverino Posted March 9 Author Share Posted March 9 3 hours ago, surrodox2001 said: I think you can just disable the problematic scenery in the settings and it'd be fine. Thank you. 1 Link to comment Share on other sites More sharing options...
Tom Gibson Posted March 10 Share Posted March 10 If you can't pinpoint it, disable all addon scenery in the Scenery Library and then check again. If that fixes it, then activate half of them and try again. Continue by dividing and checking again until you find the culprit. Link to comment Share on other sites More sharing options...
Steverino Posted March 11 Author Share Posted March 11 Thank you for your suggestion Tom. Your reply is appreciated. If I ever manage to sort this out, I'll post the results as it may help someone else. Link to comment Share on other sites More sharing options...
Steverino Posted March 13 Author Share Posted March 13 On 3/10/2024 at 11:50 AM, Tom Gibson said: If you can't pinpoint it, disable all addon scenery in the Scenery Library and then check again. If that fixes it, then activate half of them and try again. Continue by dividing and checking again until you find the culprit. Because this is only a problem in the U.S., I disabled all U.S. addon scenery and removed all other U.S. sceneries and additional AFCADs from addon scenery/scenery. AI was set to 0% and I still got OOM popups when approaching Illinois. Flew west from KIND and near the border - shut down. Same result flying NNE from KSTL. I can start a flight at Johnny Alford's KORD, but FlyTampa KMDW won't load without a OOM error. I'm out of ideas now and will probably have to designate the state of Illinois as a 'no fly' area. Link to comment Share on other sites More sharing options...
chris_eve Posted March 13 Share Posted March 13 1 minute ago, Steverino said: Because this is only a problem in the U.S., I disabled all U.S. addon scenery and removed all other U.S. sceneries and additional AFCADs from addon scenery/scenery. AI was set to 0% and I still got OOM popups when approaching Illinois. Flew west from KIND and near the border - shut down. Same result flying NNE from KSTL. I can start a flight at Johnny Alford's KORD, but FlyTampa KMDW won't load without a OOM error. I'm out of ideas now and will probably have to designate the state of Illinois as a 'no fly' area. Take Tom's advice ... disable EVERYTHING ... it's not unknown for rogue scenery elements to be accidently included in unassociated scenery and affect areas some way away. Just takes a simple mis-typed latitude or longitude figure and something from maybe South America or Europe could be trying to turn up in Illinois! I've spent several long sessions over the years disabling and re-enabling sceneries to isolate bugs like this. 1 Link to comment Share on other sites More sharing options...
leuen Posted March 14 Share Posted March 14 9 hours ago, chris_eve said: Take Tom's advice ... disable EVERYTHING ... it's not unknown for rogue scenery elements to be accidently included in unassociated scenery and affect areas some way away. Just takes a simple mis-typed latitude or longitude figure and something from maybe South America or Europe could be trying to turn up in Illinois! I've spent several long sessions over the years disabling and re-enabling sceneries to isolate bugs like this. Thar's what I said seven days ago. Meanwhile the problem could be solved or at least detected. Why waisting time for nothing? Link to comment Share on other sites More sharing options...
Steverino Posted March 14 Author Share Posted March 14 4 hours ago, leuen said: Thar's what I said seven days ago. Meanwhile the problem could be solved or at least detected. Why waisting time for nothing? Hello Bernard.... thank you very much for taking the time to comment and for the additional details. Even after all these years, I don't really understand how this sim works or what things may effect something else. I appreciate your help with this and your kind advice. Finding solutions to problems like this can be time consuming, ridiculous and annoying, but at the same time, it's kind of fun to try and fix a situation that's causing issues. Wish me luck Link to comment Share on other sites More sharing options...
leuen Posted March 14 Share Posted March 14 It may be a little reassuring and make the tedious work not easier, but I regularly have to deactivate the more than 1700 entries and reactivate them step by step to detect any incompatibility. Despite everything and as you said, sometimes FS remains quite complicated Good luck finding the troublemaker quickly. Just as a suggestion: use an easy handling scenery tool, like FS Scenery Manager. It's much easier than any default solution. Bernard Link to comment Share on other sites More sharing options...
Skywatcher12 Posted March 14 Share Posted March 14 You haven't answered if you have the 4gb patch. It's the first thing you should do. 1 Mark Daniels Link to comment Share on other sites More sharing options...
Steverino Posted March 14 Author Share Posted March 14 1 hour ago, Skywatcher12 said: You haven't answered if you have the 4gb patch. It's the first thing you should do. Hi Mark..... sorry I didn't reply about this. I have downloaded 4gb_patch.exe from ntcore.com - Is that what I want? Haven't done anything with it yet - still reading up on the 'patch' as I was not familiar with it. I have seen a lot of positive feedback from people with problems like mine - so thank you for the tip. Link to comment Share on other sites More sharing options...
Steverino Posted March 14 Author Share Posted March 14 So, at the risk of boring everyone to death with my petty problems... here's my update. After four hours today, I’ve concluded that for reasons I don't understand, my OOM errors in the Illinois are being generated by Ultimate Terrain USA – not an addon scenery or airport issue. These are my three tests that have been causing OOM errors in Illinois-land: 1. Loading a flight at KMBI (Bloomington) – immediate error popup 2. Loading a flight at KMDW (Midway) - immediate error popup and 3. Flying west at 290 degrees from KIND (Indianapolis) – error shutdown 20-30 miles west of Indy. I used these three tests on the disabling / restoring step by step sequences below. After each step I exited and restarted the sim. A) Disabled EVERYTHING in Addon Scenery except Ultimate Terrain and default entries. OOM error! B) Left Addon Sceneries above disabled and also emptied all of the contents from Addon Scenery/Scenery folder. No good. OOM error! C) Left above disabled and then also disabled Ultimate Terrain in Addon Scenery – NO ERROR this time on above three tests D) Restored/Replaced everything that was in Addon Scenery / Scenery - NO ERRORS E) Enabled everything in Addon Scenery EXCEPT Ultimate Terrain – NO ERRORS F) Enabled UT Europe and Canada – all except UT USA – NO ERRORS (It was nice to visit my FlyTampa Midway again.) G) Enabled UT USA…… OOM ERROR! When finished testing, I had everything enabled EXCEPT UT USA and got no OOM errors. But when I re-checked it, restarted the sim and took off from KIND the error popup reappeared – also OOM when I tried to load a flight at Midway. So, I think I was able to determine what has been causing my OOM error popups - but, I don't know why it's happening. Should I reinstall UT USA? Thanks again everyone for helping me. Steve Link to comment Share on other sites More sharing options...
jgf Posted March 14 Share Posted March 14 I would enable UT USA again, then remove a handful of files at a time until the OOM disappears. If it's not an interaction between UT and some other file, or between several UT files, you should be able to isolate the offending file; then either live without that file or, if it is corrupt, get a replacement. Link to comment Share on other sites More sharing options...
Skywatcher12 Posted March 14 Share Posted March 14 1 hour ago, Steverino said: Hi Mark..... sorry I didn't reply about this. I have downloaded 4gb_patch.exe from ntcore.com - Is that what I want? Haven't done anything with it yet - still reading up on the 'patch' as I was not familiar with it. I have seen a lot of positive feedback from people with problems like mine - so thank you for the tip. Yes!!! Before wasting time doing all the things you are doing or people are suggesting here, run this patch! If you still have problems, then you will need to start looking at everything else. It takes next to nothing for FS9 to run out of memory not patched. You may not even have a problem at all. Run the patch and get FS9 up to 4gig. Then see if you actually even have a problem. It harms nothing, point it to your FS9.exe and it'll patch it. 2 Mark Daniels Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now