Search the Community

I am using p3dv3..I have the latest alpha 1.679 as of today. I notice from time to time.. the vas usage lights up and dings. I was wondering with the use of Process Lasso...what is the best setup for ChasePlane as far as all of the settings across the process Lasso line from left to righ..(ie: Rules..Priority Class...etc etc.) I have an eight core AMD 9150.. I know there is a setting inside Chase Plane with CPU Assignments 0-7. The green button is to the right for "Dynamically select xxx". Does this need to be set or unticked if I am using Process Lasso. Do they override each? I have Windows 10 and latest p3dv3. I am running AS2016...real traffic..proatcx and Maybe LittleNavConnect with Little NavMap on a networked machine. Any help appreciated. I typically fly the new PMDG 747v3. As a side question..anyone using Razor/Cortex https://www.razerzone.com/cortex in conjunction with and does it really work? lol Bestest to Everyone :) Bob M.

Hello, After tweaking/changing settings, now my FSX:SE performs very good, very smooth. The only problem I have is VAS. I have tried several things to reduce but I do not know if I have done all or I am missing something. Almost all my flights I restart sim before TOD but after landing I still use around 3.8 - 3.9GB VAS (using major airports from FSDT/Flytampa/Taxi2Gate/Flightbeam/LatinVFR). Addons: PMDGs/FSLabs A320X ORBX Global AS16 + ASCA Chaseplane For now, TEXTURE_MAX_LOAD=2048. Use Simstarter NG to active only the airports that I use for the route. FSX settings as below. FSUIPC max AI to 10 aircrafts only, no vehicle/boat/ship. Any help would be very appreciated! I do not mind lower the settings because I only fly IFR and look from VC. I just do not know which setting that affect VAS. Cheers Hoang Le

This document is long but if you're interested in why you're suffering from OOM errors and how to avoid them, grab a cuppa something and read on... What do you mean I have to reinstall again? Since installing Prepar3d v2.4 and v2.5, I too have been suffering from OOM errors as well as 'random' crashes to desktop. This has resulted in four reinstalls of Prepar3d and two system reinstalls. Not a pleasant way to spend my spare time but I learned a lot doing it, so time well spent. After my most recent reinstall of Prepar3d v2.5, a few weeks ago, I made the decision to only install native add-ons or non-native add-ons that I can install manually, without the Migration tool. I also decided to install them one at a time, instead of all at once, to compare their performance, evaluate their use i.e. 'do i really need this?', as well as optimising them for use in Prepar3d. 'These go to 11' If more third parties optimised their add-ons and if consumers were more conservative with their settings, a lot less people would be suffering from OOM errors and random crashes. As consumers, we shouldn't have to optimise our payware but as most third party add-on developers focus on looks and not performance, you will never get the best performance you can 'out of the box'. There are a few exceptions where developers provide optimised products that need no further optimising but they are still the minority. The main problem is that most consumers still don't know how to optimise their add-ons and/or want to spend the time doing it. The attitude, 'I paid for it, it should work' prevails, which, as a consumer, I understand, but as someone who wants their sim to look and perform as best as possible, I can't accept. From a developers point of view, I understand the old arguments but they hold no weight with modern graphics cards and recent versions of Prepar3d, there are simply no excuses for not providing optimised products for Prepar3d. I haven't had any OOM errors in Prepar3d v2.5 since optimising my add-ons but I can easily trigger one if I want to. I don't get them any more because I check and optimise every add-on that I purchase and use realistic in-game settings that achieve a compromise between looking great and performing excellently. Multum in Parvo It is possible to have a great looking and smooth sim experience without having all the sliders to the right. By optimising my textures, I have seen a huge drop in VAS consumption and a very noticeable boost in performance. All I did was resize oversized textures (reduce from 4096 to 2048 or 1024 pixel width) and save them in the correct format with mipmaps (DXT1 no alpha, DXT5 with alpha). This cost me a lot of time but everything looks and runs much better now, no more shimmering in the cockpit and no more shimmering in external view. It's the difference between 1.3mb and 16mb PER texture in some cases. Multiply that by ten and you can see what's consuming your VAS. The irony is that the optimised version nearly always looks better. Compared to the time you can spend looking for that elusive holy grail tweak, this one actually has visible and immediate results. The mipmap VC panels option in the simulator does not work as you might expect, you will need to optimise the textures yourself if you want the best result. I have this option off. A quick example, I recently bought a brand new GA third party aircraft developed for Prepar3d. After installing it, I loaded it up only to see that the cockpit gauges shimmer, small text is hard to read and straight lines in textures look like marching ants as soon as I move my head using Track IR head tracking. Half an hour later, I had an optimised product, that looks much better and performs much better, with cockpit text and labels that are clear and easy to read, the gauges now look smooth and the external textures load instantly. The best bit, it consumes much less VAS and frees up resources to run the sim more smoothly. Plane spotting AI aircraft also consume VAS and can easily cost you 20 fps on top if set up too optimistically. UT2 is, in my opinion, the best looking and the best performing AI package, as long as you mipmap the textures correctly, but unfortunately unsupported for Prepar3d, and the last time I used the Migration Tool to install it, I had to reinstall Prepar3d after files became corrupt. My attempts at a manual install also resulted in a reinstall of Prepar3d. The only official AI package that I know of that has been developed for Prepar3d, My Traffic 6, fills the skies with all kinds of wonderful aircraft, even the textures are correctly mipmapped, but unfortunately the models are not as optimised as UT2, so unless I am extremely conservative with the AI sliders, I can cause my fps to drop by 20 frames, great for plane-spotting at airports but not that great if I want a smooth flight out of EGLL. Unification Everybody's setup is unique and no two systems will perform the same, even with the same hardware. This is why the process of 'unification', as practiced by people like Michael Greenblatt or Nick Needham, is so important. Unification doesn't mean tweaking cfg files or resizing textures, it's understanding how to design a system and then set it up correctly for optimal use. The right hardware, the right software, the right add-ons, the right settings... it takes time to learn and it takes time to set up correctly but once you get it right, you get the best sim experience available to the public. You don't need the latest hardware to run everything well, you just need an optimised system and a fast quad core processor. VAS is my currency The FSX/ESP engine was not designed to work with uncompressed textures larger than 1024 pixel width. Even if they load, there is always a price to pay. The currency is VAS. It's not just incorrectly sized textures without mipmaps, high resolution mesh has a price, even third party weather and ATC add-ons can cost you an OOM if not set up correctly. When I met the developer of FEX a few years ago, he showed me FSX running with 4096 pixel width ground textures. Not just at an airport, the whole world was covered in 4096 textures. FSX loaded and ran fine, no signs of an OOM error. This was proof of concept only and ran in a default install of FSX Acceleration but I bet if we had added all of the popular add-ons that we use today, the sim would have crashed too. Some developers have wised up and now offer an extra set of textures for their products, in a 'lower' resolution and are very active in trying to prevent OOM errors. Lower resolution doesn't have to mean it looks worse, default size 1024 textures that are well made look great too. 2048 is the maximum size I allow into my sim. Here's the reality... 4 badly optimised textures can consume around 100mb of VAS. 4 correctly optimised textures consume around 5mb of VAS. Mipmapped textures might appear to have a larger file size than same dimension non-mipped textures but in reality they ease the load on the CPU/GPU and prevent a kind of shimmering that people often confuse with geometry shimmer and try to combat with high levels of forced anti-aliasing. Ever wonder why when you load an aircraft in the Scenario Editor, it takes time to load the textures and when they appear, they are hard edged and unclear? Mipmaps is why, or rather the lack of. Wouldn't you like it if the textures in your shiny new third party aircraft were clear and readable and smooth? Maybe you don't care but the lack of proper custom anti-aliasing options in Prepar3D make the lack of mipmaps even more painfully obvious. Most Payware add-ons are designed to look amazing, that's why uncompressed over-sized textures are used so often. Why should a developer care? They have made a product that looks great and works fine on a default install of Prepar3d. They have done their job. We are purchasing the right to experience this product, no more, no less, it's like buying a ticket for a ride at the fair. We are therefore responsible for ensuring that these products are optimised. But if we combine an unoptimised aircraft with two unoptimised airports and then add high resolution mesh, terrain and cloud shadows, AI, full cloud cover, thousands of buildings covering huge Ultra LOD areas, hundreds of unoptimised cloud textures, what else could happen but... tl;dr - optimise your add-ons

I know there are a lot of VAS topics started in the forum about the T7 but it was in my interest to start a fresh one because the others are not FULLY quite my question/comments B) I am currently at CRZ (FL360) after leaving a default airport (Perth) with normal autogen and normal complexity..I only have FTX Global Base 1.3 installed and all my Vector entries are unchecked in my scenery library a long with all airports except the one I am flying into (as always when flying the T7). I left the airport with about 1.6GBs remaining and all was good...half way into my journey now, I have less than half of that. **warning big picture** http://i.imgur.com/EycHfVy.jpgre I am flying into Flytampa's Athens and I could be possibly hit with an OOM and all I have are default everything expect Global and the T7. From take-off to CRZ in the middle of Saudi Arabia where it is literally all dessert how can I leak almost 1GB - 9hrs in? I thought I loaded almost everything in Perth. Can someone break down why it keeps going less and less and less.....I have BELOW moderate settings, and I'm on a good system as well (4790k@4.6 & GTX980). I have more then compensated my sliders/scenery to just fly this thing without always having to worry about an OOM. I never would of thought being almost all default would ever still risk getting slammed with an OOM. comments, questions, concerns gentlemen?

Many third-party airplanes today are shipping with 4k/2k textures. While we can debate its usefulness to no end, the fact remains that they are quite memory intensive. There are ways to reduce texture sizes and mip them, but I came across an easy tool which makes it a breeze, http://www.nexusmods.com/skyrim/mods/12801/?, developed by AdPipino for Skyrim and other games. I let this program run through my airplanes folder, to reduce texture size to 1k and mip them also, and then I measured the results. All tests were done on runway at supposedly the most isolated airports in the world, Mataveri International Airport / SCIP. All situation were loaded after fresh start of P3D from saved flights. After loading I panned/zoomed around in both VC and spot view, measured VAS using ProcExp and GPU using MSI Afterburner. While VAS and its effects we all know, I am not sure about GPU memory and its effects, but I still measured it. GPU experts can chime in. System Specs: i7-4700MQ @ 2.8, 16GB 1866Mhz Ram, 755M SLI 2GB DDR5, 128+512GB SSD Settings of note: FFTF=0.0, AM=244, TEXTUREMAXLOAD=27, TEXTURE_MAX_LOAD=1024 Observations: We are saving about 150-300MB VAS, depending upon the Airplane. None of these aircraft had mips in their original textures. Some have 4k textures, some 2k. You might think that just by selecting 1024 as texture size in the P3D settings, it might reduce memory load. But this is not true as you can see above. This maybe because, none of the original textures are mipped, my guess. So if you want you can choose not to reduce the textures, but just mip them. I have not tried this. After reduction, I did not see any visual difference. There were no FPS differences between the textures sizes, so this does not do anything for FPS performance. The B1900D has shimmer in the cockpit controls with the original textures, but after reducing/mipping there is no shimmer :smile: So how can you do it easily? 1. Make a copy of the Airplanes folder in SimObjects directory. Let the copy be in the SimObjects folder itself. 2. Run Ordenador tool (link above), and select the folder copy you just made. And other settings as below Also in the More/Extras tab, un-select backup option, as we already made a backup. 3. Click Start and wait for 10-15 minutes for it to finish. (You may have to confirm the no backup and reduce textures options in the subsequent dialog prompts) 4. After finishing, I suggest you copy the log window and save it as text for future reference if need be. (for me the original folder size was around 21GB and it came down to 10GB after reduction) 5. Rename the original Airplanes folder to something like "Airplanes_ORIGINAL". 6. Rename your folder copy to "Airplanes" You can switch back and forth between original textures and reduced ones just by renaming the folders in future. I also want to try out the new BC6/BC7 texture formats supported by DX11, but the conversion speed is pretty pathetic with the tools today. Maybe in the future. Mega Airport experiments are next up, till then just imagine the savings! Edit: I just realized that the textures more than 1k and being cut in half, but not cut to 1k. E.g. 4k texture becomes 2k, 2k becomes 1k. So finally we are left with 4k converted to 2k. If we run tool one more time, it should convert the 2k (4k originally) down to 1k also. So more savings!

As more leading-edge developers push the envelope for detail, fidelity, and the "gee-whiz" factor, it has become readily apparent that FSX is being rapidly pushed over the edge of the infamous 4GB VAS cliff. I would propose that we, the customers, gently nudge our favorite developers to publish benchmark VAS usage for their latest products as part of the usual "requirements" list for OS, CPU, GPU, etc. If they published an average VAS usage, on a clean, vanilla copy of FSX, it would enable us to properly assess their new products in view of our current packages of add-ons to see what trade-offs we might have to make to see their product perform reasonably well on our individual FSX systems. For example, if my favorite suite of add-ons is currently pushing 3.2GB of VAS and I see a new "must-have" add-on which consumes an average 700MB of VAS, then I know ahead of time I'm going to have to do some trimming before I plunk down big bucks (euros, pounds, whatever) for the latest and greatest, and won't be blindly disappointed and disgruntled when the dreaded OOM bogey bites me on the butt. Just a thought.

Just completed a flight from FSDT KORD (Chicago) to FlightBeam's KIAD HD (Wash Dulles) and the flight was like night and day in comparison to previous versions of Prepar3D. I flew the PMDG 777 and had AS16 enabled. I had Megascenery Ultra Hi-Res scenery enabled for Chicago and in the Wash, Maryland, and Virginia area. In between I had GEP3D enabled (which has optimized textures). This was the same scenario for previous flights. I monitored and logged VAS via the FSUIPC module. FPS were set at unlimited which is different from flights from previous versions as I had to lock the fps at 30 to maintain smoothness. Previous flights from KORD-KIAD resulted in the amount of VAS to dramatically drop when on final at KIAD, from 1100000 down to 250 - 500 MB's depending on the weather (I had saved the FSUIPC reports but they are no longer there for some reason so much of this is based on memory). Most flights it was a slide show on arrival and some resulted in OOM's on final or on the taxiway. In Chicago, there was a lot of stuttering and fps were extremely low until I departed and got out of the Chicago area. Then fps and vas would start rising again until I reached my destination. So, bottom line, no fun. I thought I would have to wait until I upgraded from Haswell to the latest chipset before flying this route again. But, today, here are the results: Minimum frame rate was 6.5 fps (not sure where this happened as most of the time fps were well above 30 fps), Maximum was 157.5 fps Minimum available memory recorded was 1204Mb (or 1269872) Average frame rate for running time of 7489 secs = 39.5 fps Maximum AI traffic for session was 339 aircraft FPS went dramatically up when out of the PMDG VC and in spot or wing views. Still, FPS in the VC exceeded 30 fps every time I looked at the fps monitor. That's HUGE! So I'm really happy with this upgrade and happy to see progress is being made to enhance the usefulness of this simulator. I hope others are seeing a major performance boost too. Best regards, Jim

Hi all, Looking for some help on how to properly configure SceneryConfigEditor (SCE) for the following scenario with the goal of lowering overall VAS usage. Lets say I want to fly a flight where both the DEP and ARR airports are 3rd party airports that I have installed - as an example: DEP airport: FlightBeams' KIAD ARR airport: FSDreamTeams' PHNL ACFT: PMDG T7 I have the above airports "checked" in SCE I also have all the FSX Base entries "checked" in SCE I have all other payware and FSX specific airports "unchecked" in SCE. Are the SCE settings I have listed above correct? Do I need to have SCE entries like Eastcoast North America or Pacific Oceania checked too? Looking forward to hearing from the "Been There Done That" crowd...

Hi ppl I'm really frustrated. Fourth consecutive flight that I can't finish. After 2 blackouts in my neighborhood one CTD I was finally on final 08R KMIA (LatinVFR version 2.2, Miami City Dzwki) when my FSX Ommed. At FL360 I had 1.6gb of free VAS (I monitor my free VAS using FSUIPC). At FL100 and 20 miles from KMIA my VAS went down to 1.1GB, fair enough 1GB of allocated textures seems a lot of space left. I did an outbound turn to the west to intercept the ILS08R, free VAS was at 800mb. At 8NM VAS started to go rapidly down from 800 to 500, on short final it went from 300 to 200. I started pausing the sim to see the behavior, 100MB of VAS were added, but 5 seconds after 150MB. 100Ft AGL 120MB left, OOM. So please explain to me how the hell an approach to KMIA can drain 1.1GB of VAS from nowhere?. I tried everything, currently 1024 textures, Autogen Med, Scenery Complexity Dense, I don't use external view, all unused sceneries disabled. Addons: FTX Global + Vector FSGlobal LatinVFR KMIA PMDG T7 GSX AES FSRecorder REX Essential FSGRW FSRealTime vPilot IVAO MTP (three aircraft's in the vicinity) Hardware: -ATI HD6870 1GB VRAM (dx9 and 1920x1080) + SWEETFX and 4xSSMA -Intel I5 4670k -8GB RAM 1333mhz -SSD My CFG: // This file was tweaked on Oct 31, 2014 at 21:07 GMT using Bojote's automated FSX Tweaking & Tuning Service // Your 'original' fsx.CFG file was backed up at http://www.venetubo.com/fsx/5749e298f73176ab3a06d8c96fde19c2/backup/fsx_backup.cfg // This file is optimized as follows: 4 core(s), CPU speed 3, HT 0, GPU 4, PREF 2 // You can visit Bojote's FSX Tweaking & Tuning service at http://www.venetubo.com/fsx.html [MAPVIEW_MAP] SHOW_AIRPORTS=1 SHOW_AIRSPACE=1 SHOW_APPROACHES=1 SHOW_DATATAGS=1 SHOW_FLIGHTPLAN=1 SHOW_INTERSECTIONS=0 SHOW_JET=0 SHOW_NDBS=1 SHOW_TERRAIN=1 SHOW_VICTOR=0 SHOW_VORS=1 SHOW_WEATHERSTATIONS=1 SHOW_WEATHERSYSTEMS=1 show_flight_history=1 [BufferPools] RejectThreshold=131072 [VirtualCopilot] VirtualCopilotActive=0 [SOUND] AmbientUI=0 AmbientUIMusicVolume=-6.000000 PrimaryDevice={00000000-0000-0000-0000-000000000000} SOUND=1 SOUND_LOD=1 SOUND_QUALITY=2 UISound=1 VoiceDevice={00000000-0000-0000-0000-000000000000} [SlewTextInfo.1] AirSpeed=1,5 Altitude=1,3 Heading=1,4 Latitude=1,1 Longitude=1,2 [AContain] LabelColor=FFFF0000 LabelDelay=1000 ShowLabelAirline=0 ShowLabelAirlineAndFlightNumber=0 ShowLabelAirspeed=0 ShowLabelAltitude=1 ShowLabelContainerId=0 ShowLabelDistance=1 ShowLabelFlightPlan=0 ShowLabelHeading=0 ShowLabelManufacturer=1 ShowLabelModel=1 ShowLabelTailNumber=0 ShowLabels=0 ShowUserLabel=0 [ATC] AutoOpenAirTrafficWindow=0 COMM_MSG_AI_ATC_COLOR=FFFF7840 COMM_MSG_ATC_AI_COLOR=FF00FF00 COMM_MSG_ATC_USER_COLOR=FFB6FFB6 COMM_MSG_NONE_COLOR=FFFFFFFF COMM_MSG_USER_ATC_COLOR=FFFFD21B PilotVoice=0 ShowATCText=0 UsePilotVoice=1 [TextInfo.1] AirSpeed=1,5 Altitude=1,3 Heading=1,4 Latitude=1,1 Longitude=1,2 WindDirectionAndSpeed=1,6 [INTERNATIONAL] ASLAT=3 ASLON=1 MEASURE=1 [CONTROLS] Controls_Current=Standard Controls_Default=Standard KBDAIL=100 KBDELEV=100 KBDRUD=100 [FACILITIES] CITY= COUNTRY= GTL_BUTTON=1232 STATE= [TextInfo.3] AirSpeed=1,5 Altitude=1,3 FrameRate=2,1 FuelPercentage=2,4 GForce=2,3 Heading=1,4 Latitude=1,1 LockedFrameRate=2,2 Longitude=1,2 WindDirectionAndSpeed=1,6 [PointOfInterestSystem] CycleSetting=0 [GRAPHICS] AC_SELF_SHADOW=1 AIRCRAFT_REFLECTIONS=1 AIRCRAFT_SHADOWS=0 ALLOW_SHADER_30=1 COCKPIT_HIGH_LOD=1 D3D10=0 EFFECTS_QUALITY=2 GROUND_SHADOWS=0 HIGHMEMFIX=1 IMAGE_QUALITY=0 LANDING_LIGHTS=1 NUM_LIGHTS=8 See_Self=1 TEXTURE_MAX_LOAD=4096 TEXTURE_QUALITY=3 Text_Scroll=1 SHADER_CACHE_PRIMED_10=1693458432 SHADER_CACHE_PRIMED=1693458432 [TrafficManager] AIRPORT_SCENERY_DENSITY=0 AirlineDensity=0 FreewayDensity=0 GADensity=0 IFROnly=0 LeisureBoatsDensity=0 ShipsAndFerriesDensity=0 [DISPLAY.Device.AMD Radeon HD 6800 Series.0] Anisotropic=1 Mode=1920x1080x32 [DynamicHeadMovement] HeadMoveTimeConstant=1.000000 LonAccelOnHeadLon=-0.020000 LonAccelOnHeadPitch=-0.010000 MaxHeadAngle=5.000000 MaxHeadOffset=0.300000 RollAccelOnHeadLat=0.010000 RollAccelOnHeadRoll=0.100000 YawAccelOnHeadLat=-0.100000 [REALISM] AutoCoord=False AutoTrim=False CrashDetection=False CrashTolerance=1.000000 CrashWithDyn=False GEffect=True General=1.000000 GyroDrift=True GyroEffect=1.000000 ManualLights=True PFactor=1.000000 RealMixture=True StressDamage=False Torque=1.000000 TrueAirspeed=False UnlimitedFuel=False [Weather] AdjustForMagVarInDialog=1 CLOUD_COVERAGE_DENSITY=12 CLOUD_DRAW_DISTANCE=4 DETAILED_CLOUDS=1 DisableTurbulence=0 DownloadWindsAloft=0 DynamicWeather=0 MaxGustRampSpeed=200 MaxGustTime=500 MaxVarRampSpeed=75 MaxVarTime=50 MinGustRampSpeed=1 MinGustTime=10 MinVarRampSpeed=10 MinVarTime=5 THERMAL_VISUALS=0 TurbulenceScale=1.500000 WeatherGraphDataInDialog=0 WeatherServerAddress=fs2k.zone.com WeatherServerPort=80 WindshieldPrecipitationEffects=1 [Misc] Com_Rate=7 [Main] HideMenuFullscreen=1 HideMenuNormal=0 Location=820,6,1860,784,\\.\DISPLAY1 Maximized=2 SimObjectPaths.0=SimObjects\Airplanes SimObjectPaths.1=SimObjects\Rotorcraft SimObjectPaths.2=SimObjects\GroundVehicles SimObjectPaths.3=SimObjects\Boats SimObjectPaths.4=SimObjects\Animals SimObjectPaths.5=SimObjects\Misc SimObjectPaths.6=SimObjects\IVAO_MTL SimObjectPaths.7=SimObjects\ICE_AI User Objects=Airplane, Helicopter ProcSpeed=17903 PerfBucket=7 [Trusted] C:\Program Files (x86)\EZCA\EZCA.exe.wrbzrhlzccttoarihotqqhnarqzarbunclzczceo=1 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Aerosoft\Flight Recorder\AS-FlightRecorder.dll.ntclolhkhrelqtcbcbtcrzqoantqtitlnlazqiiq=1 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Aerosoft\Flight Recorder\AS-FlightRecorder.dll.owwwwquttqiwrobotkuuoqueiaqilhnnkcwnwnhw=1 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FS2Crew2010\Versions\AerosoftAirbusX\Gauges\FS2CrewAirbusVoice.GAU.zbehurlbcequtbewkrrzoqlnoitnzbhokrkbrcwu=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FS2Crew2010\Versions\PMDG737NGX\Gauges\FS2CrewNGXVoice.GAU.zoibtnhrbktchkkkwtuoibuqczeztwuouhiuakrr=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus A318_A319 Base/Panel_Fallback/ASC.DLL.tuqqoouwntwzelanoiuchicwkcrlerituzwhcqbo=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus A318_A319 Base/Panel_Fallback/AirbusXE.DLL.klbuiloeltialwcwkkizaquetkuwttqkleblnkre=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus A318_A319 Base/Panel_Fallback/AirbusXE.DLL.ltkzkohtkwtttzrwuqkurqkltarkihhhclquazth=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus A318_A319 Base/Panel_Fallback/AirbusXE.DLL.wetthnwthtkbawarcqaqtlabazliaoiceoqcburb=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus A318_A319 Base/Panel_Fallback/Airbus_ECAMD2D.DLL.elzeeuakcnrwokqlqalzoqlohcrqwulwqeilzlic=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus A318_A319 Base/Panel_Fallback/Airbus_ECAMD2D.DLL.iwrouztzrrilibhwlawetreanbzbunuubkannuzw=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus A318_A319 Base/Panel_Fallback/Airbus_ECAMD2D.DLL.okihebuuaqnheawwbbwabkknauiaqecbwakkeehc=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus A318_A319 Base/Panel_Fallback/DLLs/AsInput.DLL.qiraiwikniakteohwakbluilhqkrwwolbtuwunrl=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus A318_A319 Base/Panel_Fallback/DLLs/FBW.DLL.bqewqoubwtwqenzanilazrnieuuluzkwlhkhbqho=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus A318_A319 Base/Panel_Fallback/DLLs/FMGS.DLL.hzwhhckinqtwbzbcqklzkalzrcrnnbbqlkiarbbk=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus A318_A319 Base/Panel_Fallback/DLLs/FMGS.DLL.kinkwcaqtewichinatacrqohkeqtcitqbekuqwrb=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus A318_A319 Base/Panel_Fallback/DLLs/FMGS.DLL.rraqkekqoouzcbkbnkrzaqllrrbkbuiluebwzbhr=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus A318_A319 Base/Panel_Fallback/ND/AB_ND_GDI.DLL.cecrtnuhulabrkqzwkbbbikbaeuiliorwtkbknnk=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus A318_A319 Base/Panel_Fallback/ND/AB_ND_GDI.DLL.etzlbrwueoeiiknabhiearaobbeoineleetqwqei=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus X Extended Base/Panel_Fallback/AirbusXE.DLL.auiwunaqnqzqenlaainzutqhwcehenwrkaoblznb=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus X Extended Base/Panel_Fallback/DLLs/AsInput.DLL.uzncttqrnhzzhqnubkzkrzlqtbqewbtqkzzbetih=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus X Extended Base/Panel_Fallback/DLLs/FBW.DLL.crrznracbouheokrnuhwnwaczalbezqcuubwrtnk=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus X Extended Base/Panel_Fallback/DLLs/FMGS.DLL.ateztqbbherhonnlcrckwicwkezzaacchboqzzut=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus X Extended Base/Panel_Fallback/ND/AB_ND_GDI.DLL.turrkettohnrurkhkbhrkwtceqtarckitbcuhnni=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\Bell_206B.DLL.btbktziohnicirqihrbntontktwhhchzblqqaowz=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\Bendix_King_Radio.DLL.wwihqlhzatczqakeuluihlkzoqwhcueteehbtbtc=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\BoeingGeneric.DLL.lbzliheiqlccntelcqebatwulilnoiwbzqocrunq=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\Cessna.DLL.uillanolqhbkcrwizunrqtbhhhozruilllotnwrh=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\Cessna172.DLL.wohrueceatzeerrakqlruazrqcilzenlicobwbih=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\Cessna182s.DLL.qnoezcnacbetnbnzrbeewkznuohqkekcaueiuknn=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\CessnaWAlpha.DLL.nclkchrznwhkbkbatcnbokaabnkckkkoecuqnzwa=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\KingAir.DLL.wnwuaqruhkkibknoqotrzzoqctccrhcqhqozrckr=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\KingAir_Radio.DLL.horhnikaqbcneabikwwthurwqtranhwienchkalw=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\Magnetic_Compass.DLL.tazztwaaunkurotqetlalurraqqebtlbluochlzk=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PA32SARAG1.GAU.eiorbbrtlzhwtweuwwowzqticzacieaqkwqzaqqc=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PA32SARAG2.GAU.rnqrihratrqheouuuwaulcthuukakzrwoeozeeqb=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PA32SARAG3.GAU.nekchqqrbiltwiqknltbnibwbkrihrutnwnuanui=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PA32SARAG4.GAU.bewehzhwziaeznqtilahbqnawotkotukbrorrtrt=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PA32SARAG5.GAU.cnarbzowaorlbcaauobhkcirqtbhtwrtwtarccac=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PA32SARAG6.GAU.ebicoknkokouoeonhuttihwachkzwkcwowbzeelk=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PMDG_737NGX.DLL.tqttalklwebuuikutlenukcooornbbqhblqzqnbz=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PMDG_737NGX_3.DLL.zlobrewbwbrhanehwwlchnrqubiniobrqbokulla=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSRecorder_FSX.dll.oztzwhkiqbthlhkrqbqnwucuinwqhaoarqleklca=1 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.dll.ezwwtqnawllirookoauhzuihaucrhiqzaeetiiou=1 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\PMDG\DLLs\PMDG_HUD_interface.dll.rrnwcqrrionnozeaqlaoktnbkobteetozrockalc=1 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Aerosoft Airbus X A320 Extended CFM\panel\ASC.DLL.zntqbnlkliolctiaeqlroukoequrbecurikabknb=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\VistaMare\ViMaCoreX.dll.ueutiitbiuibcezlwzqizhniakrhqacncobrrtww=1 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\bglmanx.dll.izewlcnlkiuunqeuqbwcoiocwhnklrhnczbwaakn=1 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsdreamteam\couatl\couatl.exe.rhzqrnzquerrwhcthtetqwwrlihoctcizrcnqaub=1 C:\Program Files (x86)\Saitek\DirectOutput\SaiFlightSimX.exe.ircthlicbeuorkunltbciwaztzkektwcontnoeba=1 F:\Program Files (x86)\Addon Converter X\AddonConverterX.dll.aetubcqaqqobbnqllraqhtzaohhqkrbieunwbnnb=1 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\VAInterface.dll.nwoiibrthciahatoqrlkltlwnkanutuhauziqbnn=1 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus A320_A321 Base/Panel_Fallback/DLLs/FMGS.DLL.wtoeitqeelnberqhzqizbcqrzrtblzcirbkuceab=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus A320_A321 Base/Panel_Fallback/Airbus_ECAMD2D.DLL.kcrtawtziqhzorebccruetbaboarubzohzarzthe=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus A320_A321 Base/Panel_Fallback/ASC.DLL.tuqqoouwntwzelanoiuchicwkcrlerituzwhcqbo=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus A320_A321 Base/Panel_Fallback/ND/AB_ND_GDI.DLL.burkortkriarrbqlrrnlewwqthbelbewuurthcqk=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus A320_A321 Base/Panel_Fallback/DLLs/AsInput.DLL.qiraiwikniakteohwakbluilhqkrwwolbtuwunrl=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus A320_A321 Base/Panel_Fallback/DLLs/FBW.DLL.bqewqoubwtwqenzanilazrnieuuluzkwlhkhbqho=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus A320_A321 Base/Panel_Fallback/AirbusXE.DLL.kulalrlleqktubohrtttiwbhttroekktekqbnhbw=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\PMDG\DLLs\PMDG_Interface.dll.bwzwukuacuzznweclluwwlbhoekauoointlaubbi=1 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\RAASPRO\RAASPRO.dll.rrwttobbqwhklhczrkhzktulozoeoihbkhzellbq=1 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PMDG_777X.DLL.ithrbuwcccoznihieqiwwubwlkiobaalqazkknio=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PMDG_777X_3.DLL.kolrtkozeukaczhincterclhqezqlwtunuqneokw=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FS2Crew2010\Versions\PMDG777\Gauges\FS2Crew777.GAU.zihhzawqwwqrkntkbizccrhkctqltcceeuqicnee=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\737-400.DLL.ctlulkcaeunrroqahurqeqhtltiohucwlwkiillb=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PMDG_777X.DLL.onhqitroihiirtqkhuaralrzzlrihweocioktucb=2 [TextInfo.2] FrameRate=1,1 FuelPercentage=1,4 GForce=1,3 LockedFrameRate=1,2 [USERINTERFACE] DisplayFuelAsWeight=0 Map_Orientation=2 OpenATCOnCreate=0 PAUSE_ON_LOST_FOCUS=0 PROMPT_ON_EXIT=1 PageID=1 SHOW_MISSION_CAPTIONS=0 SITUATION=FLIGHTS\OTHER\FLTSIM SelectAircraftManufacturer=Todos SelectAircraftPublisher=Todos SelectAircraftType=Todos ShowAllACPaintSchemes=1 [SIM] SYSCLOCK=0 [Display] ActiveWindowTitleBackGroundColor=0,28,140,64 ActiveWindowTitleTextColor=255,255,255 BLOOM_EFFECTS=0 ChangeTime=4.000000 InfoBrakesEnable=True InfoLowerLeftBackGroundColor=255,0,0,128 InfoLowerLeftTextColor=255,255,255 InfoLowerRightBackGroundColor=255,0,0,128 InfoLowerRightTextColor=255,255,255 InfoOverspeedEnable=True InfoParkingBrakesEnable=True InfoPauseEnable=True InfoSlewEnable=True InfoStallEnable=True InfoUpperRightBackGroundColor=0,0,0,0 InfoUpperRightTextColor=255,0,0 NonActiveWindowTitleBackGroundColor=24,33,87,64 NonActiveWindowTitleTextColor=255,255,255 SKINNED_ANIMATIONS=1 TEXTURE_BANDWIDTH_MULT=40 TextureMaxLoad=30 TransitionTime=4.000000 UPPER_FRAMERATE_LIMIT=0 WideViewAspect=False [JOBSCHEDULER] AffintyMask=14 [SlewTextInfo.3] AirSpeed=1,5 Altitude=1,3 FrameRate=2,1 Heading=1,4 Latitude=1,1 LockedFrameRate=2,2 Longitude=1,2 [PANELS] DEFAULT_VIEW=0 IMAGE_QUALITY=1 PANEL_MASKING=1 PANEL_OPACITY=100 PANEL_STRETCHING=1 QUICKTIPS=0 UNITS_OF_MEASURE=1 [STARTUP] DEMO=0 LoadWindow=1 SHOW_OPENING_SCREEN=1 STARTUP_DEMO=0 [SlewTextInfo.2] FrameRate=1,1 LockedFrameRate=1,2 [TERRAIN] AUTOGEN_DENSITY=2 DETAIL_TEXTURE=1 LOD_RADIUS=4.500000 MESH_COMPLEXITY=81 MESH_RESOLUTION=24 SWAP_WAIT_TIMEOUT=2 TEXTURE_RESOLUTION=29 WATER_EFFECTS=4 [SCENERY] DAWN_DUSK_SMOOTHING=1 IMAGE_COMPLEXITY=4 LENSFLARE=0 MAX_ASYNC_BATCHING_JOBS=3 SmallPartRejectRadius=4.0 [FlightPlanMap] LineWidth=2 SHOW_AIRPORTS=1 SHOW_AIRSPACE=1 SHOW_APPROACHES=1 SHOW_DATATAGS=1 SHOW_FLIGHTPLAN=1 SHOW_INTERSECTIONS=1 SHOW_JET=0 SHOW_NDBS=1 SHOW_TERRAIN=1 SHOW_VICTOR=0 SHOW_VORS=1 SHOW_WEATHERSTATIONS=1 SHOW_WEATHERSYSTEMS=1 show_ac_twr=1 show_airways=1 show_markers=1 show_volume_boundaries=1 show_waypoints=1 [MULTIPLAYER] condAccoutPassword=0 I'm starting to think that the VGA is overwhelmed with requests and FSX is storing the queued textures in VRAM allocating more space, it's totally ridiculous how FSX handles memory. Any help will be much appreciated.

Hi Guys, I am facing a weird issue, and I can't figure it out on why my new system is eating up more VAS vs my old system. Old System - i5-750 OC to 4.1 ghz with 8gb ram, SSDs with AMD 2GB 6970 running on Eyefinity 5760x1200 Resolution P3Dv2.4 with Orbx PNW-CRM-NRM-Cali, Global, Vector, few Orbx Airports, REX4 textures, FSUIPC, Active Sky, OpusFSX (for cameras), FSDT Airports (Vancouver, New York), FlightBeam KIAD, GSX, Airplanes - A2A C172, Piper, Mustang, Cub, Majestic Q400, QualitySims 146 all installed. AI Traffic - MyTraffic P3D 5.4c (fully patched) Settings - LOD - 4.5, Autogen Complexity (full max), Building - Normal, Vegetation - Normal, AI Traffic 30 on Both I could do runs from KPDX to Bowerman to KSEA to FSDT Vancouver etc without having OOM, and my VAS stayed stable. Now the big issue is on my new system - I get OOMs on KPAE to KPDX on A2A C182 with autogen set to Normal. On Default Orbx PNW Airports, I am having trouble maintaining VAS. My new system specs - i7-5820K (OC to 4.4) with 16 GB Ram, SSD with AMD 7750 2GB (6 DP Video card). I know this card is not at all powerful as AMD 6970, but I need this card for work as it runs 6 4K monitors at 60 Hz. I do dual boot into windows 8.1 which has P3D2.4 only and 3 Monitors are only operational at 1920x1080 resolution. P3D is Single Screen on this The graphics are super sharp with i7 - but I only have 3 Sceneries Installed - PNW, Global and Vector, and 1 Payware A2A 182. I am using Activesky with Rex4 Textures (with Softclouds) all set to 1024 or lower textures. Even with default settings - I am getting VAS to be 2.5-3GB when it boots directly into a save file in P3D. Does weak GPU impact VAS to some degree? I can't figure this issue out - any thoughts or suggestions. Thanks, Skywolf PS - I use process explorer to see VAS.

I've had p3d for a few months, and have flown some GA aircraft in it, with no problems; But, as you all know, the PMDG 777 came out the other day, and I've flown it plenty of times in FSX. Though when I started flying the T7 in P3D, I started running in my first VAS Issues. Now, I've read a bunch of stuff on vas usage in fsx and p3d, as well as the P3D introduction of the PMDG Manual, and I was just wondering if the following is "normal" in p3d, or if I should be investigating something else further. Please note that this is with v2.4 as I'm holding off on 2.5 until some more addon companies are compatible with it (so, 2.5 may solve some of these issues). So, the issue is that I've started running the process monitor to monitor my VAS usage, and I was just wondering if the following is actually normal (please note that when i refer to 3gig or 3.1 gig, it refers to the general 3,000,000 or 3,100,000 bytes, and not the true value of 3 or 3.1) My basic computer specs are as follows: Windows 7 64bit Intel i7 960 12 gig 1600mhz RAM Nvidia GTX 970 w/ 4gig vram So, not the newest, but definitely not a slouch. I run the following addons Orbx: PNW, NRM, CRM, NorCal ASN Rex Texture Direct 4, Rex Soft Clouds FB KDEN PMDG 777 Now the issue. At first I did the silly thing and cranked everything up to the nuts just to see what it would do... I could hear scotty in the background going "She's Breaking up captain, she cannot take any more", and I had OOM errors when landing at an airport in the T7, so I started running some tests. I would start a new flight with the T7, parked at CYVR (with orbx scenery), and I was quite surprised that I was already at 3.1gigs of used VAS space, getting pretty close to the limit without even turning the plane on. Anyways, I've tried the following to try and reduce the VAS Usage: Disabled KDEN Reduced the REX texture sizes to 1024 Reduced the P3d Texture size setting to 2048 and then 1024 Lowered the mesh resolution (to 5m I believe, I'm not on my flightsim machine right now) Lowered the View Radius down one and two notches from the Max Reduced AI traffic to 20% from 60% (all default AI), and disabled all the other traffic except for commercial ships which I keep at 20% I have also tried setting up a flight, saving it, exiting, and restarting with that flight, and that has made no impact. I have also made all the changes specified in the Intro manual of the T7 for P3D The only thing that I noticed that had any noticeable impact on VAS was the autogen. And when all autogen was set to max, I was at 3.2gig+ and when set to sparse it was at 3.0gig . I made these changes one at a time, but still, after all the changes were made, the VAS usage is still hovering around 3.1gigs (may dip down into the 3.0s) which is odd. My frame rate improved which is to be expected, but VAS usage was unchanged. Is this normal? because there doesn't seem to be any difference in the texture sizes to the VAS usage (which from what I'm reading is the main culprit when it comes to VAS usage). I'm reluctant to turn off Orbx sceneries in p3d because I've heard that that will cause more issues than it will solve. Now I haven't tried this on any other aircraft (i also have the Majestic Dash-8, but I've never ran into VAS issues with it), but I'm just wondering if there is something else going on here where my VAS usage won't go down with pretty much any of the well known solutions. Any Thoughts, or is this just normal? Thanks

Hi all! I've never had any problems with OOMs in FSX since I switched to a 64bit OS. But recently there was a discussion in another forum about FSX RAM usage and how GPUs with large amounts of video memory might cause OOMs. The discussion was inspired by these two threads here on Avsim: http://forum.avsim.n...x/#entry2160874 http://forum.avsim.n...25#entry2100237 There were some questions whether GPUs with high amounts of VRAM installed could actually deprive FSX of virtual address space and cause an OOM. So I ran a few tests trying to prove it. I only have a GPU with 1GB VRAM, but since the GPU drivers can throw in some shared system memory if the installed VRAM is not enough (dxdiag reports around 4GB video memory on my system), I was hoping to show that if I tell FSX that there's plenty of video memory available using the VideoMemoryOverride switch in fsx.cfg I could actually cause OOMs. Well, the result in short is that I couldn't find that VideoMemoryOverride does anything at all. Neither increasing nor decreasing the values seemed to have any effect on VAS usage or VRAM usage as reported by Nvidia Inspector. I was only able to show that use of the DX10 preview mode can actually reduce VAS usage significantly. However I would be interested if that's just my system or if other people can't make this tweak work as well. So I will write up the test details here, hoping that someone will be able to reproduce my findings. Theoretical Background (I do not know much about DirectX, so this stuff is just what I read somewhere else. Please correct me if I'm wrong.) FSX is a 32bit application that --when run on a 64bit OS-- can address at most 4GB of virtual memory (->Virtual Address Space, VAS). DirectX9 applications must use their in-process VAS to address the GPU's video memory. Hence the more video memory FSX uses, the less address space is left for the actual application. There is an undocumented tweak found by ******* 'Bojote' Altuve called VideoMemoryOverride that is supposed to limit the maximum amount of video memory used by FSX. It should go in the section of fsx.cfg that contains the actual graphics card being used by the app: [DISPLAY.Device.NVIDIA GeForce GTX 460 SE.0] //VideoMemoryOverride=268435456 //0.25 GB //VideoMemoryOverride=536870912 //0.5 GB //VideoMemoryOverride=1073741824 //1.0 GB //VideoMemoryOverride=1610612736 //1.5 GB //VideoMemoryOverride=2147483648 //2.0 GB //VideoMemoryOverride=2684354560 //2.5 GB //VideoMemoryOverride=3221225472 //3.0 GB //VideoMemoryOverride=3758096384 //3.5 GB //VideoMemoryOverride=4294967296 //4.0 GB Mode=1680x1050x16 Anisotropic=1 AntiAlias=1 [DISPLAY.Device.NVIDIA GeForce GTX 460 SE.0.0] Mode=1680x1050x32 Anisotropic=1 AntiAlias=1 //VideoMemoryOverride=268435456 //0.25 GB //VideoMemoryOverride=536870912 //0.5 GB //VideoMemoryOverride=1073741824 //1.0 GB //VideoMemoryOverride=1610612736 //1.5 GB //VideoMemoryOverride=2147483648 //2.0 GB //VideoMemoryOverride=2684354560 //2.5 GB //VideoMemoryOverride=3221225472 //3.0 GB //VideoMemoryOverride=3758096384 //3.5 GB //VideoMemoryOverride=4294967296 //4.0 GB I don't know why I have two entries in my config (with suffix .0 and .0.0). I guess the second one is for a specific display (I only have one monitor connected to my GPU). Test Setup Since I do not have problems with OOMs the way I use FSX, I tried to conceive a scenario that would bring FSX down to its knees. I chose the PMDG 737 NGX and OrbX's PNW demo area for the tests, since these two are the most complex aircraft/scenery addons I have on my system. For these tests I programmed a Flight KSEA->KHQM->KSEA and recorded VAS usage on the return leg at 25nm distance to KSEA. I chose this scenario because the flight goes both over FSX default terrain as well as OrbX's addon scenery. Also, there is a lot of AI traffic at KSEA. I disabled all addons in dll.xml and exe.xml that could possibly interact with FSX during the tests and thus mess with the results (except the PMDG/OrbX libraries of course). FSUIPC unreg was also disabled. I actually wanted to record VAS usage even closer to KSEA (7nm) because it showed in some preliminary tests that VAS usage was highest there. However I got g3d.dll errors on the return leg pretty consistently shortly after passing the 25nm distance mark (at approx 24.5 nm), so I had to choose the 25nm mark as the point to record the test data. The programmed flight was low and slow to put max stress on the scenery engine (155kts, 1400ft altitude). I also opened a second window in fly-by view to keep the scenery engine busy. Additionally, I used the thunderstorms weather theme and enabled the NGX's head up display and ND terrain mode, hoping that it would further increase memory usage. The tests were all performed using a saved situation to ensure that the tests are repeatable. After loading the situation, I only pressed the NGX's TOGA clickspot, took off and enabled the autopilot at 400ft AGL (I left the gear extended). No messing around with view points or anything durring the flight. I recorded VAS usage using VMMap and GPU VRAM usage with NVidia Inspector. After each test, FSX was restarted. Once the test situation was loaded, I reset the stats in NVidia Inspector and selected the fsx.exe process to monitor in VMMAp. At the 25nm mark on the return leg, I pressed F5 in VMMap to display the current memory usage and took a screenshot to record the results. Additional test and system details: Windows 7 Pro 64bit FSX Acceleration NGX Sp1c Orbx PNW demo area (the current one with KHQM) Latest Orbx libs at that time (120328) FTX night mode on REX2 with HD textures installed (DXT5) Bojote's shader 3.0 mod JustFlight's TrafficX with recompiled traffic bgl All kinds of freeware replacement textures by Aime Leclerq installed (including TreeX) FSX ran in windowed mode for the tests, window maximized at 1680x1050 resolution (minus what the Windows task bar and window frame steal from that) Screensaver disabled NVidia driver v295.73, NVidia inspector v1.9.5.11 GPU settings as detailed here, using 8xS settings, frames locked to 30fps in the driver, no VSync My fsx.cfg and the saved situation files are included as attachments (please rename to .zip): Test Results I ran tests using VideoMemoryOverride (VMO) settings for 0.25,0.5, 1 and 3 GB of video memory. This is a screenshot of a typical test situation: During these tests, VAS usage was pretty high (300-500 MB free VAS left). Occasionally, VAS usage went further up (100-200MB free VAS) but dropped shortly thereafter. However, sometimes during these VAS usage peaks an OOM would occur. In those cases where I didn't get a g3d.dll error at 25nm before KSEA, I let the test run to see what happens when getting closer to KSEA with all its AI traffic. At approx 10nm distance, VAS usage went up (100-200MB free VAS left), but unlike above, it stayed at this level. I did not include these test results as there were too few of them. Furthermore, I ran a series of tests using FSX's DX10 preview mode. As expected, the VAS usage was significantly lower during these tests. But the VideoMemoryOverride switch didn't work there either, which I didn't expect since video memory is adressed differently anyway. The actual VRAM usage was a little higher in DX10, but it was the same for all values of VideoMemoryOverride. Also, here is a representative screenshot from one of the DX10 tests: Summary As you can see, there is little variation in the numbers apart from the differences between DX9 and DX10 which leads me to the conclusion that the VideoMemoryOverride config switch does not work. However, I do not want to write off this switch so early. There's still a possibility that the switch can work in other situations. So I would be interested if someone else (especially those people with a 3GB GPU) can try these tests on his or her system and post their findings.

For those of you observing the Vas leak on latest drivers I can confirm after some testing that the issue looks resolved with 378.72 hotfix. I think also there is a little improving on fps on my side!

Hello guys, I was told to post this here directly from the FSFX staff, my P3D works fine with chase and I really like this add-on, cannot be without it but I been having an issue, no matter how low my settings are, how many sceneries I have active while flying using the scenery tool, and no matter how good my machine is; I keep getting low VAS alerts at the end of my flights, at the beginning I was using the FSLabs 320 and I thought it was the issue but now even with any PMDG, carenado or A2A aircraft will do the same, I get very good frames on my P3D but as soon as im on approach to the destination I will start hearing the low VAS alert and if I open chase I will see the remaining of the VAS on 0.10, 0.20, etc etc, sometimes will even crash the sim. I use the dynamic core option just in case. I already updated and did a full clean install of the NVIDIA drivers and actually the VAS improved but I still get the alert but now will take maybe a little longer, I have no clue what can be so I emailed FSFX and they said it wont crash the sim but I can share it here just in case someone has a solution. Once my sim crashed so it can happen, please if anyone can share maybe an option for this I will gladly appreciated, thanks in advance. My computer settings are: i7 6700K 4.0 Processor NVIDIA GTX1070 16RAM, 2TB space and 124SSD Windows 10 64 bit

Hi. First of all I would like to say that luckilly I haven`t got any kind of problem related to VAS. However I would like solve a doubt I have related to VAS Monitor and the Windows Task Manager's RAM usage monitor. In my case they don't coincide. I don't really know if they should. While the VAS Monitor tells me that I have used 2300mb the task manager tells me that P3D has used 1010mb of RAM. This is a situation spawned at Runway holding pint in Aerosoft's Barcelona Airport with PMDG NGX and with AS16 and ASCA running in P3D v3.3.5. The differene is quite big: More tha a GB between Vas Montor and Task manager. Is it normal? Until now I have used the task manager to monitor P3D's memory usage, baut as I can see it is not by far accurate. I am a bit akcnowledge in this topic, so apologize me for my ignorace in advance. :wink:

Hi, How to fix Vas problem? i have the issue that when i fly and i can not open anything if i open it the game will not responding but it never happen before So i create the Post http://www.avsim.com/topic/496141-p3d-v3-not-responding/ and someone say that i have vas problem so how to fix it ? Here is my spec! Intel® Core I5 4570 3.20 GHz. RAM 8 GB ASUS STRICK GTX 950OC and asus mainboard Thank you Best regards, Vichayut Chunjaroen

Hello PMDG 777 Enthusiasts, Background Some of you know me from recently participating in the various VAS/OOM/leak threads involving the 777, as well as some of the lengthier ones dating back to late last year. I had the pleasure of helping Ryan M. and the PMDG Team test the most-recent 777 release after a few of us (myself, pcubine, and others) identified what appeared to be a memory leak in a weird combination of circumstances. Robert described this in pretty lengthy, accurate detail here: http://forum.avsim.net/topic/468259-07may15-detailed-discussion-of-resolved-777-vas-leak/ . He used the term "pesky" to describe it, I certainly didn't choose such polite language trying to track it down . (Robert, if you're reading this, and someone criticizes your team for "taking so long" on the 747v2, please feel free to blame me as the sole root cause ). How we identified the source of the VAS leak was a very trying process. Trying our collective patience, more than anything, I'd say. By the time I started realizing I was having a problem, to the identification of the source here...was somewhere on the scale of 3-4 months maybe, if I recall correctly. One of the keys, as I've harped on over and over again (as has the PMDG Support Team), is isolation of variables and repeatability. Just like a good old science fair project, keeping constants, changing one variable at a time, hypothesizing, and proving/disproving such a hypothesis in a conclusion. This is absolutely vital to generate the valuable data developers need to identify potential problems and act upon them. I come from an engineering/flight test background so I will likely sound like a broken record by the end of the thread, repeating those last few sentences. With a few other users posting about VAS usage still and OOMs after the latest 777 patch, I thought I might be able to help rope in the scope and breadth of all of these posts across multiple threads. Some contain some helpful information, others don't. So, I think it may be helpful for the PMDG Team, if we can do our best, as community, to perform the same type of controlled tests, and hopefully summarize this information and give something discernible to the developers to decide if further action is required. I'm not going to spend any time here describing how OOMs and VAS usage infinitely varies based on individual systems (PMDG manual introductions do a good job of that). In fact, I'm a firm believer that *most* of the time, VAS usage and increases over time are a result of settings and setup. OK, so you need some controlled data...how do you propose doing that? How can I participate? So, what I'd like to do is compile a set of scenarios for any interested users to take part in. That includes both users who still suspect abnormal 777 VAS usage after the most recent build, and those who don't. These scenarios (I'll call them "Test Cards") will take on a build-up approach, again attempting to isolate variables, starting with a VAS baseline and eventually expanding into specific flights. The best way I can think of distributing these Test Cards is via DropBox as I create them. I'll post links to updated Test Cards and users can download at their leisure. These Test Cards specify individual tests and settings for users to configure their sims to and execute. The first few tests will be baselines and ground tests, with middle-of-the-road, conservative settings. I understand that most would like to run with some higher settings, based on the more powerful systems today. It is important, though, to start in the middle of the envelope, baseline as much as we can, then start adding in the extras. However, this testing must be focused on the 777's DIRECT effect on VAS (and it's increase over time in certain scenarios, if present). Adding in 100 sceneries and ultra HD textures does not help the overall community cause. The front of each Test Card contains a Test Data Sheet. This form will be your way of submitting data back to me. After the completion of a specific test, please fill out the information I ask for accordingly and either send me a link in this thread, a screenshot, or a private message. I'll try my best to create a master archive of this data which we may be able to use to generate conclusions down the road. I'll be honest, this is going to be an experiment in itself to gauge what kind of feedback and useful data I can gather from the community. Maybe it'll fail horribly. Hopefully not. Hopefully, I can see how things start off and adjust these tests as necessary to create some kind of beneficial data-reduced product. Full Disclosures and Disclaimers 1) PMDG has not asked me to do this. I'm also not an FSX aircraft programmer, nor have any inner-working knowledge of the PMDG 777. Repaints here and there? Yes. Gauges, aircraft, scenery? Nope. Searching and reading the forums, and the vast amount of discussion on the subject, I see countless posts regarding 777 VAS. I can only imagine my head would be spinning if I were a PMDG Moderator (though I'm sure they all have more message board patience than I could ever have). If this data collection project is completely out of line, Moderators, please feel free to lock this post and smack me upside the head. 2) I do not own P3D or the 77W. I only own FSX SP2 and the 77L. And I do use DX10/Steve's Fixer, but not ReShare or SweetFX currently. Unfortunately, with recent discussions on the 77W, I can't test these out myself. For any settings I specify in Test Cards, if you own P3D, use your best judgment for similar settings. 3) It is absolutely imperative to start with a FULL, fresh install of the 777. No liveries, no previous cockpit states, nothing. Even AIRACs must be taken into consideration, so we will be starting off with the default PMDG AIRAC in the 777 (should be 1309). It would be even better if programs like REX, ActiveSky, FTX Global/Vector were uninstalled. (I mean, even more ideally, would be a fresh install of FSX - but I'm a realistic guy and know the participation rate would be near zero if I asked everyone to do that :wink: ). Many of the initial tests will ask for such add-ons and plug-ins to at least be disabled. 4) I do have a day job with a roller coaster of a schedule at times. Compiling data or creating new Test Cards for users to try may sometimes be slow. I love simming but there are just some days where I can't get on a computer to check forums or fly. 5) In general, this type of methodical testing can be a VERY tedious, time-consuming process. Since the ugly VAS monster reared its head previously on 5-8+ hour flights, our virtual Jet A bill is probably going to be through the roof. Time acceleration is worthless for these types of tests. You can easily fly EGLL-KLAX at 16x and "outrun" possible VAS leaks. 6) Feel free to call me crazy, make suggestions, comments, or provide feedback as we go. Also feel free to private message me. With that said... Here is the link to the first Test Cards/Test Data Sheets. These MUST be read in their ENTIRETY before testing. Test Card #B77L.1.1, #B77W.1.1, #B77L.1.1a VAS Baseline - http://bit.ly/1BaUc7e (B77L.1.1 must be performed before the 77W is installed, B77W.1.1 and B77L.1.1a must be performed after the 77W is installed) -------------------------------------- Thanks for reading and for your participation in advance, hopefully I can help a few users out with this project.

Many of you might be aware of this already but for those who aren't I've found a way of reclaiming up to 200Mb of VAS which may be the difference between getting an OOM and not. This is with the MS version of FSX. Flying FS Labs Concorde-X out of Fly Tampa Dubai the VAS available dropped down to 500-600Mb. As I flew away from the city I selected Options - Settings - Display and changed Filtering from Anisotropic to Off. Pressed OK and then went back into the menu and set it back to Anisotropic again. The net gain from this was around 200Mb. I'm enroute to HESH and available VAS is now up to 1072Mb. That's more than enough for my approach and landing. Hope it works for you. :smile:

Hello readers So sure, I could delete my FSX and start over to clean up my add-ons, scenery and more but I was wondering if there is another way to solve my problem of "too little VAS" causing regular OOM (Out of Memory) errors now. I have been reducing my settings (radius, texture-load, scenery all off) to increase VAS availability to FSX but without real success. I notice minimal improvements, and while yes, all those things reduce memory load, there is some culprit in my add-ons because I have only started having this problem recently and so far have not been able to find out what add-on this is. I start FSX and notice that FSUIPC is showing me 3GB left, shortly after 2GB and then I load a payware aircraft, let's say 737 NGX; some drop is normal here with the PMDG, then I have about 1,7 GB left and soon 1GB by just making myself dizzy in the spot view.... So if I were to start a flight, i would be starting with only 1GB left... this only start happening recently. With only 1GB left I would see the FSX ran out of memory error and have been. So I was wondering how I could find out how much memory each add-ons are using, is there a tool to display this? This would also be interesting to try and manage the limitations. I have also tried to regain some space by disabling some add-ons in the dll.xml but not much difference, I expect some add-on is not using memory correctly. Is there a table of reference? Some information already published that you are aware of? Thanks for any and all replies! Always much appreciated! Greetings, Joe

Hi all, I KNOW...we had this propably a thousand times already. But it really frustates me. I've been flying FSX/FS9 for almost 15 years now and I experienced a million different ways to make the Flight simulator crash (Blue Screen, OOM, CTD etc.). Last year at this time I even was so frustated I quit playing Flight Simulator and sweared to myself to wait until the new MSFS will be released. That's what I did. For that I even bought myself a new PC, because it just wouldn't be possible to play on my old one. Graphics -> WOW! Amazing! How do they do that? 😵 Performance -> WOW! Amazing! I cannot complain at all (40+ FPS on highest display settings) VFR flying -> WOW! Amazing! So nice 😃 IFR flying -> WHAT THE HELL? Even with purchasing the Premium Deluxe Ultimate Super Duper Version..WHAT THE HECK! I'm gonna wait till PMDG or QW realeases their aircraft for this flight sim! So I decided going back to good old FSX for finally flying some nice IFR legs again. What could possibly go wrong with my new PC specs? 🤪 Now the problem itself: Starting a flight on PMDG 777-200LR at EDDF (Mega Airport Frankfurt V2), activating AS Next Gen for FSX:SE and having GSX installed according to ProcessExplorer my VAS is already load up to 3.5-3.7GB (so like 92%) --> Are You kidding me? Is that normal? Even if I start a Trike flight on a non scenery airport without having AS Next activated the VAS is loaded by 2.4GB Can someone please explain? To be honest..I expected a lot more! My FSX even closed down with a OOM after reaching the gate now 2 times already. I'm definetly not a PC specialist and almost have no Idea about Hardware stuff. But this? Seriously? My PC specs: Processor: Intel i7-10700KF RAM: 64GB GPU: ZOTAC GAMING GeForce RTX 3090 Trinity Win10 Pro FSX:SE is installed on Drive D\ -> SSD 1TB FSUIPC 4.976 The LON thingy in FSX.cfg is still unchanged at 4.5000 Would I have the same problems with P3D (I just thought about changing SIM if it helps)

Hi Everyone, I've been immersing myself in the forums, here and elsewhere, to research the VAS/memory management problem that most of us who have 3.4 are struggling with. I'm convinced that it's a memory management problem. In any case, I'm curious to find out what the last version was that did NOT have these VAS problems. Maybe I can ask LM to let me roll it back since I started with 3.4 and can't get earlier versions. My VAS problems are pretty much identical to what everyone's been talking about recently. I'm still in the process of tweaking things, but maybe it will be worthwhile to see if an older version is a better option for decent performance/eye-candy until this issue gets addressed. I can hold my own for the most part with out going near OOM unless I'm in the 777 coming into JFK, and next worst airports are at LAXv2 and DFW. I don't have my sliders to the right, except for those run by the GPU, and am using low res textures. Traffic rarely above 10% unless I'm going into a smaller airport and I'll kick it up a little. Frames hover in the low 20s at most addon airports in the Airbus and 737, and of course, performance is spectacular in default ac. The CS 777 is a performance hog, knocking me down to 12-15fps in most cases at any airport, under any condition. Vectors are limited to primary and secondary roads and my cloud textures are also low. I guess what I'm getting at is I understand the VAS problem, and am learning how to manage settings in order to get the most performance vs graphics. But, after 2 weeks of constant tweaking, researching and testing, version 3.4 just doesn't give back VAS once it takes it away. The only way I can regenerate the memory is to save the flight, make it default, and restart P3D. Fortunately because of the SSD, the process only takes about 1-2 minutes. However, I'm wondering if a previous version would perform better, and if so, which one should I ask for? Thanks, John I7-6700k @4.4-4.6ghz (don't know which is more stable yet) 16gb 2100 DDR4 GTX1060 4gb (little better than the 960, but not by much- may return it) SSD for P3D and all addons ORBX Vector, HD Airports, Global, North America AS16 PMDG ngx Aerosoft Airbus Captain Sim 777 (unflyable), will upgrade to PMDG once I can get performance up Various popular FSDT, Flightbeam, Taxi2gate and Fly Tampa for USA and CYYZ, and Aerosoft (EGLL) airports MT6 (had UT2 migrated fine, but took a big performance hit and AI liveries too much to manage and update.

Hello pilots, I´ve made an update of a small tool of mine that I would like to share with you. VAS Monitor is a tool that allow you to see how much VAS memory you have on your flights on FSX and P3d. You can see the VAS amount, set a value to alarm you and pause the sim when a minimum VAS is reached (with visual and audible alarm) and a button to scramble your ambient music of FSPassengers, so not all your flights will have the same music sequence. It´s very simple and free. I hope it helps you in some way. Requeriments: FSUIPC (not registered); VAS Monitor Download P.S. Sorry about my english, it´s not my main language. Cheers Fred Matias

Hello captains, I don't know if here is the right place to put this but I think that this is an interesting tool. https://drive.google.com/file/d/0B6atkUYYWmkteHhkaG5aUkVpcnc/edit?usp=sharing This is a software that I wrote to myself but I think that it can be helpful to many people. This software monitors your FSX VAS. It's very intuitive. Just double click on setup to install. After the installation, double click the FSX VAS Monitor icon. If the FSX is already started, FSX VAS Monitor should automatically start to read the FSUIPC offset 024C. If the FSX was started after the FSX VAS Monitor, click the Connect Button and it will start monitoring. there are only 4 adjusts to set, the minimum quantity of memory avaliable before trigger the alarm (in MB), if the alarm will run with the red text blinking and a ding sound, and if the FSX VAS Monitor should start directly on system tray. System Requeriments: FSX (obviously) with FSUIPC installed. It works with WideFS too (Ideal to people that use two or more computers). This software is free to distribute. have a good flights... Fred Matias spilfred@gmail.com B)

This may seem like a stupid question but then again, I'm always told that there are no such things as stupid questions, only stupid answers. Anyway, this question is directed at those learned software engineers out there - is it possible to write a "plugin" that can encourage a "programme" to release VAS? We have so many fantastic "add ons" that run fluently alongside or inject into the sim and manage themselves into making the sim behave in a way that we dictate EZDok, GSX, ASN and of course FSUIPC amongst others, all of which were never part of the original ACES code. Why do we not have one for this issue yet? Is it impossible? I hope that in the very near future someone creates a solution of this nature since it appears that the more permanent solution of a 64bit version, X Plane aside, is in a galaxy far far away. Looking forward to the replies.

Hey, At this time, I have tried everything from complete OS reinstalls along with all low textures from Rex Texture Direct and low settings / default settings / high settings in prepar3d.cfg and I just OOMs in FTX full fat areas like PNW-NRM-CRM-NCA (along with Global & Mesh only installed - no vector). No Orbx airports, I can't even enjoy them with OOM hits in P3D2.5. Weather - ASN with 4 layers And I am only flying A2A C182 and Commanche. Sure, I can save the flight by FSUIPC and use that, but that is just getting annoying and besides GTN750 requires me to have the flight plan saved in it prior to crash. If I don't save it, I have to enter it manually again. What gives? This is just getting ridiculous. If you want to see my pc specs - it is in my profile. My question for you all is - How are you able to enjoy the FTX regions or are you all just using FTX Global? Thanks, -skywolf PS - Yes, I know this is a 32bit app with limitations