They key word here is default 737. Of course you will get high framerates and low memory usage with default airplanes. What is the point of that post? Everyone here is talking about complicated addons like the PMDG 737 combined with the scenery causing problems.

 

The point is that everyone who has the NGX thinks that its FSDT Scenery or in this case this thread being CYVR. Im at max settings and using HD textures. The VAS is well below the limit. Once I install the NGX back on, all that will change. I guarantee it.

The point is that everyone who has the NGX thinks that its FSDT Scenery or in this case this thread being CYVR. Im at max settings and using HD textures. The VAS is well below the limit. Once I install the NGX back on, all that will change. I guarantee it.

 

Indeed it is a combination of things that causes the OOM's. I tried things maxed out in DX10 with all the usual combinations though with REX clouds at 1024 and I'm right at the limit upon loading the airport 9.4 nm out using the GRIZZ aproach on the NGX from SFO. The pending update which saves 200 mb should get me over the hump. Interestingly enough, last night I had a rare SmartAssembly on the descent as I was going back and forth from full-screen to windowed mode to check VAS usage. I'm using FSUIPC so it reloaded the flight right at that point which was about 60 nm out. My reloaded flight was using almost 1 gb less in VAS than the initial flight and I was able to complete the descent with no problems. I think one of the biggest problems in FSX is that it doesn't completely clear out of range scenery/aircraft so this starts to add up and can lead to OOM's in dense areas such as CYVR.

Indeed it is a combination of things that causes the OOM's. I tried things maxed out in DX10 with all the usual combinations though with REX clouds at 1024 and I'm right at the limit upon loading the airport 9.4 nm out using the GRIZZ aproach on the NGX from SFO. The pending update which saves 200 mb should get me over the hump. Interestingly enough, last night I had a rare SmartAssembly on the descent as I was going back and forth from full-screen to windowed mode to check VAS usage. I'm using FSUIPC so it reloaded the flight right at that point which was about 60 nm out. My reloaded flight was using almost 1 gb less in VAS than the initial flight and I was able to complete the descent with no problems. I think one of the biggest problems in FSX is that it doesn't completely clear out of range scenery/aircraft so this starts to add up and can lead to OOM's in dense areas such as CYVR.

 

That is indeed interesting. Someone else mentioned that as well so not a coincidence. A sort of memory leak if you will. In my tests from a clean install, the memory VAS stayed roughly the same even if leaving the area and returning, probably because orbx is not loaded. All these addons just compound and get worse. Just nice to see a scenery with max settings which is why I went to check out KLAX and KORD to see the differences. NGX installed will kill all of that. As a side note, KLAX and CYVR werent that much difference in VAS usage.

Hi Srdan, this FSUIPC warning of impending doom, where in FSUIPC can this be found? I've looked everywhere but can't see it...

hi howard not sure about this but i could be wrong, but i think its coded in you dont need to check anything since i had the ding dongs before and i hadnt check anything in fsuipc not that i know of. Dont worry you cant miss the sounds lol sounds like soem one at the door

Hi Srdan, this FSUIPC warning of impending doom, where in FSUIPC can this be found? I've looked everywhere but can't see it...

 

hi howard not sure about this but i could be wrong, but i think its coded in you dont need to check anything since i had the ding dongs before and i hadnt check anything in fsuipc not that i know of. Dont worry you cant miss the sounds lol sounds like soem one at the door

 

No, it’s not hardcoded.

 

It is a user option in your fsuipc4.ini file.

 

If it is missing, then add “OOMcheck=Yes” (w/o quotations) to your fsuipc4.ini file under the [General] section.

 

Cheers.

No, it’s not hardcoded.

 

You have to add “OOMcheck=Yes” (w/o quotations) to your fsuipc4.ini file if it is missing.

 

No, not hardcoded but as I mentioned earlier and confirmed when I got home this evening - the default .ini file has this set to "yes" by default. Unless you've changed something, you'll have it enabled.

 

Scott

No, not hardcoded but as I mentioned earlier and confirmed when I got home this evening - the default .ini file has this set to "yes" by default. Unless you've changed something, you'll have it enabled.

 

Scott

You are quite right, it is on by default.

 

Another reason for it missing could be a User having an older version/installation of FSUIPC.

(Before it was implemented or added by Pete to the ini file, I think sometime early in 2012)

 

@Howard: Make sure you have the latest version of FSUIPC.

 

Cheers.

The point is that everyone who has the NGX thinks that its FSDT Scenery or in this case this thread being CYVR. Im at max settings and using HD textures. The VAS is well below the limit. Once I install the NGX back on, all that will change. I guarantee it.

 

Well it's not just the NGX, it's any addon with high detail that adds to the virtual memory. Take the LS MD-80, or any other detailed airplane and you run into the same problem. The high memory usage of an addon airplane plus this scenery brings the usage over the cliff. Of course a default airplane will work fine with any scenery addons you throw, but that's not the point. It just shows how basic default airplanes are.

No, it’s not hardcoded.

 

It is a user option in your fsuipc4.ini file.

 

If it is missing, then add “OOMcheck=Yes” (w/o quotations) to your fsuipc4.ini file under the [General] section.

 

Cheers.

 

thx for the info yea i got the latest fsuipc so it must have been included when installed since i never added that part at all

Thanks fellas, I never heard it chime when I got my initial OOMs at CYVR, so I guess I will have to check the Windows sounds as I'm pretty sure they are turned off...

Woo hoo! Thread back open haha.

Tried out a flight today. FSDT KORD to FDST CYVR in the NGX, AS2012, REX clouds and orbx. Was tracking the VAS and ended up landing with no OOM. 3.6GB topped out on the VAS. Some heavy pauses when the CYVR scenery kicked in on descent into Vancouver and a few more pauses, not quite a long, on final approach. All in all pretty pleased with it and will need to do a defrag of my hard drive to try and mitigate those stutters.

Its just simply how much you all have loaded and running in FSX. There is no 2 ways about it. Its not CYVR its not KLAX or the NGX or any upcoming addon. These are high quality addons and you can be sure they are optimized the best they can with FSX limitations.

 

My FSX fresh install confirms it all and for obvious means. The max VAS I saw with NGX and CYVR installed is 2.6GB. Loading orbx PNW its now at 3.2GB. If I keep loading high quality stuff or HD clouds Im for sure going to hit the OOM ding of doom.

Until we get some hope of a 64bit platform, we just have to accept the fact there is only so much we can load. Go with 1024 clouds, as it doesnt look that much different and helps towards OOM and FPS.

 

Also the alpha searcher and the DXT fixer improved studdering.

 

And for extra security if your VAS is nearing the limit,albeit somewhat unrealistic, save your flight 50 miles out and reload it. youll gain a few extra MB.

Woo hoo! Thread back open haha.

 

Probably only because of the system restore Avsim did that erased the past few days of posts. Jim will probably lock it again when he finds his work was undone.

Didn't make sense to lock it anyway. A decent discussion in my opinion.