Long haul flights are mostly impossible for FSX and P3DV2 users too. Depends on the scenario. People are just turning up their overclocks and config settings too high. Hope Dovetail fixes your problems.

 

Best regards,

 

I first agreed with this point of view, but I tested with much lower graphics settings than what I normally used in FSX where I never had terrain.dll issues, and I still encounter the terrain.dll crash.

 

 

55 minutes just totally wasted. I ask myself, is this hobby really worth it.

You are lucky you only wasted 55 minutes.  For me it was sometime hours of tweaks and reinstalling.  At the end, and thanks in part to the issues that FSX-SE has, that I reinstall FSX and stopped at installing FTX Global and Vector.  Lo and behold, I have the smooth sim I have been looking for.  I did not install any ORBX regions, nor all the other scneries that I just blindly reinstall before.  So now I will install one scenery at a time, and if it gives me grief in term of stutters and crashes it's out of the sim for good. 

That was 55 minutes sat at a gate prepping the flight in FS2Crew. Did not even get to fly for 1 minute. That's what I call a waste of time.

That was 55 minutes sat at a gate prepping the flight in FS2Crew. Did not even get to fly for 1 minute. That's what I call a waste of time.

Ouch, indeed. That's why for now, FSx-se is off my system, back to Fsx for now.

There does not seem to be any consistency with this platform, i.e. FSX-SE.

 

Just had a terrain.dll CTD when a mere 259.1 miles away from PHNL after a long flight from CYYZ in the PMDG 777-300ER. To get this far and so close to beginning descent, then this CTD. Quite frankly, DTG have brought out a complete lemon! That's it. Time to ditch this time-wasting nonsense.

I'm starting to see a lot of d3d11.dll errors, in addition to terrain.dll and g3d.dll. Has anyone else using DX10 and FSX-SE seen the same?

 

I'm aware of removing KB2670838 as a possible fix, but I've had DX10 and this windows update for years installed and only recently starting seeing this issue in FSX-SE. At this point it's impossible to even complete a short range flight.

No problems with d3d11.dll errors. I can always complete short hauls. Longer flights > 4 hours = no bueno.

A mere 259.1 miles from the destination well into a CYYZ-PHNL flight was the last straw for me. I could have lived with a CTD >3-4 hours, but deep into the flight. Sorry. No.

 

Time to head for the boxed version of Train Simulator-----far less crap than this nonsense that FSX-SE is at the moment as it stands. i-in-5 flights without a terrain.dll CTD is just not good enough.

I was able to do a transcon flight without any crashes with AI enabled and settings turned up. I was able to get in KSFO under the 4 1/2 hour mark which is usually the point in which I CTD. Whoo!

I was able to complete a long flight today, no d3d11.dll, terrain.dll or g3d.dll errors after adding affinity mask to my config file. A thread in the steam forums suggested that adding the mask would leave the first core open for the system, and put FSX-SE on subsequent cores (based on your cpu and selected affinity mask). I used a FSX affinity mask calculator to get the proper setting for my system configuration. I don't recall the link, but you should be able to find it by searching Google.

 

So far after adding the affinity mask to my config, I have not seen any of the above issues. I'm going to try a few more long flights before I say this is a definite fix for the issue, but so far it has worked. Full disclosure, before adding this to my config file I did run a repair installation on FSX-SE, and reinstalled Global, Vector and FSGlobal 2010.

 

I would be interested in hearing if adding the affinity mask to your config worked for anyone else as well that is using FSX-SE and have these issue while doing long flights.

I used an AM=14 and I still got the terrain.dll CTDs. Intel i5-4670K o/c to 4.2Ghz, no hyperthread.

I completed 17 hr flights ( Newark-Mumbai) successfully! hope everyone else gets a fix for the problems

Which sim, Sidhant? FSX-SE or FSX-MS? And care to share your settings that enabled you to do a 17 hour Newark-VABB flight without any CTDs?

Which sim, Sidhant? FSX-SE or FSX-MS? And care to share your settings that enabled you to do a 17 hour Newark-VABB flight without any CTDs?

Also, what kind of add-on were added.  Has anyone just do a very long flight with plain vanilla FSX-SE?  I am curious to see which add-on may cause CTD.  Terrain.dll crash is due to loading mesh, whereas G3d.dll crash is due to loading graphics.  

I was able to complete a long flight today, no d3d11.dll, terrain.dll or g3d.dll errors after adding affinity mask to my config file. A thread in the steam forums suggested that adding the mask would leave the first core open for the system, and put FSX-SE on subsequent cores (based on your cpu and selected affinity mask). I used a FSX affinity mask calculator to get the proper setting for my system configuration. I don't recall the link, but you should be able to find it by searching Google.

 

So far after adding the affinity mask to my config, I have not seen any of the above issues. I'm going to try a few more long flights before I say this is a definite fix for the issue, but so far it has worked. Full disclosure, before adding this to my config file I did run a repair installation on FSX-SE, and reinstalled Global, Vector and FSGlobal 2010.

 

I would be interested in hearing if adding the affinity mask to your config worked for anyone else as well that is using FSX-SE and have these issue while doing long flights.

[uPDATE]

Tried another long flight and I got another terrain.dll error. Affinity mask is not the solution to fixing this issue. Back to waiting in hopes that Dovetail will release an update for the issue.