I have neither FTX England nor FTX Global installed...I still enjoy the old combination UTX Europe + GEX2 and use Opus for weather. I have landed several times in UK2000 EGKK V3 without any problem, the last one was just this evening after an almost 7 hrs flight from KJFK. My rig is: I7-2600k @4.8Ghz (liquid cooled by Corsair H100), GTX680, 8GB DDR3 Ram @2133, ASUS P8P67 M/B. My tweaks are Bufferpools=0, Highmemfix=1, Affinity Mask=14, FFTF=0.1, LOD_RADIUS at 5.5. I have Vsync 1/2 refresh rate set through Nvidia Inspector and 30 fps locked in fsx.cfg.

I have been using this set up for almost two years now mainly flying NGX without issues, no CTD...no OOMs.... I have been using the T7 since it was released and found it a little bit worse than the NGX on FPS, but so far (keep fingers crossed), no OOMs.

Regards 

I'll say what alot of people been saying. Disable the airports and the scenery you are not landing at. If I'm flying from charlotte to ksfo, those are the only 2 airports I have enabled with FTX global and UTX USA. Everything else is off.

When you are flying at 37000ft, you cant see details anyway so why have them loaded into memory just to OOM when you get ready to land. It takes me 5 mins to disable all the other scenery with the scenery editor program. This has saved me lots of frustrations because I use to get OOM lots of time when it was time to land especially flying to NYC with manhattan X.

 

I flew from jfk to kai tak and my vas on landing was 2.9. I have all my textures set at 1024 and I cant tell any difference from 2048 or 4096

(...) It's a shame because i can even do turnarounds with the NGX without any sort of OOM and keep the LOD_RADIUS at 6.50000 and when using the 777 i can't even land.

 

(...)

 

 

And that's hard to understand:

 

The T7 has a slightly bigger virtual footprint than the NGX (less than 200 MB) - and the effect seems to be stronger than you would assume from that figure.

 

Have you tried again with the NGX? (Wondering whether Gary's latest releases like Luton have increased the strain on VAS.)

I flew into Gatwick about 3 hours ago.

 

Lod Radius 4.5

AS2012

1024 Textures

FTX Global

UK2000 Xtreme Gatwick

UT2 50%

 

No OOMS. !

And that's hard to understand:

 

The T7 has a slightly bigger virtual footprint than the NGX (less than 200 MB) - and the effect seems to be stronger than you would assume from that figure.

 

Have you tried again with the NGX? (Wondering whether Gary's latest releases like Luton have increased the strain on VAS.)

 

Yeah Olli, i have no issues with the 737 in any airport even when doing turnarounds (not THAT common i admit).

 

My solution is removal of the addon regions (England, Wales, etc).

I'll say what alot of people been saying. Disable the airports and the scenery you are not landing at. If I'm flying from charlotte to ksfo, those are the only 2 airports I have enabled with FTX global and UTX USA. Everything else is off.

When you are flying at 37000ft, you cant see details anyway so why have them loaded into memory just to OOM when you get ready to land. It takes me 5 mins to disable all the other scenery with the scenery editor program. This has saved me lots of frustrations because I use to get OOM lots of time when it was time to land especially flying to NYC with manhattan X.

 

I flew from jfk to kai tak and my vas on landing was 2.9. I have all my textures set at 1024 and I cant tell any difference from 2048 or 4096

Disabling airports or scenery you are not using is one of the greatest tweaks of all time, and I only just learned of it this year.  SceneryConfigEditor makes it so simple and quick, just take the time to know how it works so you don't mess up your scenery.cfg file.   Devgrp is so right about flying high in cruise, what is the point of having heavy framerate payware airports on if you are not using them and not even looking at them, even if you fly over them.  Ok, I actually like to go to wing view and admire some payware airports if I happen to be passing them over, but it's a fleeting enjoyment that's over in 2 minutes, and they take up valuable resources.  

 

HD cloud sets are another performance killer or can cause OOMs, no one needs 2058 or especially 4096 HD sets, not unless you are taking screenshots for contests.   1024 is about all you need, I find I get even greater performance with 512 sets, and the clouds are more realistic to me because they are more "wispy" and not as hard edged and sharp as the higher resolutions.

There is another helpful thing:

 

If you were always able to fly with the NGX, but you have problems with the T7, then look into disabling RAAS. In the DLL.XML there is a new entry by the T7, the RAAS, and you can freely deactivate it by setting False to True, and it will effectively save you about 100MB of VAS. Additionally, while doing that, I disabled some other things that were not always needed, like FSRecorder, and went another 100MB down.

1024 Texture here.

 

No scenery deactivated.

 

ActiveSky 2012 (no REX textures)

 

Don't have FTX Global (do have GEX)

 

Just flew from KORD (FSDT) on Vatsim to EHAM (Aerosoft on top of NL2000)

http://www.vataware.com/flight.cfm?id=12315990

Also flew over an active FTX England and/or Scotland, don't own the Northern Ireland one. I didn't deactivate my UK2000 Manchester Xtreme, but not sure I flew over it. Certainly was too far north to fly over UK2000Xtreme EGLL and EGKK.

 

No OOM.

 

Never left the VC though either. Did use GSX on arrival. 

 

Wasn't recording using FSrecorder, but I didn't deactivate or uninstall it.

 

1024 textures. Good enough to get the job done

Nuno,

 

sent you a PM, but yes I was able to complete a full LPPT - EGLL withou a glitch.

 

I am using no scenery other than LPMA and Lukla ( Aerosoft ).

 

Weather injector - FSGRW

 

A few pics attached ;-)

 

I hope you sort it out!

 

 

 

 

 

 

 

 

There are a few good points here. 1024 clouds are actually more realistic, yes. Just look out the window and most clouds aren't as sharp or as detailed as you can see in the simulator. I think i can start with that, reducing the 2048 set i have to 1024. I also remember leaving the cockpit 3 or 4 times to 'look around' in every flight and this is a known source of memory leakage. Each time you 'go out and back in' there is loss of memory.

 

I didn't want to deactivate airports as i will probably forget to activate them someday and find myself flying into a default airport, but this is true: I really don't need airports that i'm only going to overfly. This is another thing that i might work on.

 

I am not using RAAS, i found it fun in the first 10 flights but then it becomes annoying and so i disabled it.

 

I'll give these a try and see if i can land using all my beloved ORBX regions.

 

 

@jcomm: Using default scenery and only the airports will cause no problems at all. I wanted to have all regions enabled and still be able to fly there using more modest settings. Let's see if i can get there

worth giving dx10 preview mode a try alot of people report much easier time on oom issues with dx10 working, follow the instructions in the forum section for setting this up, worth giving it a try.

There is another helpful thing:

 

If you were always able to fly with the NGX, but you have problems with the T7, then look into disabling RAAS. In the DLL.XML there is a new entry by the T7, the RAAS, and you can freely deactivate it by setting False to True, and it will effectively save you about 100MB of VAS. Additionally, while doing that, I disabled some other things that were not always needed, like FSRecorder, and went another 100MB down.

 

Thanks for the heads up on RAAS, and it's impact on VAS.  The airline I'm flying, Delta, doesn't use it, so it will only help matters if I disable it in the dll.xml.  I'm always looking for ways to prune unnecessary resource usage in FSX, and this is a very helpful tip!

And that's hard to understand:

 

The T7 has a slightly bigger virtual footprint than the NGX (less than 200 MB) - and the effect seems to be stronger than you would assume from that figure.

 

The T7 adds more then 400MB to Vas usage on my system with 1024Mb textures.

This has been confirmed by Ryan who will amend the Vas figures in the next iteration of the manual.

 

Btw people never seem to mention the effect screen resolution has on Vas. I run 1440p and when testing dropped to 1080p. I gained around 350MB. That's more then I could save by turning off AI, drop auto gen to spare and drop and disable all unused scenery.

Disabling the RAAS via xml actually puts the VAS usage of T7 in the area of NGX, if not even slighly lower. Btw. it also gets on my nerves when loading the simulator and then I get a loud prompt that I am "on runway", argggg. Disabled.

Overall I never broke the 2.0 gig mark with the 777 but then again I don't have a huge load of scenery installed and no AI is running.