Hi.I have now done three flights with the LDS 767 and trying to get to one of the German Airport destinations but keep getting this FE.Dll error when getting close to the airport.I'm not bashing, just curious as to weather or not anyone else has had this problem.I'm running Win XP Pro with the 3GB switch, and FS9.1. ASv6.5, FE, GE Pro and was connected to SB3 at the time.I have had this happen yesterday too when flying from CDG to EDDK in the LDS 767.I have used the LDS 767 for ages without any issues, so this has left me to wonder if there are any probs with the GA Cologne Bonn scenery that anyone is aware of.Thanks for any ideas.Of course I will try another flight shortly from the same CDG airport (default) to EHAM and see if I get any error then. if not then it just leaves me to think about keeping the GA airport or get rid of it.I haven't changed anything on the sim except add the German Airports EDDK

AES ?

Hi Johan.Nope, no AES anywhere.I have just removed the 3GB Switch and put the original FS9.1 exe back in the FS folder.I will try a series of flights tomorrow and see what happens.Thanks for th suggestion though.

Hi.I have now done three flights with the LDS 767 and trying to get to one of the German Airport destinations but keep getting this FE.Dll error when getting close to the airport.I'm not bashing, just curious as to weather or not anyone else has had this problem.I'm running Win XP Pro with the 3GB switch, and FS9.1. ASv6.5, FE, GE Pro and was connected to SB3 at the time.I have had this happen yesterday too when flying from CDG to EDDK in the LDS 767.I have used the LDS 767 for ages without any issues, so this has left me to wonder if there are any probs with the GA Cologne Bonn scenery that anyone is aware of.Thanks for any ideas.Of course I will try another flight shortly from the same CDG airport (default) to EHAM and see if I get any error then. if not then it just leaves me to think about keeping the GA airport or get rid of it.I haven't changed anything on the sim except add the German Airports EDDK

FE.DLL crashes usually indicate a problem with faulty textures (FE = Flight Environment) and these could be scenery textures but are most often a problem with AI aircraft. It can also be caused by faulty textures on the user aircraft but this usually only occurs when viewing from outside.You could conduct some tests by, in turn, i) turning off the add-on scenery and ii) turning off AI traffic. If the latter, identifying exactly which aircraft is causing the problem can be extremely tedious.Hoping this helps,John

FE.DLL crashes usually indicate a problem with faulty textures (FE = Flight Environment) and these could be scenery textures but are most often a problem with AI aircraft. It can also be caused by faulty textures on the user aircraft but this usually only occurs when viewing from outside.You could conduct some tests by, in turn, i) turning off the add-on scenery and ii) turning off AI traffic. If the latter, identifying exactly which aircraft is causing the problem can be extremely tedious.Hoping this helps,John

My experience is this:FE.dll errors can occur in this situation if you have two copies of the same bitmap file - ie. one in the aircraft folder and one in the main texture folder - and they are in different formats (one DXT3 and one 32-bit)... Mostly can happen with lightmaps but perhaps also with prop textures. Have you installed any new AI textures recently?I have had this happen a couple of times in the past and get around it by being careful to check the texture formats when installing new aircraft... You can also get a batch program to convert all the textures in a given folder to the correct format...Geoff

Hi Gang.Thanks for the thoughts and suggestions.FE=Flight Environment, Hmm, this one caught me by surprise also as I don't have FE running, I just fired it up the other day to select the cloud set I wanted ASv6.5 to use. But I might un-install it and re-install it as I have the boxed version, and then just up-date it via the Flight1 files.As for Aircraft textures, then I will have a look at the textures in my LDS and make sure that there isn't anything wrong there too, as I have added two paints in the last few days. well, One paint really, one is in DXT3 and the other 32Bit. they came as a single download.I will keep checking this out, and try it with a default a/c such as the Lear and see what happens, if all goes well then it might point toward the LDS.Thanks again.

...FE=Flight Environment, Hmm, this one caught me by surprise also as I don't have FE running...

In this case, the module FE.dll is an integral part of fs9 related to texture management and not really part of the Flight1 product with the same name. However, the textures from said addon could well be the cause of the problems...http://forums.surclaro.com/ftopic6317.html"That error is can also be attributed to a texture displacement problem ie. 8 bit bmp which should be either DXT3 or 32bit 8888 enhanced"Related to my own experiences, there is one good thing about this error: it is NOT random. Once you have found a situation in which it occurs, it will alwasy happen when you load the sim there... this means that you can, at least, know you've got it or not when testing your changes...Geoff