Jump to content

Search the Community

Showing results for tags 'vas'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General
    • Announcements
    • General Forum
  • Aircraft
    • Concorde-X
    • A3xx Master Series
    • Screenshots
  • Tools
    • FSL Hardware Interface
    • FSL Control Center
    • FSL Spotlights
  • Cockpit Building
    • Chat about cockpit building
  • easyJet Crew's easyForum
  • British Airways's The BA Club
  • Aegean Airlines's The Pub of Accord
  • Wizz Air's Topics
  • My little software corner's Developments


  • A319-X Liveries
    • PBR User Submitted Liveries
    • Older Non PBR Liveries
  • A320-X Liveries
    • Older non PBR Liveries
    • FSX & P3Dv3 Liveries
  • A321-X Liveries
    • User Submitted Liveries
  • A3XX Misc Files
    • Cabin Textures
    • EFB Backgrounds
    • A320-X - Unsupported Mods
    • Utilities
  • Concorde-X Files
  • FSL Aircraft Paint Kits
  • Spotlights
  • Hardware Interface for Prepar3D v4 & v5
  • Legacy Interfaces
  • Olympic Air Virtual's Files
  • Wizz Air's Files
  • Eurowings Crew's Configs / Textures / Sounds
  • Eurowings Crew's Operational Files
  • My little software corner's Downloads

Product Groups

There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...

Found 13 results

  1. Here we go again.. New driver 378.92 released. I was using the well tried and tested 376.33 with no VAS issues whatsoever. That until the Battlefield 1 update mandated driver upgrade for it to work. So I installed the 378.78 and the first flight was marked by a massive VAS OOM halfway between Poland and Estonia, memory leaking slowly and painfully. Now I'm going straight for the update.. Fingers crossed.
  2. Dave Hoffman

    VAS and Performance tips!

    Hello all, I'm a new customer to FlightSimLabs, and I'm not disappointed. I have use both the boxed versions of FSX, and FSX-SE, and am now running Prepar3D and trying not to look back. Over the years, and in conference with a friend of mine who is also an avid simmer, I have discovered some performance enhancing techniques for your sim. Some of these can be easily found on the internet, but here, I am going to focus on P3D, and without getting too specific as to my system settings. The reason being that P3D is more stable than FSX, and is delicate, but more fault-tolerant. I've got a LOT of stuff installed on it and I'm getting incredible performance, including with the A32X. Hyperthreading: If you use a processor, either Intel or AMD, and it's capable of running more than one thread per core, the best thing you can do is TURN IT OFF! You heard right. Hyperthreading or multithreading is great for running a bunch of desktop applications in a more harmonious manner, but we're talking about an engine that was developed for use with single-core processors. Do a test with the A320 at an addon airport with your sim "fully loaded" at a gate, then go into your BIOS and turn off hyperthreading, and try the EXACT same setup again, and you'll have to pick your jaw up off the floor with the memory you will save. Frame Limiter: I'm no hardware expert, but from what I understand of frame limiters, they work on the level of microscopic time and ultimately smooth out the performance that you are getting by doing the following. Frame limiters save the time of outputting frames they otherwise would have had they not been limited, and allocate those nanoseconds to doing other processes, ultimately smoothing your performance, and adding an element of scheduling to what your graphics card is doing. 30FPS is less than desirable in today's world, but a smooth 30FPS is very desirable in a flight simulator. There is NO good reason to use the frame limiter inside ANY of these sims. They do NOT work, so set them to "Unlimited." Use a graphics card utility such as the NVidia Control panel to set application specific frame limits. Use a frame rate that is right at, or half of your monitor's refresh rate. Mine's 60, so 60 or 30 would be applicable to me. Vertical sync should be on in the application to eliminate tearing (visible when viewing a whirling propeller). SLI/CrossfireX: I've got two video cards in my rig, and love the performance of having a second GPU doing some of the work. However, the application engine was developed before this technology came to be fruitful. Using SLI in P3D or FSX is basically a placebo effect. You will barely notice any effect in P3D, and it is also said that it can DECREASE performance in FSX. If you have an NVidia card, you can change the application specific setting "SLI Rendering Mode" to "Single GPU" Setting it this way also eliminates flickering of lights, smoke, and soft particles. It also helps in OBS if you're a streamer. Using SLI will cause OBS to render only half of your frames, so your broadcast will be choppy. If you're broadcasting at 30FPS, the app will run at 15 and look more like a slide show. Remember, SINGLE GPU! AffinityMast tweak: With regards to .CFG tweaks, less is more with P3D. With P3D and FSX-SE, use the double-slash "//" to comment out the affinitymask tweak. P3D and FSX-SE do a pretty good job of selecting the processors they want to run on, often you will get better performance NOT using the tweak. .CFG tweaks: Again, less is more. Try these: Under [GRAPHICS], set TEXTURE_MAX_LOAD=2048. This is a reasonable compromise between full HD and looking like dog food. We'd all like to be able to fly in 4K, but not with these sims. Don't let any installers change that value when offered. Under [DISPLAY], TEXTURE_BANDWIDTH_MULTI=40. Some guides have you set this higher, and to be honest, it has been my personal experience that the higher I set this, the more blurries I get. I always thought it increased a multiplier of some kind and therefore, texture throughput, but this is what helped me. YMMV. Under [MAIN], FIBER_FRAME_TIME_FRACTION=0.33, this is the default value. Some guides recommend setting this to 0.01 to increase frame rate. What this does is allocate a portion of the process's thread time to rendering texture. If you want to get rid of blurries, keep this at 0.33. DO NOT SET IT TO ZERO. But, play with it, YMMV. I've found blurries the lower I set it, and found no value to setting it higher. Placebo? Under [TERRAIN], TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=4500, try reducing to 3000. TERRAIN_MAX_AUTOGEN_BUILDINGS _PER_CELL=3000, try reducing to 2000. May save you some VAS, and you won't notice much difference. Sliders: The VAS killer is Level of Detail radius. P3D is good at exceeding what FSX can do with the slider. FSX Max right position was LOD=4.50, P3D is higher. The farther to the right you slide this, the more miserable your VAS usage will be. Keep it moderate. Mine is a 5.5, but comes down for graphics preset when flying the 'Bus. If you can't read taxiway markings: such as in ORBX sceneries that use photoreal technology, sliding this up to 15 or 7cm per pixel will help alleviate this, and won't cost much VAS. Autogen: Both of these sliders can save you a little bit if you knock them down. If you're flying a tube-liner then you won't be looking down at trees or buildings, you'll be busy managing the flight deck, only to get a quick glimpse out the window. You can turn them down to the midpoint to save some overhead. Scenery Complexity: A note about this; you can turn it down to save some overhead, but if you're missing buildings or jetways at some airports, turning this up might help restore them. Finally, just remember these last few things with regard to scenery. Like anyone that innovates, publishers try different things to be fhe first to bring something new to the market. Sometimes they fail. There are different sceneries from the same publisher that are sluggers when it comes to memory, performance, or both. Some have hotfixes or updates, and some don't acknowledge there's even a problem. Some refine their product, and some ask you to make concessions in other areas. Personally, I'm still trying to work out how people can fly into JFK at a VATSIM event. I have to offer a ritual sacrifice to the OOM gods to get into New York, in any airplane. Hope this helps, and happy landings.
  3. 777cap

    A Guide to MipMapping

    Hey Guys, I just wanted to make a simple tutorial on how to mipmap and optimize your aircraft textures,both internally and externally. This subject has been discussed in the past,but is more or less ignored by most people.There is an assumption that we pay for the best quality scenery,aircraft etc..with an underlying assumption that the product has been thoroughly optimized.Most people find out later..that this infact is not true.In interest of keeping this topic as short as possible,I will not go into further details about this. But why mention something if I am not going to discuss it? Well...most developers use titles like..ultra hd and high quality and other gibberish to market their products.A simple look at the textures in these products show they are unoptimized and mostly 2k or 4k textures. The microsoft ESP engine is inefficient at using such huge texture files,and it really wont make a difference in your sim unless you start zooming into the textures at highly unrealistic levels. So let me preface this discussion by first saying you do not need textures above 1024x1024 resolution.At max..2048 is okay..to a certain degree. You most certainly dont need clouds at 2k or 4k textures(ridiculous much?). I know this sounds like a scratched record but..if you are having horrible vas problems..high res. textures are most certainly the reason. If you can't deal with it..I am sorry this guide isn't for you. For those of you interested in experimenting...read on,I will post all my resources at the end of this document.I highly recommend going through them at least once.I sincerely hope this helps you. NOTE: SAVE ALL YOUR ORIGINAL FILES BEFORE EXPERIMENTING.THIS IS THE FIRST AND MOST IMPORTANT STEP. DISCLAIMER: I WILL BE PICKING UP A LOT OF TEXT DIRECTLY FROM OTHER ARTICLES.ALL THANKS GOES TO THE AUTHORS OF THE ARTICLES GIVEN BELOW: NickN,toby23(the original author behind the mipmaping guide...all thanks goes to him!) For the description behind what is being done..i suggest you read the articles given below...this document will only cover what steps need to be carried out to properly optimize textures. In case I feel this document needs revisions I will do so at a later date.There are many things that could be added to this document,but are beyond the scope of this particular discussion. I am going to be using photoshop with this nvidia plugin :https://developer.nvidia.com/nvidia-texture-tools-adobe-photoshop You can use dxtbmp or the aces image tool found in the SDK for fsx and P3D. From my experience..photoshop works the best...it is easy to use and the end result is how I want it to be. I have found the image tool to reject pmdg textures(image given below.) . Most commonly..texture files in p3d and fsx are in either dds or bmp format.DDS is preferable and is our first preference.You can convert BMP TO dds and vice versa..but I will only be dealing with DDS for now. Okay...When you open images in photoshop(with the plugin installed) this is the message you get make sure your options are ticked in the same manner.Do not convert textures to 32bit unless specified(I will try to cover this later) MIPMAPPING TEXTURES AND RESIZING: In the menu bar choose Image>Image size> make sure resample is checked.This way your resolution ratio will not change. This is where you reach a cross roads of sorts. You can reduce the resolution and save VAS or you can use the default 2k or 4k resolutions.If you want to lower the resolution..just reduce the resolution of the width..the height will automatically reduce(with constrained proportions). Some textures have slightly different texture resolutions for eg: 2045x4096..you can still reduce the res. to 1024 or 2048. Images that are 1024x1024 do not need to be optimized. note note note!!! FSlabs have done some really smart work on the decals...i am not completely sure if reducing the resolution will cause problems( it shouldn't) .Maybe a developer can clear the air on this one. You can either choose Bicubic(smooth gradients) or sharp(this adds a very slight outline to the text..not a big deal.I would recommend making two copies of the same texture and testing them out) Now go to FILE>SAVE AS you will be greeted with the following screen make sure you are saving the texture in DXT5 format(same format in the photo) after selecting generate MIP maps..you can either use the setting at ALL or anywhere between 11-13. That is basically it. to those who find the textures becoming too blurry..I suggest you save the textures with the sharpen soft setting.also make sure FXAA is set to off in your sim of choice. With mip mapped textures it is better to have the anisotropic setting to either 8x or 16x. You will see blurries if you have saved this optimized texture file at a resolution more than the sim resolution. That is: if you have selected a resolution of 1024x1024 in the sim and are saving your optimized textures at 2048x2048. THIS DOCUMENT WILL BE UPDATED.I WILL POST THE SETTINGS I USE IN MY SIM IN THE NEAR FUTURE. if you are brave and have enough patience to play around with amount of sharpening etc. I suggest you to do so. I have only posted the very basics of mipmapping..there is a lot more to be covered.I will also post more examples from my own sim. Good luck.I hope this small document helps! Regards FURTHER READING: http://www.simforums.com/forums/re-mipmapping-and-optimising-textures_topic54022.html http://www.avsim.com/topic/382519-a-huge-fps-increase/ http://www.avsim.com/topic/471107-guide-to-mipmapping-and-optimising-textures/ http://www.avsim.com/topic/311740-severe-micro-stutters-after-mipmapping-ai/ could mods please move this topic into the general discussion in the a320 forum.Very sorry.Thank you
  4. Did anyone measure the difference in VAS consumption between VC & VC+2D Cockpit installation with 2K and 4K textures each, yet? This info would save me two reinstallations, i just tried VC only up to now.
  5. craiggear

    VAS And My Compromises

    Hey Guys, I don't have a super duper machine, but I feel like I got MY setup in P3D working perfectly for me with no issues in all my payware. These include PMDG products, and the Majestic DH8D, AS2016 and Orbx and all that. Now, new in my hanger is the ever so beautiful FSLabs A320. I bought it when it was out for FSX and I actually clean-installed my copy of FSX for it. I didn't install any Orbx or even remotely try to set it up like I have my P3D set up. I basically only had the Airbus, and a few select airports I wanted to fly to. I loved it! So, back to my P3D. I absolutely LOVE my settings. The Majestic looks phenomenal especially when you're cruising just a few thousand feet above the mountains in NRM Orbx and stuff like that. NGX is also amazing. So when my beloved FSL Airbus came with a "YOU-MUST-DOWNGRADE-YOUR-SETTINGS" manual I was kind of put off. It was only about $50 Canadian to upgrade from the FSX licence so I decided to see what all this VAS talk was all about. I'm using Project Fly Tools to check my VAS during this test. When I loaded up the bus in FT CYYZ with the intention to fly to FSDT CYUL it is pretty crap weather, and I'm using my preferred "best" P3D settings. I haven't changed a thing. Before I can even start the engines I'm almost OOM. My fix was to ONLY TURN OFF all the vector features. Yeah, that sucks big time, because it looks so great. But it works for me, for the FSLabs Bus. Basically, I ignored the "downgrade booklet" and JUST turned off VECTOR and that was enough for me to ride from FT CYYZ all the way to FSDT CYUL in cloudy bad weather at around 80% VAS. I really hope you guys can figure out a way to optimise the product to a level comparable to other payware so I can turn my VECTOR back on. Love the plane so far, though.
  6. Hi, I realized that after the update to 1.92 I need approx. 10% more VAS, so after a flight from EDDL - EGBB I'm on 3500. With the old version I'm on 3100. Nothing else has changed. Any ideas?
  7. Richard Nellyer

    My Findings so far

    So went ahead and upgraded to the P3D version after being with the FSX version since day 1. VAS usage was as expected and as in FSX you do need to compromise slightly on your scenery settings. Took a flight from FlightBeam's KIAD (an absolute VAS muncher) to Imaginesim's KATL (Another monster scenery) in horrendous weather. VAS started at 3.4Gb peaked at 3.7Gb and apart from the odd brief spike to 3.9Gb, while taxiing to the gate on arrival,(and the dreaded OOM chime from FSUIPC) it remained stable and did not OOM. My P3D setup P3D V3.4 (settings as per the guide except scenery complexity "DENSE" to save losing detail at the airports) Orbx:- OpenLC USA Vector (All settings on) FlightBeam KIAD HD Imaginesim KATL REX Texture Direct 4 REX Soft Clouds AS2016 (ASCA not installed) System i7 4790K at stock 16Gb 1866mhz RAM GTX 980Ti (latest WHQL drivers) Win 7 64bit I have seen a lot of complaints about the VAS usage with the P3D version but I really can't see the difference between VAS usage in FSX and P3D. You cannot compare this aircraft to any of the PMDG fleet as this is vastly more complex from a coding point of view as the actual systems have been modeled and are not "approximations of". To all who are experiencing VAS problems:- Be realistic with your expectations, do you really need 4096 HD textures and full autogen when the majority of your flight is at 36000'? Keep your scenery library clean and only load what you need for that flight. Vast areas of photoscenery and complex addons eat VAS even when you're not flying in that region. Turn off AI traffic, boats and airport vehicles, they are useless in an airliner and munch VAS. Remember above all we're here to enjoy flying in a simulated environment. Put away the FPS counter and VAS monitor turn your settings back a bit fire up VATSIM and delve into the finest desktop simulation of an airliner ever created. The depth of the systems and the challenge of dealing with failures (yes enable them!) will keep you so busy you won't have time to pick holes in the scenery outside. Happy flying everyone! Rich
  8. Lars Hajema

    Thank you!

    Good afternoon :D, I see a lot of complaining on the forums, but barely anyone that says thank you to everyone here for making the A320-X such an amazing plane to fly. So let me say thank you FlightSimLabs, for making an amazing airplane. Secondly I see a lot of people complaining about VAS issues both in P3D and FSX. I personaly use FSX which as most of us know is worse on VAS then P3D is. Atm I'm flying the bus from Gibraltar to Alicante, for both I have scenery installed and running at 2048 textures. and this is the VAS that I'm on atm (see picture).. I will let the data speek for itself.. Anyways, I'm heading back to the flightdeck, sins I'm actually not allowed to use my phone atm, but shhhhh don't tell the company Enjoy your weekend. Cheers, Lars (LarsTheAviator)
  9. Nikolay Efimov

    [Resolved] Persisting OOM crashes

    First of all let me say that I absolutely love this product! I really want to enjoy it, but I keep getting OOM crashes almost every other flight, which is really ruining the experience for me. I've read the FAQ, and I configured my FSX(SE) setup accordingly. Actually I have a fresh FSX install with only the A320 and a few sceneries installed. I have the DX10 fixer and used the profile from the FAQ. I'm using ASN but didn't install any cloud sets. I have no performance issues per se, with FPS in a very usable 20-30 range. Since getting the A320, about 40% of my flights end with OOM CTDs, including flights between default sceneries. During my latest flight (FSDT JFK to FSDT LAX), I was monitoring my VAS usage very carefully, and here's what I noticed: 1. JFK : ~ 1.8GB used 2. Enroute: stable @ 1.4 GB 3. At TOD: still stable @ 1.4 GB 4. 5 minutes into the descent: rapid growth to 3.1 GB, and OOM CTD... A very similar spike to > 3 GB happened on approach to (default) LGA as well. What could have caused such a sudden spike in VAS usage? Sure, FSDT LAX scene is pretty heavy, but so is their JFK, and that never went over 1.8GB on departure...Besides, I was still about 100nm from LAX, don't think it would have even loaded yet. I think it must be something with the A320. If it helps, during the flight I encountered: - APU AUTO SHUTDOWN - FUEL AUTO FEED FAULT (or smth like that), prompting to revert to manual fuel control. - I had to change the arrival runway just prior to TOD. I kept the same STAR. Any help troubleshooting this further would be appreciated. For now, I feel put off from flying the A320 since it's probably gonna CTD anyway.
  10. Ralf Reuß

    FSX A320 crashes (VAS), etc.

    I'm really disappointed !! It can not be that I have to reduce everything to start a plane without crashing? Even with aircraft of PMDG there are no such problems. I as a user have a feeling I was working as a beta tester, whether new CFG file Ramsoftware or other settings, and I speak here of hours with my Flight Club in the group all has nothing helped real. So I delete all favorite airports again? The same applies to traffic. Without traffic, it is not fun !! On the Internet you will find closed threads and no one has a perfect solution. If you write to the support, the answer is a link to the forum. This is a support ?? So can this aircraft apparently only without Scenery, traffic and without installed addons operate ?? Not with me!! My holiday I have enough already sacrificed so !! I want to give the aircraft within the right to return back !!!! Ich bin wirklich enttäuscht !! Es kann doch nicht sein, dass ich alles reduzieren muss um ein Flugzeug ohne Absturz zu starten? Auch mit Flugzeugen von PMDG gibt es nicht solche Probleme. Ich als Benutzer habe das Gefühl, das ich als Beta-Tester funktioniere, ob neue CFG-Datei, Ramsoftware oder sonstige Einstellungen und ich spreche hier von Stunden mit meinem Flight Club in der Gruppe alles hat nichts wirkliche geholfen. Also lösche ich alle Lieblings Flughäfen wieder? Das gleiche gilt für den Verkehr. Ohne Verkehr macht es keinen Spaß !! Im Internet finden Sie geschlossene Threads und niemand hat eine perfekte Lösung. Wenn Sie an den Support schreiben, ist die Antwort ein Link zum Forum. Das ist eine Unterstützung ?? Also kann man dieses Flugzeug scheinbar nur ohne Scenery, Verkehr und ohne installierte Addons betreiben?? Nicht mit mir!! Mein Urlaub habe ich schon genug damit geopfert!! Ich möchte das Flugzeug innerhalb der Rückgaberecht zurück zu geben !!!!
  11. Hello Concorde-Fans, To those of you who want to see how the VAS behaves in FSX:SE and Prepar3D in combination with Concorde-X, I have a video for you. In it, I have measured the VAS consumption in identical flight situations under comparable settings in FSX:SE and P3D v3.2. To make things more interesting, I have actually run the test in three modes - FSX:SE DX9, DX10 and Prepar3D v3.2 (since it is known that DX10 can provide a sizeable VAS relief over DX9). In the tests, I flew Concorde-X from KIAD to KJFK, similarly to what I did in the tests that I conducted over a year ago (which is still archived somewhere in this forum). Back then, I ran the test on FSX only using the old Concorde version 1.2. This time I, used the new, optimized Concorde version (1.32), and the test comes in a video form where I added Prepar3D v3.2 to the "race". So, if you are interested in knowing how much VAS is consumed by different sims when flying Concorde-X, I'm sure you will find this video useful.
  12. During testing of v1.3 of ConcordeX I noticed that my available VAS suddenly dropped by a huge amount when I was preparing the aircraft for departure from London Heathrow. I initially suspected a 'bad' texture in my Ai Traffic program but eventually found that opening the Flight Planner dialogue in FSX to load a plan was responsible. Only a few hundred Mb is lost if the Edit option is avoided but if that option is selected the map eats an enormous amount of memory and it's never released. Before opening the planner I had 1230Mb available. After I closed it having accessed the map option it fell to 230Mb and the FSUIPC low memory warning started. Why would you want to load a plan this way when Concorde uses the INS system? Well, I use Active Sky Next and Air Traffic Manager (ATM) to remove far-away Ai aircraft. ASN automatically loads the FSX plan easing your workload. ATM relies on a plan loaded in FSX to ignore Ai for the airports used and gives a useful 3-4 fps boost. There's no other way for ATM to selectively remove unnecessary Ai which can be hundreds of miles away but still affect CPU performance. However, there is an alternative way to load a plan into FSX. FSUIPC4 now includes an option to load a flight plan into FSX without using the normal interface. Open FSUIPC from the Addons menu and on the Misc tab right side place a tick against Provide Menu Entry for Plan Loading. Then hit OK. Back under the Addons menu in FSX you now have a Load Plan option. I now use that option to load my plan. Active Sky Next automatically loads the plan and when Optimise is pressed in ATM it also reads the plan and removes distant Ai. Most importantly, there is no loss of VAS loading a plan this way. I'm running FSX SP2. Your version of FSX (once the v1.3 update is released) may handle this VAS situation differently but you should still be aware of a potential huge loss of VAS. Hope you find this helpful.
  13. Hello Concorde-Fans, With free time to spare, I thought to conduct an experiment and measure the VAS (virtual address space) at different scenery and traffic settings. VAS is known to be a notorious issue for most of you, as it is the most common source for OOM's, so this report might help established or potential ConcordeX flyers getting an idea of how much they can expect the add-on to consume. In the following, I have described the precise actions of my replicated test flights, so that you can follow it and possibly reconstruct the flights yourself. I have replicated three test flights according to this script, but with different scenery and traffic settings. The first test flight was conducted with "low" display settings according to the following screenshots: In addition, I let REX Texture Direct generate 512x512 resolution clouds and 1024x1024 resolution ground textures (runways & taxiways). My CPU is Intel i5-4690K running in turbo mode @3.9Ghz, GPU Nvidia GeForce GTX 750 Ti, and I have 4GB of RAM. The NVidia driver version is 347.52. As far as scenery add-ons, I use FTX Global and XClass LC. I also have ORBX' freeware NA airports installed (packages 1-20). Other than that, I use no other airport add-ons; only the stock airports. My test flights were from KIAD (Washington D.C.) to KJFK (John F. Kennedy). I picked up this route because it was not too time consuming, but at the same time heavy enough on the scenery and VAS, so that the average memory consumption would be above most flights over less dense sceneries. For weather generation, I used Active Sky Next SP2B (Build 5575). I specifically chose April 7, 2015 18:27UTC as the FSX time and let ASN synchronize weather with this time (by forcing historical time to sim time), because at the mentioned time, weather conditions were cloudy over the northeast US. The clouds would add more VAS compared to a clear weather scenario. Know that the FSX' own Cloud Draw Distance settings are overridden by ASN (where I set the minimum value to 90mi and the maximum to 110mi). In the FSX flight creation menu, I select "Gate 1 C Heavy" at the KIAD airport, set the aforementioned time, select ConcordeX and click on "Fly Now". Upon loading the ConcordeX in 2D panel mode, I let the add-on set up the systems (INS, etc.) and then go to the Fuel editor, set the fuel preset to "Training" (over 22T) and load the airplane with a "low" number of passengers. Then, after FSL has taken over these settings, I capture the VAS consumption using the Process Explorer. Next, I look around the airplane in the external view, go back to the 2D panel and then open all engineer's panels (only them, not other panels). (Some have reported that the panels consume a lot of VAS). I record the VAS at this point: As you see, the VAS has increased by roughly 250MB. Now I switch to the virtual cockpit (1024 resolution version), request taxi to the runway. The ATC assigns runway 19L via taxiway D K J1, which is very convenient, as it is the closest runway from the gate. While taxiing, I set the altitude at 5000ft on the autopilot (set by default) and 90 degree heading. Our route to JFK will go over OTT VOR (113.70), and then directly to JFK from there. As such, I set the radios to OTT VOR. Upon reaching the runway, I request a takeoff clearance from the ATC, which is given immediately, as there is no other traffic at all. I activate the landing lights and line up with the runway. Here is the VAS: (End of Part 1)
  • Create New...