lots of variables, most of the people with OOMs have either added tweaks to their cfg file or run P3D2 with the sane slider settings as FSX. I have been flying for 4 days now, last night a 5 hour flight. not single problem. I have not tweaked my cfg file nor copied sliders from fsx nor do I have anxiety problems of my sliders are noy all the way to the right. there may be a memory leak, but for those having the issue, adjust the sliders and fly until it gets fixed. just enjoy what is there. really no point getting all worked up about it, there are more patches coming.

These "oom" threads are starting to become old and annoying. It's been discussed up and down, left and right. There's no 100% solution other than waiting for 64-bit p3d. That's it. The temp solutions are there and if you use common sense, you will be just fine. Other than that, there's nothing more to be said so please stop with these threads.  :Praying:

These "oom" threads are starting to become old and annoying. It's been discussed up and down, left and right. There's no 100% solution other than waiting for 64-bit p3d. That's it. The temp solutions are there and if you use common sense, you will be just fine. Other than that, there's nothing more to be said so please stop with these threads.  :Praying:

64 bit is needed and is planned.  When the vegetation autogen paging issue is resolved by the LM team, the app will be quite stable.  In fact it is quite stable now (barring non-compliant add-one) as long as the user does not exceed the autogen vegetation setting of normal.  What seems to be happening is the paging process loads autogen veggies but does not remove them when too much is being loaded.  It seems to be a paging issue and I believe it can be resolved.  In the meantime, for those who fly in P3D, we can certainly enjoy it with knowledge of some limitations that are being resolved.  For those who fly FSX, we can certanly enjoy it as well with knowledge of some limitations as well.  

Gosh, remember just a few months ago when all of these problems were going to be vanquished by P3D? There would be no tweaking, no limits on settings, no more ooms, and anyone who suggested that P3D would have similar issues to FSX was ridiculed? 

 

When P3D works as advertised, and you can use the settings provided by the manufacturer without crashing the program, then the oom threads will disappear.  Until then I am sorry that folks are annoyed by them. But if we don't point out the problems, they won't get fixed.

 

And really, if the threads annoy you, don't read them!!

There is nothing vague about my experience. I got ooms on my second and third flights after the patch. I have no add-ons loaded. It was a clean install. I got the ooms with both high and medium density vegetation. Seems clear enough.

 

 

I was only quoting LM staff. That was their terminology. To clarify my views on version 2.1, read this previous post of mine:

 

http://forum.avsim.net/topic/434861-poll-if-you-have-21-working-as-it-should-do-improvements-outweigh-downsides/#entry2927647

 

 

Awhile back when P3d 2.0 had been out for just a few weeks, I posted that there were three different categories of experiences that people have had when using P3d2:

 

1. The sim works fine "out of the box". Some of these people even have low to mid-range hardware, which  to me is surprising. Most of these users seem quite happy with P3d.
2. The sim does not work properly, but people admit to, pushing all the sliders to the max, using  a large number of 3rd party add-ons, tweaking the CFG file, OCing the CPU, fiddling with nVidia Inspector, etc.. Many of these people are accepting in the fact that the results that they are getting may be of their own doing.
3. The sim does not work properly, but there is no obvious reason why this is so, except to speculate that there is something about the specific hardware and software configuration that is contributing to the problem. Generally, these users experience errors that are seen by very few if any other people using the sim.

IMO, category 3 is the one that is hard to come to grips with. There are far too many people in this category with P3d 2.1. Some of these people have ultra high end hardware, so that can't be the explanation. Unfortunately, a number of the users in category 3 basically have given up and gone back to FSX or have tried XP10, which means that whatever bugs have caused their problem will likely never be solved. I also wonder how many of these users have filed a support ticket with LM.

 

 

I believe that I clearly stated that the present condition of P3d is not acceptable. On the other hand, some of the people that are complaining about version 2.1 believe that everybody is having the same problem. That can't be correct either.

Here's the difference, FSX was built to tax hardware from 2006. P3D was enhanced to tax hardware currently being produced. If you are experiencing OOM's with P3D your hardware is either lacking or you are demanding too much from the sim.

Here's the difference, FSX was built to tax hardware from 2006. P3D was enhanced to tax hardware currently being produced. If you are experiencing OOM's with P3D your hardware is either lacking or you are demanding too much from the sim.

 

Is default scenery and aircraft at medium autogen settings demanding too much from the sim?

Is default scenery and aircraft at medium autogen settings demanding too much from the sim?

 

Quite possibly, think of how much more in terms of graphics P3D can do compared with FSX. Think shadows, Bathemetry(sp?). 

Here's the difference, FSX was built to tax hardware from 2006. P3D was enhanced to tax hardware currently being produced. If you are experiencing OOM's with P3D your hardware is either lacking or you are demanding too much from the sim.

An i4770 running at 4.5, a 780ti, 16gigs of memory? I think my equipment is pretty damn good! And all I expect is to be able to run the sim with default scenery and aircraft with the sliders on "very dense". If that is asking too much, why put the settings in there? And I COULD do that before the patch. Now I can't. Nothing else has changed. Hence, I conclude that the patch made a negative change to the program in this area.

 

It's just that simple. No venom, no hysteria, no demand for a refund, and plenty of patience while I wait for the fix. That's all!

Quite possibly, think of how much more in terms of graphics P3D can do compared with FSX. Think shadows, Bathemetry(sp?). 

 

No, Prepar3D 2.1 renders the same graphics with FSX, except for the autogen which is the same amount, just spread out differently. Shadows are handled by the GPU and don't affect VAS usage, and bathymetry is something that I'm pretty sure everyone in here has turned off.

 

Nobody is at fault except for Lockheed Martin. Prepar3D 2.1 is bugged with lots of memory leaks and inefficient autogen, mostly the vegetation. You're probably one of the lucky few who don't get OOMs, but many people get OOMs when they fly above default scenery for 10 minutes.

Edited February 22, 201412 yr by ChaoticBeauty

Background jobs hold a reference to the tile they work on which prevents it from being deleted while the job is active. Thread contention can make jobs take much longer to finish which keeps the scenery data for that tile from being released. Paging performance would impact memory usage with or without any leaks. There does appear to be a leak of sorts where some tiles don't get released, but it only happens when paging performance gets in a bad state. We do plan on detecting OOMs and putting safeguards in place to prevent crashes but if a user loads up 6GB of scenery content and a 2GB user aircraft add-on, we can't magically decide what content and settings should be disabled/reduced. In a case like that, what you'll likely get is a warning and a chance to save your flight or change your settings.

Beau Hollis

Rendering System Lead - Prepar3D® Team

 

 This a statement from the official LM message board, posted today. Although I suspect that LM will fix whatever is causing at least some of the OOMs, I do agree with the sentence about the user's role in these types of issues.

Edited February 22, 201412 yr by jabloomf1230

I must admit I am rather curious how some people look the other way and make excuses for the rather parlous state P3D2 is currently in.

 

In twenty years of flight simming this is the first flight sim I can recall that will OOM straight "out of the box" so to speak, with no user addons or modifications, using just the content that came with the sim and settings available to the user on the options screens.

 

That simply shouldn't be happening.

My philosophy is that Microsoft have been producing quality flight simulation software since the 90s and I will always be loyal to only a flight simulator that is from them. For me, FSX works perfectly and I will never be leaving them!

I really don't mean to sound defeatist, but that official statement from LM kind of implies that we will never be free of ooms.

 

In my case, it isn't an issue, because I never got them before patch 2.1, but I think this is a stance that third party developers had better be aware of. I'm sure they already are.

Anyone remember what they said in the DirectX 11 developer blog entry? http://www.prepar3d.com/news/2013/10/4507/

"With the right video card, be ready to max out those autogen sliders with much less impact to performance. Not only do trees perform better, they also transition in smoothly rather than popping in."

Not only does autogen still run on the CPU, but it seems that we'll never be able to max out the autogen without OOMs. Had they really moved the autogen to the GPU, it would run on the VRAM, which means we wouldn't have OOM problems now.

Really sad. That was the part that got me most excited when reading that news post.