I'm pretty sure this is only true if you're running a 32-bit OS.

I think on a 32-bit it is actually 2 Gb.

Yes, I saw those three fixes too. It's a bit odd indeed. 

 

We'll see how it all works out! And I indeed hope to get it sorted…  ^_^ As I said, those default textures don't cut if for me. 

 

Could this be the same issue albeit in a different area?

 

http://www.prepar3d.com/forum-5/?mingleforumaction=viewtopic&t=4315

 

Daz

 

 

Could this be the same issue albeit in a different area?

 

Sounds similar, at least when it comes to VAS looking okay but suddenly getting an OOM. 

I have been flying around ENBM and many other airports in Norway wwith the freeware add-ons and FTX global. I have flown both during winter time and summertime, with default planes and addons. Most of the time I use OpusFSX for weather.

I have not experienced a single OOM, although I have experienced different types of crashes (e.g. when selecting a parking position in GSX after landing at ENBR yesterday).

This was before you mentioned any of your specific problems with this area, however, so I can do a few flights this evening in that area to see if anything occurs.

What I do experience is weird frame rate drops. For instance, I loaded up the MJC at ENBR yesterday evening and got around 10 frames per second. I decided to try a different airport loaded up at ENVA with the same plane and still with OpusFSX. This gave me 35 frames per second (lock I have set in Nvidia inspector). When flying from this location to ENBR the frames dropped a bit when approaching ENBR, but they were never below 25 this time around. This could be weather-related, or it could be some combination of problematic textures, something weird with the ENBR airport, I just don't know. I did try to switch to a less demanding weather theme when I was experiencing 10 frames per second at ENBR and reduce the cloud coverage (which set at maximum coverage and area), but this did not affect the frame rate in any significant way (increased with 2-3 FPS).

 sooooooo.......... is there a reason why you posted that, but neglected to tell us what "limits" are keeping you OOM free? Im not sure what value your posts adds to this thread.

 

I expect there are enough variables in-play that my limits may not be precisely your limits.  And my preferences may not be your preferences.  You're going to have to do your own tuning, based on what visuals you prioritize.

 

The point is simply that it is possible.

 

Obviously most of us are having issues. Share your secret please. 

 

Ok, here it is: 

 

I went back to default settings and starting adjusting things upward, one notch at a time, until I started seeing occasional terrain spikes.  Then I backed a couple of things off a notch and haven't had any more problems.

 

I'd noticed on the OOMs that I experienced that I always started getting terrain spikes right before the OOM, though the framerate stayed high.

 

I didn't test exhaustively, but terrain mesh seemed to play a huge impact in spiking and OOMs.  At 1m mesh, I'd get about 90 seconds of flight followed by an OOM.  At 10m mesh (once I gave up on the idea of 3D waves), spiking is eliminated and I was able to turn all the shadows back on.  They are at medium quality, but with the draw distance pushed all the way out to 24,000 (better for mountain flying) thanks to Jeroen's tip on changing that.

 

I now have great performance (30-60fps) flying over FTX Global and over ORBX regions, with no more OOMs or problems of any kind.  My LOD is only 4.5 but all of the autogen is set to one notch below max.  Could it look a little better with higher settings (and better hardware)?  Sure.  But I'm satisfied "as-is" and it's a big improvement over my FSX experiences.

 

I took some screenshots during one of my test flights.  I've actually bumped the autogen up a little, added vegetation shadows, and pushed the shadow distance farther out since then, but if you'd care to see what I'm calling "good enough" here are some pictures:  http://forum.avsim.net/topic/427867-departing-homer-lh-quest-kodiak-over-orbx-sak-in-p3dv2-caution-extremely-large-images/

 

 

have been flying around ENBM and many other airports in Norway wwith the freeware add-ons and FTX global. I have flown both during winter time and summertime, with default planes and addons. Most of the time I use OpusFSX for weather.

I have not experienced a single OOM, although I have experienced different types of crashes (e.g. when selecting a parking position in GSX after landing at ENBR yesterday).

This was before you mentioned any of your specific problems with this area, however, so I can do a few flights this evening in that area to see if anything occurs.

 

Thanks for the report and volunteering for the test! ^_^ If you do fly around ENBM, really fly around it for a while. The thing is, in my flight before things went wrong, I flew from ENBR to ENBM and didn't have any problems. Problems started when I wanted to take off from ENBM (in a later flight, after restarting everything) with heavy weather and circled around the mountains. 

This statement is so powerful IMO

 

What is exciting for ME about P3D v2 are the following in this order.

 

1) FSX is not an orphan any more...its been adopted by a loving family! HA Ha!

 

2) There is a future for FSX. Not so hopeless like it was 2 years ago when MS abandoned it..or so we thought.

 

3) LM is focusing on the right things... improving the core of FSX and finishing up the unfinished business of FSX.

 

4) The fact that LM is not trying to compete with addon Vendors. Instead leaving stuff to addon Vendors what they do best and taking on things that addon vendors cannot do or should not do..Mess with the core, Orbx was beginning to do some of that which I thought was not a good idea, This way, LM can be requested by Orbx to accommoddate what Orbx wants. Which is a better way to go about.

 

5) LM plans to put patches out periodicall (I think I am right on this) where fixes and issues could be addressed periodically rather than wait for a fix after 4 years.

 

6) Moving stuff over from CPU to GPU. (The best thing to happen to FSX). I couldnt believe someone complaining about this because he had an old video card. Sheesh! Thats like someone wanting to cut their feet to fit into their old shoe.

 

7) Everything else like shadows and what not are of secondary benefits! Nice to have things.

 

I cannot stress those  enough to the P3Dv2 skeptics... Yes..My current FSX seems better than the P3Dv2 at this stage..But I need to give myself some time to figure out P3Dv2 better,

I had my first OOM ever (never had one in FSX) while flying in freeware Norway with FTX Global and the Real Air Duke.  My settings were reasonable too. My guess is that there is something in one or the combination that is causing memory leaks.  If I had to guess, it would be Norway since there are photoreal textures and such, and it was not designed/tested for P3D.  Just a guess, though.  Wes's post on the LM forum was a good guide to the factors that cause OOMs.  For the time being, I've removed Norway from my scenery.  Maybe I'll try reflying the same route without it and see what happens.  Could also be the port over of the Duke causing issues.

 

Edit: I was using 1m mesh, so that could be it too.  I'll try dialing that back per RoboRay's advice.

FTX Global seems to pop quite frequently in this thread?

Did some more tests: without FTXG no OOM, no matter what I did. With FTXG OOM...

 

I will completely uninstall and reinstall P3D and all my addons and begin again (although there probably are all kinds of files scattered all over my HD's...). If that doesn't work, I might restore my OS disk and REALLY start from scratch.

FTX Global seems to pop quite frequently in this thread?

 

Yes, for me it is the cause of OOMs, but not for everyone. So there must be something wrong with my install. Which is scary because you never know how and when and where things went wrong... so they can go wrong anytime!

 

 

 If that doesn't work, I might restore my OS disk and REALLY start from scratch.

 

 

You're down to blaming your OS install?  

 

You really.. Really. Really need to sit back and ask yourself

 

"When did my problems start occurring"

 

if it's

 

"When I started messing with P3V2"

 

It's not your OS

You're down to blaming your OS install?  

 

LOL I know it's not my OS, which I installed only two weeks ago. I was only thinking of restoring a back up from the OS (won't take as long as really reinstalling it!!!) to make sure there are no leftovers from P3D and FTXG. Because of course there are leftovers and maybe those can influence things. But right now I am simply reinstalling everything first. I will test without installing any addons and then add them one by one, only after thorough testing. Yeah, you gotta love flightsimming...! B)

You may want to hold off on reinstalling FTXG until the 1.2 patch for P3Dv2 is ready.

So I managed to set aside some time to fly around ENBM for about 30 minutes. Affluent summertime using OpusFSX and FTX global. To top it off I just bought the Twin otter extended, so it was my maiden flight with this aircraft as well :-). I am action are quite happy with the landing, although it appears that both came in a bit slow (and I should probably not use reverse in air the to slow down :-) ).

The entire flight when smooth without any hiccups, stable at 35 frames per second. I recorded the last 10 minutes, and I was still able to get a frame rate of 30 while recording. I experienced some blurry textures in the beginning, but it seemed to sort itself out during the flight.

I noticed that the Twin otter does not react well to going out of beta/reverse, it really kicks forward.

I have attached the video since it shows off quite nicely clouds, shadows, and the Norwegian scenery. AA is at 4x, with 2SGSS and 16x AF.  When landing I noticed that I have some texture problems with the buildings. I'm not sure if this means that I have not installed correctly or if anyone else is seeing this?

I made it my mission to fly round ENBM today. I set the time to today so it's fall but wanted to start somewhere. After two hours of flying round and getting completely lost. I can report no issues. You know I don't have GlowBall but its worth having a control. Tomorrow I'll do summer.