First off let me say I'm the 7 years I've used FSX I've never had an OOM and up until v2.3 of p3d I never had one in v2 either but now they are common nothing has changed really same addons ect . To me 2.3 is really bad at memory management on a flight from KRNT to PAKT I over flew ORBX KBVS and 74S and I heard the ding of doom from FSUPIC so I fire walled the throttles and got away from them and the dings stopped but on decent into PAKT I got an OOM so I went back and redid the flight this time with the two orbx airports disabled and no OOM. Its defently these two airports causing it as before I disabled them I tried going due west out over the Pacific and then north so they wouldnt be loaded and no OOM. My question is why is P3D still holding data in memory from airports that were over 500 miles away at the time of my OOM?

Here I have OOMs also.

 

Where I could use 3 screens for the outside view in v2.3  icw Night Environment I now cannot get 1 screen to display the night without getting an OOM with v2.4.

Me too. When flying between two payware airports over Orbx openLC Europe with the new Aerosoft Airbus A319 (1 screen), I almost always get the OOM warnings from FSUIPC or an actual OOM in the final stages of the flight. That's a real shame because with v2.2 OOMs where almost impossible. Would really like to know why memory consumption got worse with the new versions...

While I've never done any flight complex enough that would cause an OOM, I do hear a lot that OOMs were pretty much gone with 2.2 and that after 2.3 they came back. I guess they added something which in turn cancelled the vegetation autogen optimisations introduced in 2.2.

 

One tip is to be very careful when you're selecting a vehicle; apparently going through different aircraft liveries in the Vehicle Selector increases the base VAS.

Yes, the same here...after v2.3 OOMs are back. :(

 

Marko

 

 

selecting a vehicle; apparently going through different aircraft liveries in the Vehicle Selector increases the base VAS

 

Thats d..n stupid programming. :mad:

My question is why is P3D still holding data in memory from airports that were over 500 miles away at the time of my OOM?

Did you ask LM this on their forum too?

Spirit

I got an OOM yesterday over the middle of nowhere. There is something seriously wrong with 2.4. I have to be so careful now where I fly. 

It was raised in another thread recently that LM must be getting close to the limits of what's possible with the old 32bit code. This would seem to support that theory.

It would be a pity having all those new features and eye candy, but not being able to use them all together, even when your hardware can handle it.

This is curious, for me the VAS management seems better in 2.4. Several times, when on final, I'll start to hear FSUIPC's ping, indicating the imminence of an OOM. But all of the times that happened P3D managed to release some memory, and I was able to land and taxi without problems, everytime. Never got an OOM.

 

Cheers!

Thats d..n stupid programming. :mad:

 

I know, and I've got to say I'm quite disappointed this issue hasn't been fixed even with 4 updates.

I started getting OOMs in v2.3. Still only very short flights in v2.4, so dunno if it has changed.

Using 512k clouds and "normal" autogen (both veg and buildings).

 

In FSX I never had OOMs, nor in v2.0-v2.2.

As I said months ago regarding P3D2, LM with every new version is fixing bugs from previous versions, but introduce new, major frustrating bugs. And that is perpeetum mobile sadly. I wonder how many builds and versions will be released when we can say "and now we have a clear, bug free, stable versions of improved FSX". Probably in a year or two, if we have luck.

I was getting ooms in 2.2 but haven't had any in 2.4, so far. Flew from Calgary to Vancouver in the Carenado B1900 over Orbx scenery the whole way with ASN weather and REX cloud textures with no issues. But I have no doubt that you folks are having the issues you say that you are. It's a confounding program the way it fails for some but is fine for others.