Sign in to follow this  
neil0311

OOM in the NYC area

Recommended Posts

I recently started getting OOMs in the NYC area.  Yes, I have a lot of add on scenery in that area, specifically Imaginesim KLGA, FSDT KJFK v2, and Megascenery Earth 2.0 New York (photo scenery), and Megascenery Earth 2.0 Ultra Res City - NYC (high resolution photo scenery).   The only recent changes/additions were an upgrade from FSDT KJFK v1 to v2, and adding the Megascenery ultra res NYC photo scenery. 

 

The question that I have is related to photo scenery in this situation.  If you have two photo scenery packages like Megascenery Earth that cover the same geographic area, but one is a higher resolution and has a higher priority in the scenery library, do both packages consume virtual address space and contribute to out of memory issues?

 

If the answer is that only one package is active and affects the 4GB VAS for FSX, then the only conclusion is that KJFK v2 is the culprit, since v1 did not cause any issues.   I'm not "blaming" the JFK v2 scenery, but it looks like it may be the straw that broke the camel's back.  Only other thought is a memory leak but not sure how that could happen since nothing is running an executable. 

 

Any thoughts?   Thanks!

Share this post


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

OOM in NYC is common due to the sheer number and volume of buildings ect.  I heard people using DX-10 don't have this problem.  Are you running DX-10 or DX 9?

Share this post


Link to post
Share on other sites

Depending on what type of flying your doing, meaning g/a or airline, I would disable the airport in the scenery.cfg that your not flying to. So if your flight is going to KJFK, then disable the KLGA scenery in the scenery.cfg before you start your flight. No need to have both airports running at the same time if you will only be landing at one of them and it will save you some memory and maybe some FPS as well.

 

Not sure, but I think the higher res city photoscenery might cause more of a VAS hit than the regular low res version since the files are larger size. If I were you and flying a complex aircraft that consumed lot of memory, then I would probably disable the NCY high res version as well, and just use it when flying g/a or aircraft that dont require as much overhead.

Share this post


Link to post
Share on other sites

And using DX9, since I've not been successful with antialiasing and had some other issues with DX10. 

Share this post


Link to post
Share on other sites

New York is the Bermuda Triangle of FSX. Be careful no to add too many addons into the mix if you run your graphics settings and AI traffic at high levels!

Share this post


Link to post
Share on other sites

This is an automatic message.

 

This topic has been moved from "MS FSX Forum" to "Crash To Desktop (CTD) Forum". This move has been done for a number of possible reasons.

  • The most likely reason is that the post was off topic.
  • The topic could also have contained images or a video that were not appropriate to the original forum it was posted in.
  • The images might not have been "illustrative" or "explanatory" in nature.
  • The topic could have been moved because we deemed it to be more appropriately placed elsewhere.
Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums. See our image posting rules here.

 

Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated.

Share this post


Link to post
Share on other sites

Only one package is active BUT, the other package will load too (but not be displayed).  That's the nature of photoscenery (including Orbx).  Everything loads whether you are using it or it's a higher priority or whatever.  I discovered this with MSE V2 since I own almost all of them here in the USA.  I was getting constant OOM's.  I then decided to download the SceneryConfigEditor that allows you to disable/enable only the scenery you will be using during a flight plan.  You can do this even before FSX is loaded.  It worked and FSX no longer OOM's unless I'm flying a long flight with several MSE V2 or Orbx photoscenery loaded and arrive at a nasty high density area like NYC or Seattle.  If I have real weather loaded, for sure I'll probably get an OOM near my destination.  So, to avoid OOM's, disable as much photoscenery as you can before starting up FSX.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

The metro NYC area is well known in this community for contributing to stutters, and in the worst case, OOMs.   Jim's advice is spot on, the discovery of the SceneryConfigEditor app to disable scenery you are not flying over is one of the greatest tweaks out there to surface in recent memory, IMHO.  Even when you disable extraneous scenery in the library, you are still going to get a big drop in frames in this area for a few reasons:  

 

- You have 3 major international airports in a short radius of each other.   FSX has to display the complex scenery elements for those airports (LGA,EWR,JFK, and some other smaller fields, notably, KTEB) AND, if you have AI traffic displayed, compute and manage flightplans for that traffic.  If the traffic is just sitting at the gates it's one thing, but when that traffic becomes active FSX uses precious resources to have ATC manage those flightplans, and when you add up the hundreds of traffic, that can put a chokehold on the simulator in that specific area in the northeast corridor.   Depending on your level of hardware, you will need to prune the AI sliders appropriately, maybe even the scenery complexity of the autogen will have to go down a notch.

 

- The default models used by FSX for the custom buildings in downtown NYC, and the various cranes at the docks, are poorly designed and use up more frames than they should.   The only option there would be for someone to offer replacement models that are more frame rate friendly, but unfortunately, such a solution does not exist. 

 

You can eliminate the chances of an OOM in that area with careful management of your scenery library before you load the sim, but you cannot avoid the frame rate impact of the complex airports situated so close to each other, and the traffic that uses those busy hubs will also have a noticeable impact if you like to run large amounts of AI traffic.  This is one of the first lessons I learned about scenery performance in FSX, NYC is the biggest drain on the simulator and you need to work around the limitations it poses on your hardware's capabilities accordingly anytime you fly in it's vicinity. 

Share this post


Link to post
Share on other sites

Thanks Jim and A.J.  I'll investigate SceneryConfigEditor and play around with various configurations.  

Share this post


Link to post
Share on other sites

Well that's disappointing.  I downloaded and installed SceneryConfigEditor and found out it requires Java.  I refuse to load that crap on my system, so I guess I'll be looking for a different tool.

 

Anyone know of a similar utility that doesn't require Java?

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