Search the Community
Showing results for tags 'memory'.
Updated: 27th February 2016 - Should anyone have any suggestion I will be most pleased to update and improve the text. Just leave a reply to this post. FSX is and will always be a 32 bits application. At the time of writing this post (september 2016) P3D (latest version 3.3) is also a 32 bits application.That means they can only handle 4 Gbytes of your installed RAM. No matter how much RAM you've got on your system. Even if you have 128 GB of RAM a 32 bit application such as FSX or P3D can only make use of up to 4 GB of RAM. Concorde-X is probably the most demanding plane on the market regarding memory use, but I don't think you'll ever have a problem if you fly Concorde-X using default sceneries and reasonable settings. However, you'll very likely get OOM errors (Out of Memory) when using extreme settings and/or other memory demanding addons, such as complex sceneries like Aerosoft Heatrow (specially if combined with London VFR or specially UK2000 sceneries), Aerosoft Mahhattan (specially if combined with FSDream Team KJFK), Paris Charles de Gaulle (LFPG) or FlyTampa Dubai, just to name a few. Because there's no way to increase the amount of memory that FSX/P3D can use, which will always be limited to 4GB, the only solution to avoid OOM errors is to lower the memory demands. As far as I have been able to check, these are the items to take care of when experiencing OOM errors: Number of objects: Scenery objects: Each tree, building, ground assistant and vehicles, post and signs... Every single object needs a space in memory. Reducing autogen or the scenery detail will be of a great help to reduce memory use and has usually solved all my OOM errors. Traffic: Each vehicle is also an object. So using road and airport traffic, boats, etc, will also increase the memory use. It is also important to bear in mind that AI traffic addons, such as My Traffic X, ICE or SKY can introduce a great number of planes (objects) and textures (described next) which will noticeably increase the memory requirements. Airports: FSX/P3D will load airports even if you overfly them at 60.000ft and don't use them to land or even look at them. That means a complete waste of memory by loading a whole lot of unnecessary objects. In the Scenery Library it would be wise to only tick departure and destination airports unchecking all the rest addon sceneries to make sure that we are only loading default sceneries along our route. The free tool Scenery Config Editor is very valuable to easily activate and deactivate sceneries as necessary: http://fs-sceditor.sourceforge.net/ Textures: Varied textures: FSX and P3D come with a limited set of textures, so it is very common so see "repeated" the very same tile of land over and over again, specially over water, desserts, etc. Addons such as FTX Global solve this problem providing a much wider range of textures that help increasing the realism of our ground environment. However, using a wider range of textures means an important increase in our memory use. Most of our flights with Concorde will take place at supersonic speeds over the water. Water textures are usually very monotonous, so most of the times the range of textures won't be a problem for us in those kind of flights, but that is a factor to be taken into account if making a continental flight over land where we will load a wider range of different textures. Photo sceneries: For the reasons explained in the previous section, photo sceneries are a real memory killer, the reason being that no two texture tiles are the same. Even if you are not using a 100% photo scenery please take into account that some developers include a certain area of photo realistic textures around the airport. HD Textures: We all love HD textures... but they are also a memory killer. HD textures are great for the cockpit, but I would strongly recommend not to use HD textures for clouds. I personally don't find that much of a visual difference and, in return, I find a much better performance, specially in storms, and a greater margin to avoid OOM errors. Level of detail: The lod_radius setting in the [TERRAIN] section of the fsx.cfg or prepar3d.cfg files defines the distance from our current position at which the simulator will start loading textures and objects. At least in theory, that will help to reduce blurry textures in the distance or airports suddenly popping up from nothing on our approach because the textures and objects, airport in this case, will be loading long before we arrive. However, and as described in previous sections, having a lot of objects in a scenery can cause OOM. Having varied and HD textures can also cause OOM. Increasing both of them is certainly not a good idea. The default lod_radius setting for both FSX and P3D is 4.5. Extreme caution should be taken when Increasing that value and flying Concorde, as an OOM error is almost guaranteed. Toggle from windowed mode to full-screen mode Monitoring VAS Usage Using FSUIPC Source: http://www.avsim.com/topic/431663-vas-fsuipc-and-fsx/ FSX Menu bar | Add-ons | FSUIPC ... Select the Logging tab Enter an Offset of 024C (that's a zero) Enter a Type of S32 from the drop down box DO NOT check the Hex checkbox Press OK projectFLY Pilot Tools http://pawkbun.co.uk/ Microsoft tool TN Process Explorer http://technet.micro...s/bb896653.aspx Hope this info helps. Bests, PS: This is what Andrew Wilson, one of the developers, says about this OOM errors in one of the replies to this post:
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.
I recently purchased the FSLabs Concorde X and let me say that it is AMAZING. I have become familiar with flying the old iron steam gauges such as the DC-9 classic, 727, and 707, but the systems in the Concorde is unprecedented. The modeling FSLabs creation is top notch. I was happy to see that one of the developers was with PMDG and therefore a lot of the menus were familiar to me as they are almost identical to the MD11 from PMDG. With this being said, I have one issue...the dread OOM and black textures upon landing. My first flight from London to JKF, I landed, taxied off the runway and was performing the After Landing checks when textures started to go black then a minute later FSX closed due to a OOM issue. I never really have a problem with these and I have done trans Atlantic crossing in the MD11. I did have a problem that when I landed at the airport, only the jetways were visible. I couldn't see the airport buildings itself. Since my MD11 crossings I have purchased a boatload of new scenery files that I am sure hog up a much memory as possible. On my first flight I forgot to turn those off. So on my second flight to Paris from JFK, I closed down all add on scenery and upon landing, I was able to taxi to the gate, however I was afraid to open up any panels because I noticed black squares and textures missing from AI aircraft. (I forgot to mention that I was running Traffic 360, REX Textures for weather, and UTX in North America. I have seen some videos on YouTube from a fellow who flies from Heathrow to JFK with add on scenery and it seems fine. I have a similar setup as him. I saw the post about running in windowed mode but for some reason the bar at the top of the screen bothers me and I can not get over it. I did a couple of time hit ALT+ENTER to exit full screen to read a PDF and the bring it back to full screen. That maybe the issue there. What other steps can I take to ensure that I can complete a flight? I would one day like to get a scenery pack for JFK but right now I think that would kill my flight and cause me grief.