Hello All ----- Well, like many, I was worried about a fix for my panels predictably locking up after about 20 mins of flight....After installing both hot-fixes, no joy. Still locking up, although the lock was resettable, it was almost too ugly to fly.I was upset. And from testing a number of complex add-ons the previous weekend, I had seen the problem there too.Not right. I spoke with a fellow simmer who suggested I check my fsx.cfg file for errors, and for a couple of things based on my system content: (1) Was I using the BufferPools function in the file? (2) What was the value I had set for TEXTURE_BANDWIDTH_MULT function? My answers were: "yes" and "125" Given my video card, a GTX460 with 1GB memory, I removed the BufferPools section COMPLETELY.I set the TEXTURE_BANDWIDTH_MULT down to 80 (still on the high side) but I have a 6-core CPU. And guess what. Not one hang in a bunch of hours of flying!! A first, and still going in the background.I sent a personal apology to the guys at PMDG for my shower of bad data which just added to their anxiety about their new product. All that said, the NGX is a beauty (how better to describe it) and after the normal bug squashing process, a real dream machine.It now sits in my hangar along side a raft of fine add-ons including the Queen of the Skies and the MD-11. Hope this helps some pilots out there --- Regards, Bob

Did it cross your mind to use the latest hot fix? Or was that not rectifying the issue?

Did it cross your mind to use the latest hot fix? Or was that not rectifying the issue?

Hi Zach -- I did note that I had installed BOTH hot fixes and still had my problem. At the same time, one or both of the hot fixes may have been enablers that allowed my changes to have the impact they did.I probably will never know. Thanks for asking!!!

The BUFFERPOOL value reserves the amount of memory for generating landscape mesh; setting this argument too high, than is the memory not functional; setting this value too low than the disk is taking over this function (page-filing) with as a consequence a stuttering frame rate; read the story here; In your case the w7+16Gb takes over the "page-filing" assuming that the virtual memory manages automatically the paging file size for your drive(s)

The BUFFERPOOL value reserves the amount of memory for generating landscape mesh; setting this argument too high, than is the memory not functional; setting this value too low than the disk is taking over this function (page-filing) with as a consequence a stuttering frame rate; read the story here; In your case the w7+16Gb takes over the "page-filing" assuming that the virtual memory manages automatically the paging file size for your drive(s)

Hello janvanne ---- yes, and thank you for your input. I was planning on testing the BUFFERPOOL function to its extremes to see that exact impact. I can see now while my system, without any allocation for bufferpool operation, runs very smoothly with a periodic hit in frame rate but tolerable. My goal is to find a small value that the bufferpool will operate with and not interfere with sim operation. The link you provided is a good one I have seen before -- very well written by the way. Thanks again and Happy Flying !!!!