It's a matter of adjusting your settings and not to simply blame one addon

 

And I hadn't had a single OOM in FSX till the 777 install. (not blaming)

 

I stated that it happened at FSDT YVR, and I speculate it had to be that.  Not 100% blaming the FSDT.  I understand it's a combo of everything.  Since I hadn't had an OOM before, something must be getting overloaded now I have the 777 installed.

 

And YES obviously OOM will continue to be discussed till the end of (fsx) time.  

OK - got Process Explorer. Virtual Size is solid at 2.53 Gb.

 

Currently at 69135N. 6 hrs 54 minutes.

 

Best regards,

Robin.

I'm 100% with you.  Lots of us here have got OOM when flying in to FSDT CYVR so I think we need to look at these other options too that are being listed to try.  I wouldn't be surprised if it is the culprit.  It's a huge hog.   

Its nothing to do with CYVR, nothing to do with 777 or even NGX. I agree with Dave. Its all about what your running. Dont expect max sliders. I hope you installed with the update with the ability to choose your textures. Dont use 4096 for one thing. 

 

When I reinstalled FSX, I did a test with CYVR since everyone was blaming it. I only installed CYVR and the NGX. no weather nothing else. I could fly in and out of YVR all day and not come anywhere near OOM 4gb limit. It hung around 2.6.  When I started adding PNW, and weather, its crept up again. Putting up the sliders to max adding more. So whos to blame now? Its not CYVR or any detailed airports fault. 

 

If you dont believe this, reinstall FSX clean, and install a detailed scenery and the 777. You wont get an OOM because nothing else is installed and included in part of the 4GB VAS limit. 

 

Ryan said it best in the intro.pdf.    The error from Microsoft should read your FSX has run out of Virtual Address Space. (4gb) Not the ridiculous your out of memory error.  If that was really true, then if you had a 32gbs of ram you would have cleaned that out, and we know that is impossible with most applications, let alone a 32 bit app.

landing in about 50 mins time Robin?

 

 

Its nothing to do with CYVR, nothing to do with 777 or even NGX. I agree with Dave. Its all about what your running.

 

Yes I get that.  All along I got that.  What I have been meaning is the combo of my settings and flying in to FSDT with the 777 caused the OOM.  Better?

 

 

Dont use 4096 for one thing. 

 

If I change my texture max load in fsx.cfg from 4096 that should do the trick, eh?  I don't need to re-install FSDT do I?  

landing in about 50 mins time Robin?

 

About 1 hour 20 mins from now. FMS predicting 0509z, time now 0354z.

 

 

 

Best regards,

Robin.

 

 

If I change my texture max load in fsx.cfg from 4096 that should do the trick, eh?  I don't need to re-install FSDT do I?  

 

That entry should be 2048 or 1024. You dont need 4096 anything as it uses large amount of ram. The ngx doesnt need to run in 4096 textures. It still looks great at 2048. Same goes with Clouds, and water. Ensure they are all installed with 1024. This entry should be a overall general limitation from what I understand. 

 

As for YVR- There is an update. When you install it, it will ask you which textures to use. Use the medium or lower grade. 2048 or 1024. There isnt a whole lot of difference in visuals, and if it helps contribute to less VAS usage, then its worth it. This principle applies to any addon. Scenery, or aircraft. 

 

 

Auto gen reduction etc?

 

That will put me over the top.  See my other thread http://forum.avsim.net/topic/418713-pmdg-777-lod-95-4096-textures-fb-ksfo-rex-4096-is-possible/

Estimating Anchorage at 0515z. Setting up for the ILS RW13.

 

TAGER6.TAGER BGQ.ILSRW15

 

7 hrs 38 mins. 65146N.

 

Memory in use: identical to my last report.

 

Best regards,

Robin.

That entry should be 2048 or 1024. You dont need 4096 anything as it uses large amount of ram. The ngx doesnt need to run in 4096 textures. It still looks great at 2048. Same goes with Clouds, and water. Ensure they are all installed with 1024. This entry should be a overall general limitation from what I understand. 

 

As for YVR- There is an update. When you install it, it will ask you which textures to use. Use the medium or lower grade. 2048 or 1024. There isnt a whole lot of difference in visuals, and if it helps contribute to less VAS usage, then its worth it. This principle applies to any addon. Scenery, or aircraft. 

 

Roger.  Re-installing the update with lower textures.  I'm also going to adjust the sliders in FSX a few notches lower, and confirm I've done ALL the PMDG Intro tweaks to my .cfg.  

 

I've never got an OOM with NGX in to FSDT, however it would always pause the sim close to the airport as if it was going to not respond, then it would come back to life.  Maybe these fixes might fix that for me.  

 

Thanks for the info.  

As my setup uses 3.monitors with a resolution of 5040 x1050 as one wide outside view the first I did was testing the VAS in a very heavy situation to avoid OOMs.

 

By setting the LOD radius to 5.5 max I can fly with the NGX over photoscenery with autogen and use 2048 textures.

Inthis way there will always be a minimum of 400 mb VAS left

1st flight and OOM. KPAE to KORD. Never had single OOM in the NGX to ORD, ever. I'm tired, I'm going to bed.

Changed tex max load to 2048.  INstalled the 2048 FSDT CYVR.  Sitting at gate with 2.9 VAS load monitored by Process Explorer.  Sound good?  Who knows what I had before.  Obviously it was not good.  Fingers crossed.  Thanks gents.  I'm out.  

must be a  nice approach there Robin

I can't even get through 5 minutes without it crashing and this is on an alienware R4!  my VAS was around 2.5.  I tried all the tips and tricks and I am still having issues.