I've got this error after two consecutive short flights. During the first one, Madeira to Laayoune, all went perfect. I didn't close FSX:SE but I simply set up the aircraft and took off towards Dakar, just like a normal pilot would have done. After about two hours and half I've got the terrain.dll error.

 

My configuration is : Aerosoft A319, Orbx FTX Global and Vector, REX 4 Textures.

 

No sceneries, no weather engine, all settings to max except for water. 

 

Even with many more addons installed I haven't ever got this error on FSX or P3D.

I emailed Dovetail's support about this issue, after reading several "fixes" and suggested work arounds; which never worked I must mention, to get to the bottom of this issue, and they did reply. They said, "We are currently aware of this issue and we are working on a fix. When finished this fix will be downloaded automatically via Steam." -Dovetails Game Flight Simulator X Support

 

I found another post on the Steam forums from someone else with a similar response from Dovetails. I don't think any of the fixes in this thread actually fixes the issue. The best we can do at this point is wait for them to release the next update.

 

Anyone that suggest that this issue is just part of the way the simulator works, or you have your settings to high, or that Dovetails cannot fix the issue because legally they cannot release updates which they have already done, is probably being disingenuous.

When one reads the suggestions of how to the reduce the chance of the terrain.dll error, one finds two common recommendations:

 

1. Use an AM=14, for CPUs with >= 4 physical processors. Of course, if you have Hyperthreading turned on, the number is different. This change has worked for some people for some unknown reason.

2. Turn your settings down. Of course, this isn't much of a solution.

I wonder if the likeliness of getting a .dll error increases when using an aircraft that uses a comprehensive navigation database or similar...because I see a bit of a pattern from the PMDG and AirbusX users.

I only have PMDG 777 and Aerosoft Airbus 318/319 for P3d so I  can't say anything about the navigation database idea. My FSX-SE crashed almost predictably with no scenery add-ons and 3rd party aircraft. I tried reinstalling FSX-SE, using DX10 and even installing a lot of add-ons. It just made the terrain.dll CTD happen at different elapsed times into a flight. It's a bug and the only thing that reduced the CTD frequency for me were those two suggestions that I listed in my previous post above. 

Yea guys, I actually had to go back to FSX boxed until they fix this.  This along with Active Sky Next not working yet made my decision to do so.

 

Granted I only got the terrain.dll error on long flights but I'm not going to limit my flying to only 1-2 hour flights.  Just not going to do it.  The only aircraft I use is the PMDG 777-200LRF and the Airbus 320/321.  

 

So I've gone back to FSX boxed until this is fixed, then I'll go back to Steam.

Limiting my routes to under 4 1/2 hours seems to avoid this CTD completely. Else I have to resort to saving my panel states.

I wonder if anyone had this problem.  I had the MSFSX GOLD installed on a separate drive on my computer and I bought and downloaded the FSX Steam version and put it into my main drive. Once I turned on the Steam version for the first time, I got loads of dll.terrain  errors. I had lots of blue sky scenery installed in MSFSX and somehow Steam had copied all of the file names. After clicking okay about 50 times I finally got into the program and went to settings and found all the scenery files checked enabled just as they are in the MSFSX. The actual folders where not installed. The other thing was all my personal graphic settings were also transposed into this new version. I also noted that my MSFSX had interaction as well. I wound up deleting FSX Steam and having to reload the MSFSX I decided to wait for the 64 bit version before I switch. Has anyone else had this happen?

FSX Steam and having to reload the MSFSX I decided to wait for the 64 bit version before I switch.

There will never ever be 64 bit versions of FSX-SE or FSX. P3D, which is also closely related to FSX but under active development by Lockheed Martin, may be converted to 64 bit but this has not been confirmed it will ever be done.

 

Best regards,

Addons used:

 

Default Airports from both WSSS and KEWR

IVAO's IVAP app

IVAO weather 

PMDG 777 

(no CFG tweaks)\

 

As I had said to solve the problem I relocated the Steam folders completely ( uninstalled Steam and then reinstalled FSX)

 

 

P.S: How many folders are present in your Steam folder?(not the FSX or common folder , the root steam folder)

There will never ever be 64 bit versions of FSX-SE or FSX. P3D, which is also closely related to FSX but under active development by Lockheed Martin, may be converted to 64 bit but this has not been confirmed it will ever be done.

 

Best regards,

Wow, I hope that somewhere down the road someone or some company will create a new and better sim. 

My hope is that Microsoft will sell the FSX code so someone, like Dovetail or even LM, who can convert it to 64 bit and update the code to be compatible with modern computer systems. That would be a great service to the Flight Simulation community.

 

Best regards,

My hope is that Microsoft will sell the FSX code so someone, like Dovetail or even LM, who can convert it to 64 bit and update the code to be compatible with modern computer systems. That would be a great service to the Flight Simulation community.

 

Already been done; it's called P3D.

I'm now for two weeks returned from FSX-SE to the original MSFXS after the famous terrain.dll crashes. I since then never had any crashes or related errors.

 

I fly long/ short hauls with the PMDG 777 and 737 with Orbx global, vector, landclass, ASN and almost full UT2.

 

Glad I paid just 5 Euro for FSX-SE, because for me it is unflyable. And I don't think there will be a solution on short term.

Still the same old story FSX-SE keep crashing.