Search the Community

Concorde Performance System X: http://concordeperformancesystem.org/ Concorde Performance System X (referred to as CPS-X hereafter) is a standalone utility which can be used with SSTSIM for Microsoft Flight Simulator 2004 (aka FS9) and FSLabs Concorde X for FSX, FSX-SE, P3D v2.x and v3.x. It allows the most demanding simmers to plan any Concorde flight either subsonic or supersonic. Any airport included in the simulator can be chosen as departure, destination or alternate, provided that it has a long enough runway to takeoff or land Concorde. CPS-X is only a fuel and performance planner, not a route planner. This means that you first need to use software like PFPX, FS Commander, or any route planning tool to generate the routes that CPS-X will use. Those routes must be exclusively created in FS2004 (text file) or FSX/P3D (xml file) *.pln files format. If not, CPS-X will not be able to use them. The tool provided by FSLabs only allows the calculation of the performance for some of the most popular airports used by Concorde during her illustrious career and only with a few loading profiles. CPS-X offers virtually unlimited routes only restricted by your own imagination. CPS-X allows you to calculate the right balance for any load, the right amount of fuel required and its distribution and the correct takeoff and landing performance. The performance provided by CPS-X is based on the real aircraft documentation from Air France. CPS-X uses several weather sources to compute the performance and fuel required. Real weather can be downloaded from NOAA servers or programs such as Hi-Fi Simulation Technologies Active Sky 2016 (only for FSX and P3D) or set manually by the user. CPS-X benefits from 5 years of experience developing previous versions while listening to and supporting its users. It is the sum of these 5 years that has helped me to improve it. This is a short summary of this product that should satisfy the most demanding fans of “Hard Core” Concorde simulation. Pierre Chassang

I thought I'd share this in case anyone finds it useful. It will give you results for any combination of runway length/slope/elevation so you can fly out of any runway as long as you have access to the relevant airfield charts and the METAR. Just a health warning: I have got is at accurate as I can from the performance data available so it is fine for simulator use, but some Concorde data doesn't fit equations very well, hence some numbers might not be exact. It is not very "automatic" by modern standards because the actual program is built for the HP200LX pocket computer that the crews in BA used and I have re-visited my programming after learning how to add a GUI to it, making it more "PC friendly". You will probably have to exempt the file from any Anti-virus stuff after extracting the zip file, but I haven't added anything to the exe other than very basic programming, however use at own risk as usual. Download link: https://drive.google.com/file/d/1J13AvFHbm3Kw35LYpe7RsavP4KFbbPNJ/view?usp=sharing Frazz

Hello dear flight simmers, First of all I am new to this forum and I guess this is the right section to post it. Yesterday, I purchased a new PC and I´d like to know how well I could run the A321 for P3Dv5 (It doesn´t work for FSX:SE, does it?). --------------------------------------------------------------------------------------------- Specs: AMD Ryzen 5 3600 (17,828 Passmark CPU points) RX 5700XT 8GB VRAM (16,729 Passmark CPU points) 32GB RAM 3200MHz 1TB M.2 SSD (R:2000MB/s W:1700MB/s) --------------------------------------------------------------------------------------------- According to Passmark my PC will exceed the recommended specs by over twice the amound of points. So I´m sure that I can run it... but how well? I don´t plan to add any addons besides GSX and some other aircraft addons and my perfect goal would be to achieve 40FPS no matter where I fly (I have no idea if that is even possible with such a complex aircraft) It may be that this question has been ask a hundred times by now and I also tried to look on youtube to get a feeling which FPS I can expect from which specs, but every youtuber either has a much better system than mine or lots of graphic/scenery addons that influence the performance. I want to be 101% dead sure before investing 200$ into the A321, so if anyone has the same or a similar system as me, I´d apreaciate if you could share your experience with me. Kind regards and thanks in advance!

Hi guys As i only get 25-30 FPS when flying over water in 1440p, i was wondering if its possible to set 1080p in the setting but telling the GPU to render at 4K and then resizing to 1080p, I think it's called downsampling something like that ?. In 1440p, my 1080ti is barely used less than 40-45% so still have some GPU power available but it this possible in p3Dv4 ? In 1440p, the gauges a,d texture look sharps in the fslab and I fear that it would be not the case if i go in 1080p, also how much FPS can I expect from 1440p to 1080p ? Thanks

Much has been said about this over the months and years, but I’m going to add my few quid because I’ve had a huge degree of success with it. Therefore, perhaps some of you can benefit from my experience. Firstly, simmers tend to be obsessed with frame rates, in the mistaken belief that higher frame rates are the key to a great flying experience. This is completely wrong. Frame rates are important in first person shooter games, where on the onscreen action is fast and furious and milliseconds are the difference between winning and losing. What us simmers need (I’m a gamer as well by the way) is fluid and stable frame rates, without stutters at just high enough frame rates to deceive the eye into thinking it’s looking at motion. The illusion of continuous motion is only convincing (and therefore immersive) if it is smooth. Essentially we need 29-32 fps. Anything higher and you’re probably wasting capacity at the expense of something else. Many people report having rates of 50-100 fps which, if completely stable is great. However, stuttering and fps instability even at these rates will still kill the illusion dead. It is worth mentioning that stutters may not show up as momentary drops in fps on the beloved red texted frame rate counter. Don’t confuse stuttering with low frame rates. They are completely different issues and may be caused by completely differing reasons. People often associate stuttering with having low frame rates, and therefore believe that their attention should be focussed on increasing frame rates to cure the stutters. They are barking up the wrong tree. There are 2 main causes of stuttering: 1. System bottlenecks – The throughput of data demanded by the sim overstretches the capacity of the system to provide it continuously. By system, I mean your entire setup, including your monitor. 2. Syncing – Your monitor, graphics card and remaining system must all be perfectly synchronised. Like the gearbox in your car, if the components aren’t meshing in synchronicity, there will be grinding and lurching all around. This is a good metaphor because it demonstrates that smoothness is not dependant on speed or frequency. Smooth gear meshing will provide smooth transmission at any speeds from standstill to racing speeds. It's pretty easy to isolate what is causing what. Simply put, system bottlenecks tend to produce random stutters which vary a lot in amplitude and follow no particular timing pattern. On the other hand, syncing stutters tend to have a more stable, rhythmic pattern to them, like one solid stutter every second, or half second. A good way to see this is to jump to the default spot view by pressing “S”, then panning continuously around your aircraft, looking down at about 20-30 degrees. After a few revolutions, you should be able to see if your stutters are stable or more random. With this in mind, don’t be fooled into thinking that if you have massive throughput capacity, there won’t be any immersion killing stutters. If your monitor isn’t properly synchronised with the action, you’ll get massive, brain twisting stutters (which may lead you to believe you have a frame rate problem). Your output device (monitor) is like the tyres on our metaphorical car. If the engine and transmission are running beautifully smoothly but you have one or more misshapen tyres, the car will drive like crap, regardless of power output and speed. Once you’ve isolated the cause, you can fix the problem. You don’t need to mess around with Nvidia Inspector, Process Lasso, or any other stuff. You just need to understand the problem. I have used Process Lasso recently and believed that it was helping. However, when I found the real cause of my stuttering, I realised it was a placebo effect, so I got rid of it. Firstly, you need to aim for a specific lower frame rate threshold that your system can maintain in all or nearly all scenarios. Ideally 30 fps. Any modern reasonably high powered machine can achieve this if you’re not too greedy with your settings and appreciate which things can be turned off without killing the immersion. I’m not going to go into exactly what my setting are because they are specific to my machine. The simple way to find out for yourself is to start with everything set to medium (including anti-aliasing etc) then pick a scenario which represents a reasonably challenging scenario for your system. Save the scenario, then gradually increase settings, incrementally, one at a time until your lowest frame rate hits 30. This is only half the story though. You MUST then ensure that your monitor is synced properly with the system output. I use a 40” TV as my monitor. It runs at a native 1920x1080p resolution at a refresh rate of 60Hz. By the way, TV’s don’t make great monitors for a number of reasons, but it’s what I’ve got. If my system could run everything with a lowest frame rate of 60fps, I’d want to make sure that my Vsync was outputting exactly 60 fps @ 60 Hz. However, my system can’t do that so… I have to improvise. The monitor refresh rate specified in the driver setting of your graphics card will tell P3D’s Vsync module what frequency to output at. This is absolutely essential for smooth graphics. IF I tell my graphics card to refresh my monitor(TV) at the rate of 30Hz (or put another way, 30 times a second) then I enable Vsync in the P3D settings, the graphics driver will tell P3D’s Vsync to output at exactly 30 frames per second too. This results in perfect timing and therefore synchronisation between the system and the visual output. This further results in completely smooth, stutter-free fluid graphics. If you can make this work, it’ll feel like you think it feels at 40fps, 80fps and so on. In summary – Great flight simming is about creating the illusion of fluid movement. This gives you the feeling of momentum, movement, mass etc. Convincing Immersion is only possible with smoothness. Forget high frame rates – they are irrelevant in flight sims above 30fps. You need to achieve 30fps as the lowest performance benchmark, then force the sim to stay there using Vsync. Ensure that your monitor or TV is playing ball by forcing its refresh rate down to 30Hz. You won’t notice the difference in the sim, though you probably will at the desktop. Just enable it before you load your sim, then put it back to 60Hz when you’ve finished flying. Then, just make sure that nothing in your other settings is causing momentary bottlenecks which cause the stable frame rate capacity to drop below 30fps. As said previously, you can do this by lowering your AA settings if required. AA and DL seem to have the biggest impact in the P3D V4, so it’s fairly easy to isolate them. There is no need for complicated tweaks in Nvidia Inspector, third party apps, various driver versions, as it can all be done with your basic driver control panel and within P3D’s graphics settings. If you’re more inclined, you can use HWMonitor to see how your hardware is bearing up but even then, you only need to know your CPU utilisation and your GPU utilisation. Nothing else will really help you. That said, my overall CPU package is often running at or near 100% but I have NO STUTTERS. CPU maxing doesn’t always mean stuttering. It may just mean that it’s working hard, as you’d expect! GPU maxing is more likely to cause stutters and ideally you’ll have yours running at around 80-90%. Again, aliasing effects are often the biggest influence here, so adjust them accordingly. Using this basic and logical approach, and understanding the problem, I have managed to achieve the following with my hardware and software setup: Hardware: Intel 7700K running at 4.0 GHz – I do not believe in overclocking. It just stresses your hardware enormously for very little real gain. Particularly as I’m not chasing ever higher frame rates. Nvidia 1080GTX, Asus Maximus Hero VIII, 16 Gb ram running at PC2100, SSD for OS and P3D, Samsung 40” LED Monitor @30Hz for sims and 60Hz for desktop. Currently using driver version 388.0 but it doesn’t really matter which you use. I have only changed 2 things in the driver control panel – prefer maximum performance to prevent GPU throttling by reducing power, and monitor refresh rate @ 30Hz. With this, I have Vsync turned on, frames unlimited, triple buffering on or off as it doesn’t make any difference for me, SSAAx8 during daytime and MSAAx8 at night time, with DL turned on. DL does not play well with SSAA, so I use MSAA at night. In the dark, the difference visually is very small. Using Orbx Global, LOWI, UK, Scotland, Wales, UK2000 major airports in the UK and a combination of Orbx, Aerosoft, Flytampa, Flightbeam, and FSDT for the others. I also use GSX. On a networked laptop I have ASP4, ASCA and Avliasoft EFB. I occasionally use PTA with various pre-sets but often find that where they improve in some areas, they ruin in others, I often revert to default shaders which are fine. I run tex resolution at high not extreme because it’s pointless at a screen resolution of 1920x1080 and makes no visual difference. With the FSL A320 in P3d V4, I can achieve completely smooth fluid graphics, at night, at LOWI, with DL on at 30fps. The same during the daytime with SSAAx8 and it looks stunning and feels stunning. All other P3D’s settings range from extreme to normal. Stop chasing frame rates and concentrate on smoothness by improving your system’s synchronisation.

Hi Guys, I'm sure you probably get this type of question a lot, but I need advice on whether to purchase with my specs Specs are as follows: Intel i3 6100 (5494 rated) GTX 1050ti (5804 rated) 16gb DDR4 ram Windows 10 64bit FSX Steam Edition I would really love to fly the fslabs a320 but with no trail system I don't want to risk £80 if the performance is too low so I would really appreciate some opinions. Most of the system seems alright according to the product page, except the CPU, which is slightly below minimum, of course I understand that there will be major scenery and settings reduction needed, but I consider it worth the trouble for such a product. Are the requirements slightly less for FSX? and should I consider overclocking the i3? (although I have heard this can cause issues with FSX in the long run) Thanks in advance Kester Rice

Hello, I am very interested to purchase this product! I am just wondering on how my PC would run with 8GB worth of ram... I saw on the website it said: '<Minimum 16gb of RAM' Is 8gb enough? What does RAM do exactly in P3D V4? Does this affect performance ? I would love to get this aircraft! I'm too scared to purchase in case of the bad FPS. By watching videos online with the difference performance with the 8gb and 16gb I don' notice a big change in FPS or stutters for example... All I can see is maybe a 4-8fps decrease. My setup is: Intel Core I5-4590 GTX760 4K monitor 8GB of Ram Installed Thanks, Jack Sparrowhawk.

Hi, First of all I would like to thanks FsLabs for 1.Making such a great product. 2.Making such a great forum, where you can talk not only with other users but with the staff. I was one of those who claimed for a brake and rudder solution for those who play with no hardware. And now the experience it's brilliant. It's awesome to fly this beast with such inmersion: vc, systems, procedures, behaviour, PA knob (really?), sound... I have now upgraded to P3D, and the result is even better. Superb. But one of the things that worry me a little (and only a little) is the performance. Even when the performance of this product is also really good taking into account all the information that has to be processed, I (and all of us I guess) we are always looking for ways to maximize fps. And there's my question: will there be an option to disable the weather radar scanning for those who want to sacrifice this system to gain some extra Fps? Or maybe I'm wrong and disabling this system wouldn't be as good as I think? Many thanks, and safe flights!

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.

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

Hi everyone! Since I downloaded the (fantastic) FSLabs A320 I've been feeling like my system hasn't been performing as well as it should be.I followed the settings suggestions in the forum but, when I compared my settings and performance with videos from other users online it seemed that the only way I could dream of getting the same frames and smoothness was to drop my settings to really low quality. Of course - I didn't want to do that! So I've been searching for a guide that makes it easier for someone with very little understanding of how graphics and performance actually work to follow. Well - after some google searching and some experimentation - my FSX is running much better! I found a guide called the DX10 Fixer "How To" guide - and I wanted to share a link to it here so others can try it as it seems to work for me. Since following the guide my frames are no longer dancing around and have stabilised at around 20FPS. I've also noticed the sim is running much more smoothly. The guide version in the link was written in 2014 so the NVidia inspector version has moved but I was still able to find all the settings I needed to change. Anyway - I'll stop rambling - hope this works for some of you. Regards Jamie

Hello all, I've recently built a new machine specifically for the release of the wonderful FS Labs A320X. From a performance standpoint, everything is good. I get 40 - 50 FPS in the cruise and 25-38 FPS on the ground depending on what airport I'm at. The issue that I'm having is with VAS. I have followed all of the guides on this forum along with some that I've found on Youtube. I understand that this product, for now, has a trade off between scenery visuals and flying performance. I'm still trying to dial in that medium. I won't dive into my each and every setting as they are per the guide stickied in this forum with the exception of scenery complexity because I do want gates at my airports. My main question is does AA have any affect on VAS? For the past 3 years I've been flying on an older i5 ASUS laptop so I had a very limited range that I could play with in terms of settings. Now with my higher end machine, there is so much to look at. My specs are as follows: Hardware: i7 6700k @ 4.4 Ghz GTX 1060 3GB Pascal GIGABYTE G1.Sniper Z170 16GB DDR4 3000 mhz Windows 10-64 bit Software: FSX-SE ORBX Global ORBX Vector ORBX oLC NA REX4 Texture Direct (settings per FSL recommended) ASN Imaginesim KCLT LatinVFR KRSW LatinVFR KMIA FSUIPC (registered) GSX Directx10 Fixer Before I get yelled at too much, I have disabled ORBX Vector and oLC with not too much difference in VAS usage. I have not disabled global yet, but I will try it. I've been trying to get a flight from CLT - MIA in and all 3 times I've OOM'd on final at MIA. Right now, when I load up the A320 at KCLT, I have about 1.1GB of VAS remaining. At the time of pushback I have about 750MB remaining. I start getting the FSUIPC alert at around 400MB which is when I'm on approach. I know that a happy medium lies somewhere within all the inspector and DX10 fixer settings, I'm just still working to figure it out. I was basically just wondering if AA and sampling settings affect VAS at all. Thank you all and thank you to FS Labs for this amazing aircraft. I was never that much of an Airbus fan until now! Happy Holidays Matt

Hello, I have: Genuine FSX SP2 , FSUIPC, and FSLabs A320. Nothing else! No add-ons or anything! This can tell you how desperate I want to fly A-320. PC: Win 10, i7 6700@3.4ghz,gtx 970.16Gigs of ram HT off or on no difference actually, and yes, all threads are on , CPU usage is around 50% goes up to 100% from time to time. I can not get above 25 FPS, 20 at takeoff Tnx in advance, cheers

I want to buy fslabs a320 but I have fairly old PC . I just want an insight what performance will get ? PC config :- Processor - AMD 1090t Black edition . Base clock 3.2ghz over clock 3.6 GHz . 6 cores . Motherboard - GIGABYTE 780 LMT USB3 Ram - Gskill ripjaws 8 GB 1666mhz Graphic card - Asus gtx 950 2gb strictly edition. PSU - 650 watts . Thank you.

Hi, I have a weird issue with FPS, basically it is around 25-30 in VC, on my AMD 8250 / Geforce 980, but every 20-25 seconds it drops down for about 5-8 seconds, and after that it returns back to 25 - 30. In 2D cockpit it is similar, I have 50-60 FPS and every 20 - 25 seconds it drops down to 18-20. Any ideas to this? best regards

Hello everyone, i bought the FsLabs A320 yesterday and installed it. I experiencied very massive performance issues in the VC, although I have an I7-920, 12GB RAM and a NVIDIA GTX 660 I only have about 10-15 fps. I already set everything up so I have outside the VC about 40fps but not in the VC. Textures are on 1024. Thanks for your help.

Hello as I have read numerous times here on the forums, the FSL A320 seems to be very demanding on frames and as a P3D user I didn't have the chance to get my hands on this beauty yet so I just wanted to ask if my system would cope with the FSL A320 in P3D (as for all the other add ons its all smooth, PMDG 777 etc) My system: intel core i7 4720HQ 3,6 Ghz 8GB RAM 500GB HDD Win 8.1 nvidia GTX 960M many thanks in advance

I saw on another forum that this lovely plane is released - and was about to purchase it last night, until I read about the performance requirements. I've got a Mac Pro running Windows 7 x64, Intel Xeon 3.2ghz and Radeon 5870 1gb. Also have 8gb ram - which I can upgrade to 16gb, 32gb or more. I generally run FSX at 2560x1440, the native resolution of the screen I have. I know FSX doesn't care so much about graphics cards - it CPU power (high clock speeds), will it work with okay frame rates (eg, 25-30fps)? I can upgrade the ram, and I could upgrade the graphics card if it will help, but the CPU I cannot do anything about short of buying a PC (the mac is also used for work). I can run the Concorde and also the PMDG 777 with pretty good frame rates. That said, is it likely to work okay? Regards, Chris

Owning this airplane is bittersweet. It's the best aircraft addon for FSX so far, but the low settings I need to have in order to get acceptable fps... that's just horrible! I had my FSX settings almost at max for PMDG NGX with ok fps, but now.. it's like I'm back in the days when I had a dual core processor(I have i7 4790 4.0 now) . Flying with these terrain settings is not immersive at all. Don't get me wrong the airplane is beyond amazing! I hope that better CPU's come available soon.

Hello, I have quite a big problem- I installed Concorde X yesterday and wanted to test it immediately, but when I loaded the aircraft via the FSX menu and pressed ''Go flying'' it loaded but after it loaded the systems there was an ''invalid licence'' error and FSX closed. Then I started FSX again and started the Perf. Manager, but all buttons were grayed out and it said: FSX Status: Disconnected. I absolutely dont understand what happened. I have the box-version of Concorde X v1.2 (with SP2 built-in) bought from Aerosoft and installed as administrator on Win 7 Home Pr. 64-bit and FSX standard with Acceleration expansion pack. Any help would be very appreciated to get this wonderful bird in the air. Thanks in advance, Maximilian

First, apply Bojote's tweaks: http://www.venetubo.com/fsx.html They really work GREAT and will do wonders for most of you. The only thing I'd rather not do is to use an external limiter. I prefer the internal FSX's limiter to 30 fps. Then I always apply this nVidia Inspector for my nVidia graphics card: If you don't mind to get you hands "dirty", then the AVSIM Software and Hardware Guide for FSX is a MUST Appart from that, I always TURN OFF land and sea traffic, which hits very had on FPS. Also, I have to lower autogen to normal or lower in complex sceneries in order to avoid OOM (Out Of Memory) errors. See here.If running My Traffic X like me NEVER set it avobe 40-50%, specially in busy airports, when about 30% gives you plenty of traffic. These simple things really changed my simming experience. Bests,