I have also had OOM problems specific to PNW. They don't seem to occur in NRM or CRM. I've attempted a number of different "cures" but nothing seems to work. My first solution was to comment out almost all tweaks in my config file - no joy there, just more problems. I then tried re-installing PNW and my "Bermuda Triangle" airports (Skagit, Anacortes, and Orcas) thinking I might have a corrupted file but that made no difference at all. I then tried re-apportioning my VAS with the system SET command, giving my self the max allowed for a 32bit sytem and then decrementing gradually back to system default. That didn't help at all. Based on this thread, I tried adjsuting the AutoSave in the FSUIPC.ini file (I have the registered version) but I still get my OOM screen. What puzzles me is I used to be able to fly PNW - not well perhaps on my older system but I could at least finish a flight. Now, I can't taxi my A2A Cub to the runway at Skagit before the system dies.Any thoughts would be appreciated. Maybe it's just time to retire this old machine and get a new 64bit platform.ThxJim S.

I have also had OOM problems specific to PNW. They don't seem to occur in NRM or CRM. I've attempted a number of different "cures" but nothing seems to work. My first solution was to comment out almost all tweaks in my config file - no joy there, just more problems. I then tried re-installing PNW and my "Bermuda Triangle" airports (Skagit, Anacortes, and Orcas) thinking I might have a corrupted file but that made no difference at all. I then tried re-apportioning my VAS with the system SET command, giving my self the max allowed for a 32bit sytem and then decrementing gradually back to system default. That didn't help at all. Based on this thread, I tried adjsuting the AutoSave in the FSUIPC.ini file (I have the registered version) but I still get my OOM screen. What puzzles me is I used to be able to fly PNW - not well perhaps on my older system but I could at least finish a flight. Now, I can't taxi my A2A Cub to the runway at Skagit before the system dies.Any thoughts would be appreciated. Maybe it's just time to retire this old machine and get a new 64bit platform.ThxJim S.

Hi Jim,Welcome to AVSIM and the Unofficial ORBX forum. You can't taxi the cub to the runway? That's bad! I have not hear of hat happening so soon before. Instead of the A2A cub, what happens if you take the default cub (I know, I know, what a drag) instead. Does that make a difference. Are there any other patterns that you can discern? What about around Twin Oaks and Portland?Kind regards,

Hi Stephen,Yes, I've tried others. In fact, I just tried the new Twin Oaks update tonite in a Caranado C172 and managed one circuit before getting scenery spikes and then OOM. Sometimes just flying into the region will do it. For example, flying the Caranado C337 from Redmond, OR over the mountains to the Willamete Valley did the job. It's very puzzleing. I can fly all the way from Alberta to Boise with no problems other than a few stutters. I really need to solve this. The ORBX scenery is just too good to give up on it. Nothing else measures up to it in my opinion.Regards, Jim

Jim,I am deeply puzzled. Are you using *******' tweaks? Have you tried asking over at the official forums? There are a couple of guys over there that really know their business. Also, if there is something specific in those areas lighting the fuse, Holger would have the best idea I think. It sure does seem to be PNW specific to your system. Also there will be more guys checking into here throughout the next day that might have an idea as well.Alternatively, perhaps it is time for you to consider upgrading, and getting on a powerful 64 bit system. Just throwing out ideas...Kind regards,

Acoma, I seem to recall from other threads on OOM errors that a high LOD_RADIUS can cause that and it would probably be worse in the PNW areas than in other less populated areas, so if you are running a tweaked setting there, you may want to try setting it back to 4.5 and see if it helps.

Before the general G3D.dll FSUIPC fix I often could not complete anything but the shortest of PNW flights, for no more than a half hour or so before getting hit with that error. Therefore FSX did not run long enough to have the OOM error. Now that there are no G3D.dll crashes most of my ORBX PNW flights end with a OOM after about an hour of flying over intense areas near Seattle. It happened again last night. I flew a Caranado 340 from Jefferson to Cushman Narrows, to Bowerman, to Wax Orchards, to Vashion Island and got almost to S43 when it ran out of memory. I don't think that it is something particularily wrong with my machine hardware or software. I can go for hours flying from, say, Jefferson County to anywhere in Tongass Fjords (which is a fabulous addon), and on to CRM and SRM stopping at various places along the way.My settings are maxed out in every way, so I know it processes a lot of data very quickly with the CPU near 5.0 GHz and the GPU at 900Mhz, but the machinery itself is under no stress or duress at any time, and is completely flawless until it hits that wall. I don't want to lower my settings, for what is the point when the machine is not even challenged. Now awhile back I did a complete reinstall of FSX and 90G of addons. I installed FSSave and it worked flawlessly to save everything routinely, which seemed to help. But when I recently changed my Nvidia Inspector settings FSSave will no longer start. Very strange!Is anyone else experiencing anything similiar?Kind regards,

I've been using the 275.33 driver and have not noticed any OOM errors, but with a BP=850000000, I did get lock ups. I tried using the latest driver with a BP=850mb and I got my first OOM error. What this could tell me is that there could be a correlation between driver & BP setting and memory errors. I have not experienced any memory error with the 275.33 driver and a BP of 30000. Maybe Paul J can expalin what the BP=30000 means. I have also NOT experienced d3.dll CTDs since Pete Dawson's FSUIPC fixed most CTDs.I have settled on BP=0, FSX locked at 26, and water at H2x. If I experience any problems, I'll just go back to BP=30000. It was very stable but not as smooth as I wanted.I hope that this helps others.

Edited March 6, 201214 yr by DJJose

Acoma, I seem to recall from other threads on OOM errors that a high LOD_RADIUS can cause that and it would probably be worse in the PNW areas than in other less populated areas, so if you are running a tweaked setting there, you may want to try setting it back to 4.5 and see if it helps.

Thx for the suggestion but it's one I tried a while back. Since then, I just keep it at 4.5 - it seems to reduce some of the workload on my old system. unfortunately it doesn't help the OOM problem.Regards, Jim S.