FE.dll CTD on night-approach LOWW 2.0 (FS2004)

Post Reply
Posts: 3

FE.dll CTD on night-approach LOWW 2.0 (FS2004)

Post by whiggy » Fri May 14, 2010 9:30 am

Hi @ all!

Since I Installed LOWW 2.0 I have a CTD with FE.dll Error on every night-appraoch on LOWW 2.0.

I reinstalled LOWW 1.0 and all Errors are away.

I am using FS2004.
Site Admin
Posts: 5202

Post by martin[flytampa] » Fri May 14, 2010 12:51 pm

FE.dll crash might indicate a corrupt night (_lm) texture. First check LOWW2 with AI turned off (slider to 0), if it still crashes we need to figure out what file is causing the error.
Site Admin
Posts: 5202

Post by martin[flytampa] » Sun May 16, 2010 3:40 am

Try the following:

With Windows Explorer go into Addon Scenery/FlyTampa-Vienna/

There rename the folder "Texture" to "Texture1" or so.

Try again, no need to test with long flights, just slew away around in time mode (R + keys).

The scenery will be untextured with the folder renamed, but if it doesn't crash we know you have a faulty texture file causing it.
Posts: 112

Post by TJC » Wed May 19, 2010 3:23 pm

I've worked for the better part of the last 2 weeks on a new AFCAD/ADE file for LOWW, but as it was always during the day for best visibility I have never had any problems here.

Browsing the forums here today and remembered this post, tried it myself and bang, FS crashes.

I've done some testing since it crashed and found some interesting info from my set up.

Dawn, Dusk, Night testing, 100% AI, FS crash.

Dawn, Dusk, Night test, 0% AI all ok, which leads me to think AI is a problem.

Further test;
Dawn, Dusk, Night, 99% Ai, Austrian Airlines removed, all ok.

Dawn, Dusk, Night, only Austrian Airlines installed, all other AI removed, crash.

Back to the original post, what AI are you using whggy?
Custom installed (AIA, AIG, PAI and others), WOAI or payware (Ultimate Traffic, My Traffic)?

My AI is all custom from the usual places, AIA, AIG, PAI and many many others.

I need to check all lightmap textures for Austrian to see if one of them is causing my trouble.

However, the fact that you say when you re-installed V1 everything was fine doesn't solve the AI problem route.
That seems to suggest something else is wrong here somehow.

Please test out Martin's suggestions and reply so we can narrow this down.
Post Reply