just tested your update v.1.98a and unfortunately still got the same CTD about 4 miles from the tarmac.
However, I think I might have good news for everyone suffering from this problem, as I may have found a way of making your workaround
("placing your aircraft to an AES-supplied airport before departing from a Non-AES airport") more stable. Iīve been testing my
modification of it about 20 times by now and I NEVER had a CTD with it. Tested my most problematic routes, I always got CTDs before & new
ones as well, all without a single CTD.
This is what I did (Oliver, if you donīt wanna read all the following, please go to the end, where it says "@ Oliver"):
Tried to find every Landclass-file on my system that causes a memory-leak (still need the /3GB-patch, though):
- Searched for empty texture-folders.
- Searched for files called "WC*.bgl" in the entire FS9-folder & -subfolders and moved all of them to "FS9\scenery\Base\scenery".
- Got FlightSim-Manager & its latest patches and consecutively searched for Landclass-files in each and every scenery-folder with an attached texture-folder.
In case a LC-file was found, I searched for .bmp files in the attached texture folder, named with a number of about 8-15 digits followed by two letters (something
like *su.bmp, *fa.bmp, *wi.bmp, *hw.bmp, *lm.bmp, *sp.bmp), and for .agn-files.
Two results were possible:
- No files like the ones described above could be found in the texture folder -> moved the LC-file to the "FS9\scenery\Base\scenery" folder (that doesnīt have
an attached texture-folder!)
- Files like the ones described above could be found. This case was a little trickier:
I followed the "memory-leak-discovery-pattern" described earlier in this thread and checked if this particular scenery had a leak.
If it did have a leak, I used "filemon" to see which files were missing and causing the leak.
In case I could find those missing files in any other texture-folder of FS (mostly they were located in "FS\texture"),
I copied them into the texture folder of the scenery being investigated (the one where filemon said, FS couldnīt find them).
In case I found all the missing files and the leak was gone, I left the scenery installed; otherwise, I uninstalled it.
Made sure "AES-lite" supplied airports use the latest version of it that is updated to be compatible with the /3Gb-patch
(Frankfurt_2008 for instance has a compatible version, for other sceneries youīll have to refer to Oliver).
Some sceneries with moving ground traffic, e.g. "Overlandīs Kansai" together with "URAKAWA - APT GROUND VEHICLES
for Kansai" can cause a very similar "g3d.dll"-induced CTD when arriving there from an AES-supported airport (even if Kansai
itself is not AES-supplied!!!). This kind of CTD doesnīt neccesarely only occur on final approach, but can also happen when just
flying over the aiport at high altitudes. Moving the airplane before departure from an AES-supplied airport to such an airport
should solve that.
BTW, I think that this could also be the reason for the CTDs, "Psolk" reported, when flying from an AES-supplied airport to a
Last thing I found was that when using Oliverīs "workaround", it was vitally important for the workaround to work properly, to move the
plane to a gate with MOVING JETWAYS at the AES-supplied airport before departure, wait there a couple of seconds until the jetway docks
at the airplane and then go to the Non-AES-airport for departure.
Attending to these 4 steps got AES back on my system :-) :-) and will hopefully help others too!
I think the most problematic part of loading AES at the arrival airport with active /3GB-patch is the moment the Jetways are being loaded.
I remembered that you once gave me an AES-test-version without moving Jetways which worked fine. Therefore tested your workaround again
in two different ways:
1. Moving to an AES-airport with moving Jetways prior to departure from a Non-AES airport and
2. moving to an AES-airport without moving Jetways prior to departure from a Non-AES airport.
Test No.1 never caused the CTD when flying to an AES-supplied airport with moving Jetways
Test No.2 always caused the CTD.
So maybe this is, where the core of the problem could probably be found?!
Can you tell me which "AES-lite" supplied airports use the new and updated version of it, which works with the /3GB-patch (such as the
one in Frankfurt_2008)?
Do you have any news on "Cloud9-KLAX", if it will ever be updated to be supportable by AES? Itīd be sooooo awesome to have an AES-KLAX!!!