Lets be honest, FSX is not that bad in stock scenery. These I enjoy with all other aircraft except FSL Concorde. Not CONCORDE ADD ON IN FSX as we know it with its nice add on's.
I use a bare stock FSX as a CONCORDE SIMULATOR platform with basic scenery and My thinking (to keep me flying FSL Concorde) is that Unfortunately this is what I do (deactivate heavy departure and/or destination scenery) but by this way I never have any OOMs with Concorde. This means that you have some 700~800 Mb spare for clouds and AI traffic. I cant fly Concorde X without the constant risk of ooms on finalĪndreas it is a big compromise to deactivate nice add on scenery but to be honest, once you do it you are not in constant risk of OOM.Ĭoncorde Cold and Dark loads some 2.5 Gb of VAS and while en route and to final approach stage with everything operating it will not go above 3.2 Gb. In order to use this product, I have to turn off all other addons and go au naturell. I have never understood which stay and which clear out later. Some of the scenery load on VAS clears after you leave the area and some does not. Lefteris, once you asked me UTX adds 300~400Mb on a departure from Heathrow to the west.Ī heavy add on airport will load 200~500Mb depending on options selected.įlying the Concorde at Dawn/Dusk is also not very helpful since the 2D textures load more heavily (and keep the VAS space consumed for later) as they refresh to follow up with differing lighting. This leaves some little room for an external view load (~100 Mb) and the occasional AI traffic texture FSX will load. While en route it will go up to 3,6~3,7Gb and on landing at a large (default FSX) airports it will reach 3,8~3,9 Gb. On Concorde's departure with all ncessary 2D opened at least once the VAS will be 3,3 gb by then. In a large default airport the VAS will start with 2.4~2.6 Gb with Concorde having everything off and 2D panels not loaded.
The rest of scenery enjoyment I leave it for all the other aircraft I fly.
I don't like it but until - if ever - FSL release an improvement update on the issue, at least this way I enjoy this amazing aircraft.
So all I do is disable the add on scenery to be flown through (including UTX) and I manage to have a trouble free flight. At some point you open them via VC to set the necessary settings for the flight. It is a big compromise in aesthetics and FS immersion factor but at least this is my way of guaranteeing no OOM's up to arrival.ĢD panels' load we can't avoid even if we fly on VC.
Even on big events I cannot participate because by the time FSX loads more than ~50 different liveries then it consumes valuable VAS that is needed up to the end of the flight.
I fly only on line on VATSIM network so I do not have the extra load of AI traffic from other traffic software but the occasional live AI traffic in VATSIM. All other scenatio's I have tried and at some point you get the lethal 4 Gb limit on arrival at destination or even earlier. Simple as that.įlying from default FSX to default FSX scenery (even large airports) without having anything in between like UTX or heavy add on airports will produce a worst case scenario of 3.95 Gb VAS. If I want to have a flight without OOM worries I have to have all scenery and other add on's disabled. In my post early on this thread I detailed how I avoid OOM's.įollowing further extended tests flying in all sorts of areas of the FSX globe with and without add on sceneries I have concluded to the following.