You got rid of AI traffic which leaks memory (to be exact, it doesn't free it up again).

 

Best regards,

Robin.

I know how to set up FSX in DX10 mode. It simply does not look as good as DX9 mode on my PC.

 

Correct. It is incomplete, and always will be.

 

Best regards,

Robin.

 

 

You got rid of AI traffic which leaks memory (to be exact, it doesn't free it up again).

 

Who did ?

I have plenty of Ai under DX10 and P3D

The OP. AVSIM seems to merge posts sometimes, which gets confusing.

 

Best regards,

Robin.

 

 

Correct. It is incomplete, and always will be.

 

But still much superior to DX9 and we do not know how much further Steve may be able to take it.

Still with P3D and DX11 available and under constant development there is less need for FSX + DX10

Are you talking about FTX Aero??

 

 

Are you talking about FTX Aero??

 

windows 7 Aero, I could not get Vsync working under DX10 until I enabled Aero.

then after that my AA issues went away also

OOMs are mostly caused by duplicate afcads. With more people buying FTX products, you have dozens sometimes a hundred duplicate afcad files all confusing fsx. Flight1 AFX program does a great job listing all duplicate airport files for you to go through.

 

OOMs are mostly caused by duplicate afcads

 

Where on Earth did you get that idea? I do not have duplicate AFD files, but I can easily induce OOMs if I try to run too much high detail stuff at the same time.

Here is an excellent document written by Ryan Maziarz of PMDG about how to reduce VAS and eliminate OOM's:

 

http://support.precisionmanuals.com/kb/a108/vas-management-stopping-out-of-memory-oom-errors

However, here is another technique that ultimately solved my particular VAS/OOM issue in addition to suggestions of Ryan Maziarz and others. There are other tools, documents and techniques mentioned on the AVSIM forums and in AVSIM documentation like the CTD Guide.

I ran across the suggestions below on an AVSIM thread (contributed by AVSIM member tf51D) which I implemented to further help reduce VAS usage and OOM’s. This technique has pretty much eliminated the FSUIP4 beeping I used to get when I was nearing VAS limits, or prior to incurring an OOM.

I implemented the below process which basically prevents the loading of the following DLL’s during the FSX startup phase when I fly the PMDG 737 NGX on my system (your system may no doubt be different than mine):

1. Captain Sim 707 Sound DLL (needed only when I fly the 707)
2. RAASPRO DLL – built in and only used by the PMDG 777 on my system
3. A2A Service DLL (for A2A aircraft, possibly some other stuff)

I also modified all of my Orbx Scenery Object Flow DLL statements  in the XML file (I have a total of 14 Orbx airports and each airport has one of these types of DLL’s).

By the way, the DLL.XML file is located where the fsx.cfg file is (use the edit feature built into Windows 7 to modify XML file):

C:\Users\your unique name\AppData\Roaming\Microsoft\FSX\dll.xml

Most of my OOM memory issues happen when I fly the PMDG 737 NGX. These CTD/OOM issues usually occur at the end of the flight on final approach when nearing the Virtual Address Space (VAS) limits.

 

I solved it by setting many of my DLL's in the XML file to Manual load. By doing this, I only load, or not load, the DLL's for the addons I'm using for the flight. For example, there's no need to load Captain Sim DLL's, Feelthere DLL's, or Orbix Object Flow DLL's, for example, if I'm flying the NGX, but not flying into specific Orbix add-on airports. This is especially important, since VAS has to be contiguous. Clearing VAS contributors up front prior to loading FSX, makes larger amounts of VAS available at the later stages of flight.

 

This is why the great many OOM errors happen on approach, or just after landing, especially at addon airports, as the arrival airport has to load the detailed 3D objects of the airport/ground AI, etc. Even though it may appear there may be enough VAS to handle it, it may not have a large enough contiguous space to fit what is needed, causing the OOM.

 

Since modifying the DLL.XML file entries, I can now pretty much fly the NGX to any airport I own, without problems, and haven't had a OOM since, plus my FSX.EXE shuts down properly without crashing.

 

To implement this technique, add the following line to each optional section of the DLL.XML file, unless it is already there. (These are usually the airplane/scenery/sound addon dll's). Orbx items appear to already include this <ManualLoad>False</ManualLoad> command line, but I had to change the state from False to True to make manual load work.

<ManualLoad>True</ManualLoad>

Note: Leave the XML entries for the dll's you want to use on every flight alone, for example, utilities, llike FSUIPC, FSX SDK's, etc.

When you start FSX, it will then ask you if you want to load each dll, only say YES to the ones you will be using for this particular flight, and NO to those not needed. Every time you shutdown and restart FSX,  you will be asked to respond to this same list of questions.

 

Here is a portion of my DLL.XML file on my system to give you the general idea (Just be careful when you edit, it is easy to make a mistake):

 

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>dll.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Name>ObjectFlow_KRDD.dll</Name>
<Disabled>False</Disabled>
<ManualLoad>True</ManualLoad>
<Path>E:\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_AA_KRDD\scenery\ObjectFlow_KRDD.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>ObjectFlow_KWYS.dll</Name>
<Disabled>False</Disabled>
<ManualLoad>True</ManualLoad>
<Path>E:\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_AA_KWYS\Scenery\ObjectFlow_KWYS.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Addon Manager</Name>
<Disabled>False</Disabled>
<ManualLoad>True</ManualLoad>
<Path>bglmanx.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>ObjectFlow_KSFF.dll</Name>
<Disabled>False</Disabled>
<ManualLoad>True</ManualLoad>
<Path>E:\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_AA_KSFF\Scenery\ObjectFlow_KSFF.dll</Path>
</Launch.Addon>

//////////////////-------- Break---------///////////////////////////////

<Launch.Addon>
<Name>Visual Effects Tool</Name>
<Disabled>True</Disabled>
<ManualLoad>False</ManualLoad>
<Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>A2A Service</Name>
<Disabled>False</Disabled>
<ManualLoad>True</ManualLoad>
<Path>A2A\Shared\A2A_Service.dll</Path>
<DllStartName>module_init</DllStartName>
<DllStopName>module_deinit</DllStopName>
</Launch.Addon>

Bill Clark

Where on Earth did you get that idea? I do not have duplicate AFD files, but I can easily induce OOMs if I try to run too much high detail stuff at the same time.

 

I said mostly caused, I never said it was the only cause. Did you read what I posted?

 

 

By the way, the DLL.XML file is located where the fsx.cfg file is

I don't have this file DLL.XML - but the pmdg777 works fine.

I notice some of the entries are "<Disabled>True</Disabled>" , does this mean these items are not loaded by FSX ?

ther45k9,

 

Possibly the reason you don't have a DLL.XML is that you may not have any add-ons installed on your system. Everyone's system will be different based on their personal preferences.

 

As to the "<Disabled>True</Disabled>" line of XML code I'm not sure why that was set this way (hopefully I didn't inadvertently modify it?)............I'd have to go back to my system and look, but it is not important in what I'm passing as a positive experience to reducing VAS.  But the entries that helped me the most were these types:

 

<ManualLoad>True</ManualLoad>

 

Bill Clark

Hi,

 

The idea of just disabling stuff makes my blood boil.....This is NOT right that in the middle of a light you have to save flight or at TOD, you stop/restart FSX to clear VAS.

 

More so over, bloody disabling airports you don't fly....It does not make sense all of it.

 

By doing all of this, realism is flushed throughout the toilet along with the big xxxxx.

 

PMDG 777 usage of VAS is far greater than that of NGX 737....So PMDG should help in this area also. I hope SP1 will address that.

 

Scenery vendors like Aerosoft, ORBX etc...Must use image compression that do not eating much memory and balances out with performance and quality

 

And Microsoft, pioneer of a tradition, must come on top of things, worries cannot always be angle who's profit dollars....There is a tradition in this also. How many people have become pilot throughout Microsoft Flight Simulators....Shame on them, they don't see it this way. Real shame on them.

 

Yes, I have said it.

Regis  - An bho dhearg

We should not be wasting time on fixing this....We should be flying.

 

I said it.

Regis