Well Gentlemen,

 

I also receive this terrain.dll crash in FSX:SE, With a plain vanilla install and the FSX 747 after about 4-5 hrs of flight. 

(tested that one last night)

 

Yes, maybe I could avoid that by setting my settings lower (havent tried) but then again - If I need to lower my settings already in a plain vanilla install - what do I need to install FSGlobal mesh etc. then if I can't even have FSX's native 38m mesh display at highest settings? + FSX boxed never had that crash on my system, with a lot more demanding scenery installed and FSGlobal set to full right.

 

And except of that - the sim should not crash - only because I have my settings a little too high + what is too high? My sim runns nicely at ~50-60fps, I have tons of VAS left and I was plowing along in 35000ft in cruise over Africa - not really a very demanding scenery when my crash happened.

 

Others are receiving the crash over the Atlantic - also not really a demanding scenery for the terrain engine.

 

And to say - not many are getting this crash - well, maybe not too many are flying the long range flights yet on FSX:SE, and the ones that do try, get the error and change back to other options like FSX box or P3D (like me), and just stop bothering with FSX:SE.......

 

So for me, the only one who needs to change something is DT and/or MS. They need to fix that bug!

 

P.S.: I don't think it has anything to do with the UiAutomationcore.dll, because my crashes happened without any Menu interaction......

 

kind regards

Well Gentlemen,

 

I also receive this terrain.dll crash in FSX:SE, With a plain vanilla install and the FSX 747 after about 4-5 hrs of flight. 

(tested that one last night)

 

Yes, maybe I could avoid that by setting my settings lower (havent tried) but then again - If I need to lower my settings already in a plain vanilla install - what do I need to install FSGlobal mesh etc. then if I can't even have FSX's native 38m mesh display at highest settings? + FSX boxed never had that crash on my system, with a lot more demanding scenery installed and FSGlobal set to full right.

 

And except of that - the sim should not crash - only because I have my settings a little too high + what is too high? My sim runns nicely at ~50-60fps, I have tons of VAS left and I was plowing along in 35000ft in cruise over Africa - not really a very demanding scenery when my crash happened.

 

Others are receiving the crash over the Atlantic - also not really a demanding scenery for the terrain engine.

 

And to say - not many are getting this crash - well, maybe not too many are flying the long range flights yet on FSX:SE, and the ones that do try, get the error and change back to other options like FSX box or P3D (like me), and just stop bothering with FSX:SE.......

 

So for me, the only one who needs to change something is DT and/or MS. They need to fix that bug!

 

P.S.: I don't think it has anything to do with the UiAutomationcore.dll, because my crashes happened without any Menu interaction......

 

kind regards

For me I don't have options. I'm running Win8.1 and going back to Win7 is a pain. FSX boxed crashes on Win8.1. So I'm pretty much stuck in between.

For me I don't have options. I'm running Win8.1 and going back to Win7 is a pain. FSX boxed crashes on Win8.1. So I'm pretty much stuck in between.

 

Well my friend - that makes me really feel sorry for you - anyhow - I'm in a somewhat similar situation........ Yes, I do have alternatives, however - 

 

FSX:SE is crashing with terrain.dll....... and sometimes (if orbx is installed) with g3d.dll.......... which means I'll have to wait until DT patches these bugs... and ORBX will update their products for SE.....

 

FSE:MS - runns nicely, except the VAS problem.......

 

P3Dv2.4 - runns nicely - however no PMDG at this moment and v2.5 on the comming meaning many addons might be incompatible for some time to come........... they are going to change something in the folder structure......+ it means a fresh install.....and who knows how it will run in regards to VAS with PMDG coming to town.....

 

Anyhow - the future looks bright - only the present is a little depressing in the FS World.....(Happy to have another life!)

 

regards

I think we can start concluding that the terrain.dll will yield a CTD 4-5 hours into any flight, and that it is not scenery dependent.

As someone who has installed FSX-SE side-by-side, I never had a terrain.dll CTD in FSX-MS. I may have had OOM when deep into an 8 hour+flight.

 

With a PMDG aircraft----and only the ones that they have approved to used in FSX-SE----I get no OOM CTDs but get that terrain.dll with one hour remaining in North America. I did have my scenery sliders maxed, so that could have led to the CTD, so I have opted for default settings. I have not flown another long trans-Atlantic flight, so have no follow-up observations re:that terrain.dll manifesting itself again.

 

Windows 7 Pro 64-bit 4.2Ghz.

I think we can start concluding that the terrain.dll will yield a CTD 4-5 hours into any flight, and that it is not scenery dependent.

I'm tempted to load a complex aircraft in FSX-SE on an airport terminal ramp, running on external power, fully programmed with route and performance data, and then just leave it sit there, with the sim running for several hours.

 

I'm curious if the terrain.dll crash might pop up after 4-5 hours of continuous running, even if the aircraft never actually takes off and flies anywhere.

I'm tempted to load a complex aircraft in FSX-SE on an airport terminal ramp, running on external power, fully programmed with route and performance data, and then just leave it sit there, with the sim running for several hours.

 

I'm curious if the terrain.dll crash might pop up after 4-5 hours of continuous running, even if the aircraft never actually takes off and flies anywhere.

 

That might be worth a try, please go ahead and report back.... would be good info...

I think we can start concluding that the terrain.dll will yield a CTD 4-5 hours into any flight, and that it is not scenery dependent.

I get these crashes at fixed intervals, but the timing is highly dependent on where I fly and what aircraft that I am flying. I think that firehawk has this CTD figured out correctly in that FSX-SE will not run stable on some systems without the IQ settings turned down a bit.

So I did another test with lower autogen settings and mesh detail. No AI. No tweaks. This configuration was suggested by a few others. I flew westbound over the Atlantic EGLL-KORD. I took a more southerly route than normal, probably 300-400 miles south of Greenland overall, due to the winds aloft being favorable to the south.

 

I made it across the Atlantic and got about 20 miles inland into northern Canada before I experienced a g3d.dll and terrain.dll crash once more. VAS usage was about 2.3 GB. Once again, I experienced it around four hours and thirty minutes after loading up the sim. It's always around 4 1/2 hours into a flight. Why?! WHY!?! WHHHYYYYYY?!

 

(Yoda voice): So weird, this CTD.

So I did another test with lower autogen settings and mesh detail. No AI. No tweaks. This configuration was suggested by a few others. I flew westbound over the Atlantic EGLL-KORD. I took a more southerly route than normal, probably 300-400 miles south of Greenland overall, due to the winds aloft being favorable to the south.

 

I made it across the Atlantic and got about 20 miles inland into northern Canada before I experienced a g3d.dll and terrain.dll crash once more. VAS usage was about 2.3 GB. Once again, I experienced it around four hours and thirty minutes after loading up the sim. It's always around 4 1/2 hours into a flight. Why?! WHY!?! WHHHYYYYYY?!

 

(Yoda voice): So weird, this CTD.

 

 

Precisely the same experiences, more or less same routing, and always just within Canada's northern borders. It is so damned frustrating. Personally, IMHO, I think this particular sim is a ******!!! It stays grounded until somebody at DT finds a solution.

So I did another test with lower autogen settings and mesh detail. No AI. No tweaks. This configuration was suggested by a few others. I flew westbound over the Atlantic EGLL-KORD. I took a more southerly route than normal, probably 300-400 miles south of Greenland overall, due to the winds aloft being favorable to the south.

 

I made it across the Atlantic and got about 20 miles inland into northern Canada before I experienced a g3d.dll and terrain.dll crash once more. VAS usage was about 2.3 GB. Once again, I experienced it around four hours and thirty minutes after loading up the sim. It's always around 4 1/2 hours into a flight. Why?! WHY!?! WHHHYYYYYY?!

 

(Yoda voice): So weird, this CTD.

 

Well, Gentlemen - same experience here ~4 hrs flight - only for me it was over Africa - 1x PMDG 777; 1X vanilla FSX:SE / Boeing 747 (original, (what a cr*p plane) so its not a specific location..........1st flight was recorded with FSFlight Keeper, 2nd flight (747, vanilla SE install) was same route, only tracked by orig. GPS - crash in same area (~same time) but location wise not on the same spot.........

 

Funnily FSFlight Keeper recorded a flight time (from T/O) of  exactly 04:00 hrs.....

 

Personally, IMHO, I think this particular sim is a ******!!! It stays grounded until somebody at DT finds a solution.

 

+1

 

regards

 

P.S: Could you guy's maybe check if your Flight Time also matches those exact 04:00 hrs??? (from T/O to sim crash)

At first I thought that there might be a bug in the terrain in the area of southern Greenland, or along the eastern reaches of Labrador, but I think that most of us have had crashes in this specific area only because on a typical day, in a typical Mach .78 to Mach .82 airliner, it takes just about 4 to 4.5 hours to arrive in this area after departing westbound from the UK or other airports in Western Europe.

 

I had my first standalone G3D crash yesterday on a flight in the Aerosoft A319 heading to Orlando from Trenton, NJ. My FP was direct to STOEN from KTTN, thence J75 to CAE. I had the crash twice, just after STOEN, about 10 minutes after takeoff. (Which is to say that I flew the flight twice, and CTD with G3D in the same location).

 

I know that some people have reported a decrease in G3D crashes with Bojote's tweaks, but I did not want to apply those tweaks "wholesale" to my config, as many of them are somewhat outdated. I did manually add one change in FSX.cfg entering MaxTextureLoad = 3, a downgrade of the FSX default value of 6.

 

This did indeed prevent the G3D Crash on the third repeat of my KTTN-KMCO flight.

At first I thought that there might be a bug in the terrain in the area of southern Greenland, or along the eastern reaches of Labrador, but I think that most of us have had crashes in this specific area only because on a typical day, in a typical Mach .78 to Mach .82 airliner, it takes just about 4 to 4.5 hours to arrive in this area after departing westbound from the UK or other airports in Western Europe.

 

I had my first standalone G3D crash yesterday on a flight in the Aerosoft A319 heading to Orlando from Trenton, NJ. My FP was direct to STOEN from KTTN, thence J75 to CAE. I had the crash twice, just after STOEN, about 10 minutes after takeoff. (Which is to say that I flew the flight twice, and CTD with G3D in the same location).

 

I know that some people have reported a decrease in G3D crashes with Bojote's tweaks, but I did not want to apply those tweaks "wholesale" to my config, as many of them are somewhat outdated. I did manually add one change in FSX.cfg entering MaxTextureLoad = 3, a downgrade of the FSX default value of 6.

 

This did indeed prevent the G3D Crash on the third repeat of my KTTN-KMCO flight.

 

I've reported enhanced stability with Bojote's tweaks, but now I'm not so sure. My crash frequency seems to be going back to normal :(

 

Just for the record, while the majority of my flights are transatlantic, I've gotten crashes near Indonesia and Turkey, All about 4-5 hours into the flight. I haven't really done any transcon flights though.

 

 

I made it across the Atlantic and got about 20 miles inland into northern Canada before I experienced a g3d.dll and terrain.dll crash once more. VAS usage was about 2.3 GB. Once again, I experienced it around four hours and thirty minutes after loading up the sim. It's always around 4 1/2 hours into a flight. Why?! WHY!?! WHHHYYYYYY?!

Well in my case, it was from CYUL to LFPG, terrain.dll and g3d.dll crash after 4 hours as well near Ireland.  I only had ORBX Global and Vector, FSGenesis mesh and PMDG777-200.  I happened to still have FSX (box), also with Global and Vector only and redid the the flight with no issue.

I think Dovetail is aware of the issue. Please see my post here...

http://forum.avsim.net/topic/460411-an-impressive-fsx-se-report/?p=3168900