Search the Community
Showing results for tags 'out of memory'.
Found 1 result
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: