Cheyenne Chief Pilot

Fly into a massive wind shear in normal law and your Airbus *WILL* stall. The tricky thing is, the moment you enter that huge wind shear, your airspeed information becomes invalid, the Airbus therefore switches into alternate law, so your crash won't be in normal law anymore.

Plain customers or also customers who coincidentally happen to be beta testers for Aerosoft, for example? I faintly remember dialogues via a certain skype group ...

... you may want to check those dll's too: Bryan York (himself!) tested the VAS impact of his FS2Crew NGX edition (no external exe; it's dll-based): It's some 170 MB in VAS. http://forum.avsim.net/topic/420220-so-how-much-virtual-memory-does-fs2crew-use-anyway/

Someone mentioned the lighting in FTX-G as a possible, VAS-increasing factor? I'm puzzled 'cause I was trying to back up Otto's flight - but I have more VAS left with LGTS default than Otto has with LGTS lite II. Simply put, Thessaloniki X is (just ) for me ...

AXE at LGTS in its factory state (no lite), all options enabled in the LGTS manager, real wx according to ASN gives me a max. of 3.2 GB VAS. I have not disabled any scenery layers (so even 0.4 GB more to spare), I do not use "global" addons - no FTX-G, no such night lighting etc. Instead I run Heli Traffic which injects extra helicopter traffic, on top of MT2010 (both sliders at 20%).

Have you checked your VAS at the other airports (where you had departed from) and have you checked what happened to your VAS once you settled in cruise? I did two separate flights (FSX shut down and restarted in between), one from EGLL (ORBX and UK2000), the other one from LGTS: During both departures my VAS was "tight" (some 4.0 GB - I wanted it that way for testing purposes). Settling in cruise after departing EGLL my VAS usage reduced to 3.5 GB, after departure from LGTS it was "only" 3.2 GB. So my EGLL departure gave me an additional "VAS burden" of 0.3 GB which I probably would have carried with me into LGTS on arrival. (In other words: Thessaloniki X seems to "unload" VAS in a more efficient way than some other sceneries.) The LGTS efficiency has been mentioned before in this thread, but maybe less efficient departure sceneries contribute to your VAS findings here, when arriving LGTS? Have you checked your "VAS burden" you were carrying with you from your TOD, for example?)

Thanks for retesting, Otto. Even though Bojote's tweaks are a bit outdated (geared at older graphics cards) they yield far better results as far as VAS usage is concerned? That's really odd ...

What SCE does, it "almost" sets your scenery.cfg back to a vanilla FSX installation state: Hardly any more entries active than those from the "FSX base pack". And that's what Mathijs and Emilios have been referring to a couple of times: LGTS works just fine in its factory state with just "plain" FSX, realistic weather and a nice (or even a "heavy") addon aircraft active. And that's exactly what's so outstanding about this freeware SCE: Despite my nearly 600 scenery layers, I can still run the full-blown LGTS as if my FSX were in its "virgin" state - what it obviously isn't.

Sorry, Otto, I cannot confirm your findings. Your setup (vs. mine): setting "Lite" (setting "default"!!!) default C172 (dto.) from rwy 16 with 2020 MB VAS left, flew a right hand circle at 1000ft and landed again on rwy 16 (dto.) with 950 MB VAS left. (1.600 MB VAS left) After every 90° turn VAS droped by approx. 200 MB. (400 MB for the complete traffic pattern) nearly vanilla fsx.cfg (see the no. of my scenery layers above. I still have 400 MB of additional free VAS to gain by disabling unnecessary scenery.) FSX settings (see my cfg file linked above) That's your 1.000 - 1.100 MB loss in VAS vs. my 400 MB VAS loss. You lose 1 GB in "lite" configuration, while I lose only 0.4 GB in "heavy"?

How will the configurator be offered to customers of flightsimstore? Can they download from their FSS account? At least there doesn't seem to be an entry for LGTS X yet in the Aerosoft FAQ/Updates database.

Not yet in there - but that should be a matter of ... hours only? Anyhoo, my safety margin (0.4 GB) stems from disabling other scenery areas - no "castratorv3.0" needed!

Thank you, Sir, my bad! What I noticed after disabling "unnecessary" scenery were shorter loading times when firing up FSX, and even higher fps?!`Does that make sense, higher framerates when scenery that isn't even rendered in the first place, is deactivated??? Probably just a coincidence ...

That's true: This tip of disabling scenery came up a couple of months before the release of PMDG's T7: Some guy on the AVSIM forums, who had installed masses of photoscenery, was facing OOMs over and over again. PMDG's Ryan helped him out just to discover that disabling all that PS brought back about 1 GB (yes: 1.000 MB!) of VAS to this guy. Those findings were discussed on AVSIM and have made it into the T7 introductory manual. I installed quite some PS in recent weeks (freeware Canary Islands, freeware NL-2000, a payware PS for the Balearic Islands; I also had had some MSE, VFR Germany, BSS and other PS before) so I gained those 400 MB. You'll probably need a huge installation of PS to reach between 0.4 and 1.0 GB. (I have 538 layers in my scenery library!) But flying into and out of London airspace, it will help for sure to disable all those Gary Summons airports you don't need (otherwise they will be loaded during those London SIDs and STARs and fill up your VAS as active scenery). The same is true for the N.Y. airspace and maybe some more (Hong Kong? Flying into YMEN, you may want to disable that huge ORBX YMML, perhaps?) Anyhoo, "just" 200 MB of additional free VAS can make all the difference when descending into one of those addon airports.