July 20, 201411 yr using the cam means 3 additional opened FS windows. Its not just a hit on fps it fills the needed FS adressing space, too. The bad thing this space called "VAS" is limited regardless how much physical RAM you have. On 64 bit operating systems a 32bit application like FSX can't handle more VAS than 4gb. Before SP2 and acceleration-pack it could just handle 2gb without hack. (LARGE_ADDRESS_AWARE flag) "The so called 3GB patch" So your job is to lower your settings to stay within this limit even in the worst weather and the most demanding area. no LOD > 4.5 in your fsx.cfg limit your textures water/clouds (1024) uncheck airports and sceneries you don't need for the actual flight in library reduce range of weather and layers don't use HD liveries for your aircraft dont't use addons with your widebody which are designed for VFR flights (ORBX vector, etc...) if you have a second pc, or an old laptop,.. whatever it could be easy to monitor your actual VAS consumption via wideFS and VASMonitor. tools like processexplorer do no t work via network so you have to stay in windowed mode.
July 22, 201411 yr Author Can you link me VASMonitor ? Thanks a lot!! Can you link me VASMonitor ? Thanks a lot!!
July 24, 201411 yr Can you link me VASMonitor ? Thanks a lot!! You'll find it at AVSIM Library search for "VAS Monitor" after login http://library.avsim.net/login.php I finally want to add that traffic also claims VAS. Forgot to mention, initially.
Create an account or sign in to comment