I don' have this problem, but I sugest to all that have that as soon as they have an OOM, delete your P3D.cfg and run the same scenario again...see what happens., Then think about your addons if you get another one.

 

Jorge

Never had an OOM. I always fly the NGX to intensive airports. Yesterday for example I flew Tropicalsim TTPP to FSDT KIAH then Tropicalsim KDCA. Did not have an OOM the whole day and that's with out restarting the sim.

I flew yesterday IAH - YVR - DEN - IAD with a pmdg 737 and no OOM. Today started my flight in DXB to Lisbon and got OOM 15 min after the start of the sim. Still at the gate. And this is not the first time i get OOM in p3d with a 777.

This I didn't know so thanks for pointing it out, will keep that in mind.

 

It's not as big a killer as others.  All it does is tell the simulator to basically more and more vertex points on the terrain mesh making it more detailed but ALL those new vertex points have to be stored somewhere.   If you are a high tube flier, having Tessellation maxed out is useless.    Tess is really, in my opinion, useful for the GA fliers that are below 10k feet where you can really see the details of the mountains and valleys.

Ok, got it.

 

Although I'm a tube flyer I do like as much detail as possible as long as my FPS and VAS allow it and especially so when departing and arriving in mountainous areas.

The title reveals the fact that users expectations are often a bit off the mark. OOMs are a local machine issue if the overall majority of users are NOT experiencing OOMs.

Local issues first, followed by LM if unable to resolve the first. :rolleyes:

The only OOM I've encountered so far was on a flight from Montreal (FLY TAmpa) to Toronto (FLY TAMPA) using the Aerosoft Airbus. The flight was just over an hour in duration. I got the OOM as I was taxiing to the gate in Toronto. There's no doubt in my mind the it was the FT Toronto scenery. I've flown much longer flights with addon airports and not had this problem.

I've only ever had one "OOM" message in P3D and that was a few weeks back when I tried to install some FSX airport scenery for Croatia. Since removing it I've had no repeat of the message.

 

+1 Worth keeping the tessellation slider low especially on long high altitude flights. I also switch to another graphics profile when flying above FL120 - no need for tons of autogen above that altitude when you can't see it!

Reading these threads is a little depressing.

 

If I bought a car, would I be able to hold the car manufacturer responsible for an aftermarket stereo that I put in it blowing up the stock speakers?

 

Likewise, If I bought a PC game like Skyrim, then added so many mods to it and an intensive ENB package that crashed the game, would I hold Bethesda (publisher of Skyrim) responsible?

 

If you feel that LM can do better, instead of voicing your complaints to people who can do nothing about it, it's better to take your complaint directly to the source: http://www.prepar3d.com

 

Otherwise, if you are asking for help from the FS community, ask for it directly and respond to any help offered. Poop or get off the pot! :rolleyes:

 

 

 

 

 

No offense, but I find that hard to believe, unless that is, you have all sliders full left...which negates the point that the OP is making. When will LM address the real problem?

 

I got a VAS warning today after one circuit at the new Orbx Sedona in the Iris Texan Driver. I'm running Medium LOD, 1024 textures, and Normal Autogen sliders...give me a break..

 

I have a video on my YT channel of a flight in the new Texan where I ranged all over the scenery coverage area of Sedona. In addition to what is seen on the video, I shot about 1 hour of footage there (different angles and whatnot). Autogen was at Normal for buildings and Very Dense for vegetation. Tesselation maxed, LOD 5.5. Terrain Shadows ON. Cloud shadows OFF. Because of all the static aircraft available there, I disabled AI traffic. I also made the video in two segments. For taxiing, I enabled most of the control panel items for the airport. For the flying portions of the video, I had the control panel pretty much limited to static aircraft. For the whole experience, max VAS used was 3.1GB.

 

One question, did you start at another airport and then use the Go to Airport function and switch to KSEZ? Switching between high end airports like that is the only circumstance I have ever had memory issues (twice).

I did a 20 minute flight though yes my autogen settings are set to very dense but I didn't fly into a payware airport I flew into KRNT Seattle. Large citys always brought me near ooms

One easy check - use FSUIPC to log remaining vas - set it to display on screen -

 

Now start your favorite flight and notice remaining VAS. Exit - Restart and load a different flight.

 

You'll find that the remaining VAS changes drastically with location, aircraft, etc.

 

So, if you can fly from A to B in a Cessna with no issues and get OOM when you use a 777 - is that the fault of LM?

 

As others have pointed out, it really is not only system specific but flight, location and settings specific.

 

I have some flights that start out with almost 2G free VAS and others with 800-900mb. Guess which one might OOM first?

 

 

Vic

I think I am going to contact Pizza Hut and ask them why they aren't doing anything about American obesity.

Do you guys think the message has been delivered by now?

Why don't people put their puter specs on here.  I have a GTX770 graphics card, all sliders at high or ultra high and use REX Essential and FS Commander and AI aircraft on 90%  This is not top of the line graphics card but with adjustments like no VSyn, Anistropic 16x and a reasonable frame rate of max 30 can give good results. Just flew from RKSI North Korea to Atlanta (6199 nm) and not a hiccup.  I have my FPS set to 30 and my eyes see everything smooth.  I think I'll be getting a Titan GTX Z so I can really laugh at these types of complaints.