Thaks Luca, will try that. I am using the 4.4 but its strange it only started to happen the past week or so. Never happened before from 3.9 to date.Will try your tip and see if it works.Bill

>For AFCAD errors, I do what you do, run the fault finder and>try and correct any faults until the AFCAD file shows no>faults found. If there's still a CTD at that airport, then>something is wrong with that particular scenery. I also find>that when you install a new scenery, you have to check and see>if you might have also installed an AFCAD for the default>scenery for the same airport. This can cause conflicts. Just>use one or the other.>>LeeI have for the same custom airport 2 afcad files;a custom afcad file in the airport folder and a default afcad file (for the default airport in case I disable the custom one) in the addon scenery folder.because the custom airport has a higher priority than "addon scenery" of the two afcad files only the custom afcad file is being loaded.Is this OK or causing me more troubles?I'm still having CTD problems.... I guess it has to do with the graphics drivers/card as the screen gets black (with a crash after 10 seconds).I'm able to fix it inverting the rendertotexture option; it seems to restore flight simulator without crashing!unfortunately it doesn't give me a clue whichever rendertotexture setting is better; in fact I'm still getting the black screen with both rendertotexture set to on or off.I seem affected while switching from fullscreen to windowed (and viceversa), changing from VC to 2dpanel and resizing window.....cheersLuca