Guys, I have a long list of dlls in DLL.XML files due to all my installed addons.

 

1. Is it a good practice to disable those I'm not using? Can it actually help the performance?

2. Do I really need these ones enabled if I fly to/from Aerosoft and FSDT airports:

- Addon Manager bglmanx.dll

- VistamMare ViMaCore.dll - this one is particularly annoying as it offers some updates and keystrokes I don't need. I understand it is from FSDT, but do I have to enable it in a FSDT airport?

3. Aerosoft\Flight Recorder AS-FlightRecorder.dll

 

There are also other dlls of the aircrafts I'm not flying, do I need to disable them one by one if not flying a particular aircraft?

 

Thanks,

Dirk.

Unlike an executable... a DLL does absolutely nothing unless called upon to do so. So, unless they're poorly written, they do nothing harmful being loaded.

Do they sit in RAM taking up memory if loaded?

.dlls are mapped into the application's Virtual Address Space (VAS).

So if you're running close to max in that space, having the .dlls in RAM could be eating up memory you might need otherwise, yes?

 

Or if they're not presently active do they just go to page file?

FSX has no way of knowing what dll's are needed except via the dll.xml file. They are all loaded by default unless the dll.xml specifically tells FS not to. The Level-D.dll is one such. The bglmanx.dll is required by the FSDT scenery. In general, FSX handles the loading better than FS9 did, so your best bet is to leave it alone unless you know exactly what you are doing.

 

DJ

FSX has no way of knowing what dll's are needed except via the dll.xml file. They are all loaded by default unless the dll.xml specifically tells FS not to. The Level-D.dll is one such. DJ

Good info, ubersu. So if you think you know what you are doing you can potentially save some unfragmented VAS, which has become more and more important with all the heavy addons recently.

 

Thanks,

Dirk.

Yes I've taken to selectively loading my pay ware aircraft dlls and not "Trusting" them at startup, to try to save a few bits of VAS and I have no idea whether I'm waving a magic wand at a blue dragon or actually accomplishing something (these dlls are listed in fsx.cfg so might be a separate issue).

You can tell FSX which DLL's to load selectively, by adding the following line to each of your optional addon entries in the dll.xml file. Do not add it to addon dll's you use on every flight.

 

<ManualLoad>True</ManualLoad>

 

Now when you load FSX it will ask you if you want to load each of those dll's separately. Say yes only to the ones used for your flight. It's a little inconvenient, but I think it will solve many of your problems!!

How big are these friggin' .dlls that they are chewing up too much memory?

 

regards,

Joe

How big are these friggin' .dlls that they are chewing up too much memory?

 

regards,

Joe

Joe, what if they just defragment VAS? That would be enough for disabling them when possible. I'm guessing, of course.

 

Dirk.