I dont even turn on the VAS counter unless IM in ORBX territory

 

How does one turn on a VAS counter?  I've yet to have an OOM in 7 years of using FSX.  That could be from the fact I always reboot on every flight and also historically would set unnecessary services and apps not to run.

 

 

OOMs are not hardware/RAM related - they are VAS/32bit app-related.

 

I understand this idea on this however I notice when I'm flying longish flights in complex scenes physical ram gets used over 5Gb.  Can you explain what is happening there?  I have yet to get an OOM in 7 years of flying and have complex scenery and airplanes.  I do reboot and limit unnecessary services.

How does one turn on a VAS counter?  I've yet to have an OOM in 7 years of using FSX.  That could be from the fact I always reboot on every flight and also historically would set unnecessary services and apps not to run.

 

 

 

I understand this idea on this however I notice when I'm flying longish flights in complex scenes physical ram gets used over 5Gb.  Can you explain what is happening there?  I have yet to get an OOM in 7 years of flying and have complex scenery and airplanes.  I do reboot and limit unnecessary services.

7 years OOM free , that's impressive. Have you ever had a CTD in that time?

(...) I understand this idea on this however I notice when I'm flying longish flights in complex scenes physical ram gets used over 5Gb.  Can you explain what is happening there?  I have yet to get an OOM in 7 years of flying and have complex scenery and airplanes.  I do reboot and limit unnecessary services.

 

 

Currently 4.7GB for me. Of course you need physical RAM as well when using FSX. But it's impossible for me to have physical RAM utilization exceed 7GB. That's why you should be fine with 8GB RAM and a 64bit OS.

 

Even with those 8GB RAM your VAS limit for a 32bit application like FSX is 4GB - that's the tougher restriction.

Here, let me re-explain it to you:  'I can't tell how many users are experiencing this...'

 

Most people here have higher end hardware right now and as the poll so far notes very few experience OOMs in the recent past.  Now there is the occasional discussion so I have attempted to turn pure random anecdote into something somewhat more meaningful.

 

My point being is that OOMs have nothing to do specifically with the T7.  OOMs are not hardware or software related - the 4GB VAS limit is as a result of FSX being a 32-bit application.  If you overload it with anything and go over the 4GB limit than you will CTD - you can do this with the NGX or other high end aircraft add-ons, as well.

 

You seem to have a mis-understanding of what VAS actually is.  I'd read through the post that HighTower linked.  It got locked but there is still a lot of good information in there.

 

 

You seem to have a mis-understanding of what VAS actually is.  I'd read through the post that HighTower linked.  It got locked but there is still a lot of good information in there.

 

I know what you're distinguishing here, but as a practical matter I find it's quite relevant to know how many users are experiencing OOMs now w/ the T7 installed.  This doesn't really talk about VAS and certainly not that the T7 has any sort of design flaw in it--just that it's a significant user of VAS.  It definitely gives would-be purchases a heads up that they may need to take steps to reduce other impacts on VAS saturation and that may not be acceptable to all...would be purchasers.  

 

 

I'm using SceneryConfigEditor with "Groups" that I can deactivate.

 

Thanks for the heads up on this. Seems to work a treat. Funny how you can be pretty immersed in this hobby and still have little things like this slip by unnoticed.

 

 

7 years OOM free , that's impressive. Have you ever had a CTD in that time?

Some BSOD's but that was likely from overclocking cpu/fsb/memory etc.  NEVER have been flying and when straight to desktop--I guess that must be rare.

 

 

The best way to tackle it is place the ngx or 777 in no mans land where nothing much of anything loads, and note your VAS and work up from there.

 

Thank you for these explanations.   FSX as a process gets 2Gb dedicated of private VAS as I understand it.  What's a good choice to monitor VAS?  Performance Monitor?  Be nice to see it in a tray applet.

Thank you for these explanations.   FSX as a process gets 2Gb dedicated of private VAS as I understand it.  What's a good choice to monitor VAS?  Performance Monitor?  Be nice to see it in a tray applet.

 

VMmap.exe (Sysinternals).

PMDG explain OOM's very good in the "Introduction"-Document and they tell how to avoid them, too.

 

Thanks for the heads up on this. Seems to work a treat. Funny how you can be pretty immersed in this hobby and still have little things like this slip by unnoticed.

I know it, because it was announced in the German "FSMagazin". In the "Introduction"-Document, PMDG recommend it, too. I use it every flight. The Manual is a little bit tricky but If you try it ob yourself it would work,Too.

Someone break the VAS seal :t0103:

 

I know I know - the game is from 2006 it old etc.

 

But an update on the game cant be done its said :dirol:

 

But someone please do it anyway :p0305:

 

Jens 

VMmap.exe (Sysinternals).

 

I got this program but where do I read out VAS?

I got this program but where do I read out VAS?

 

 

"Virtual size".

Aren't they working on some tool to lower the memory impact of the 777? :mellow:

Aren't they working on some tool to lower the memory impact of the 777? :mellow:

 

 

Performance Manager - similar to un-checking the high-res VC option. See their pinned 'known issues' thread.