Here's the scoop,

 

With looking at another site this evening, I realized that I had a wrong syntax entry as the first of my FSX.cfg file. I changed this ONE header and its entry, and have stopped my O.O.M's and CTD's after about any flight going over 20-30 minutes.

 

Ok, so here's what I had until I changed it to a correct version;

 

[bUFFERPOOLS]

BufferPools=0

 

I then changed it to read;

 

[bufferPools]

UsePools=0

 

------------------------------------------------------------------------

 

As a result of this one change to my .cfg file, I am no longer O.O.M.'ing and CTD'ing.  For whatever reason, my previous entry (and its incorrect syntax), was apparently causing FSX to do what it needed to do to O.O.M me after about a 30 minute flight.  I am delighted to report that now I can fly 120 minutes and more with all my settings maxed out in the graphics sliders, over FSXG and I'm the one now ending the flight!

 

So, good, bad, or indifferent, this is ALL I did to my FSX.cfg file, and it made the world of difference.  Just to note, all my previous posts that referenced any O.O.M's and CTD's after about a 30 minute flight....was happening with my first entry of this post. I had incorrectly entered that, and this seemed to be what was causing all my O.O.M problems.  Go figure!

 

Just wanted to post this as a head's up to others, to check out what syntax they are using for this .cfg section. You might want to change this section to my corrected second version, if you do not already have this in your .cfg.  If you do experience chronic O.O.M's...then at least, give this a go, and see what it does for your usage.

 

Graphics Card in use: GTX 680 2 GB.

 

Post Edit:  Straws in the wind...straws in the wind...for MONTHS!  I had been chasing so many other 'possible reasons' for my chronic and fatal 20-30 minute O.O.M issue...and it was the subject of this post that was causing it!  Dang!  I just came back to report that I just had another great flight across Michigan and glad to report no further O.O.M and following C.T.D. that I was suffering for over a year with that wrong heading syntax in place.  

 

You add, FSG-X and no O.O.M.'s...and what do you get?  An AWESOME simulation enviroment!  FSGX, probably the best add-on I have ever purchased for a total-all-in flight experience.  The real world, and what it actually looks like?  I got it....FSXG......   Let the happy flights begin......O.O.M's in the rear-view mirror....and glad of it...

 

Mitch 

Really?  I have used both....and even "poolsize=0" and never had any effect on OOM errors or CTDs ever.  Interesting.

 

And you can check out my dated PC specs in my profile.

Really?  I have used both....and even "poolsize=0" and never had any effect on OOM errors or CTDs ever.  Interesting.

 

And you can check out my dated PC specs in my profile.

Yessir...really.  That's all I did tonight, that changed my O.O.M. on-going situation, for over a year (probably as long as I had entered that in the first place...).  I entered the second reference this evening as stated, and went flying. I just kept flying for over two hours, actually. I  came off another cross-Michigan flight over FSXG, and again, no issues, landed at KORD, no problem. Can I speak for every system and config file out there? Nope. I can only relate what I changed (cause and effect), and what happened.  If you could see the smile on my face...it could light up the continent!

 

I can finally enjoy FSX, full out, and expect to SEE THE NUMBERS at the end of the flight!  For over a year, or longer...that was not even going to happen....lol!

 

Cheers,

Thanks. Will have to try this.

Thanks. Will have to try this.

I can't say that it will work for every system, of course, but I do hope that it will work for you. It is encouraging to note that this is the only thing I changed in my config file, and that made all the night and day difference.  I was plagued with this (OOM and resultant CTD), and now it appears to be corrected. 

 

Funny, how you pursue a solution for months to years, and find none, and then,... when you are not even looking, that 'solution' falls right into your lap....

 

Off to bed...good night to all!

 

Mitch

The two you can use:

PoolSize=0

UsePools=0

Some of the most common tweaks including the bufferpools can be easily applied and unchecked with a freeware utility called flusifix without the danger of wrong syntax. Check it out. http://www.wolfgang-picheta.de .There is also an English version available.

Poolsize=0 or Usepools=0 will do the same thing, but bufferpools=0 was not correct. This is why some good tweaks are not working for some people, they need to be applied in the right way