Jump to content
The simFlight Network Forums

Its official - Pete Dawson Fixed Terrain.DLL crashes


Recommended Posts

Just wanted to report that I have not been able to complete a 4+ hour flight without a crash since moving to FSX Steam Edition, but with the latest FSUIPC patch that was intended to fix the G3D.dll crash, he has also captured the Terrain.DLL crash. I have completed 3 separate flights which were 7 hours, 12 hours, and 6 hours without the crash. THANK YOU PETE! 

Link to comment
Share on other sites

I have suffered from this issue also. Can you please provide the exact procedures you used to resolve the issue. I downloaded and installed FSUIPC4, Version 4.939 but I still have terrain.dll exactly at about the 5th hour in flight every time, regardless of where I'm flying to. Can you confirm in your FSUIPC logs that the terrain.dll error has been captured?

 

Also Jordan thanks for the YouTube videos. Your videos are awesome! Keep up the good work.

Link to comment
Share on other sites

I have suffered from this issue also. Can you please provide the exact procedures you used to resolve the issue. I downloaded and installed FSUIPC4, Version 4.939 but I still have terrain.dll exactly at about the 5th hour in flight every time, regardless of where I'm flying to. Can you confirm in your FSUIPC logs that the terrain.dll error has been captured?

 

Also Jordan thanks for the YouTube videos. Your videos are awesome! Keep up the good work.

 

The G3D crash trapped by FSUIPC is just one of many different ones which plague FSX in general. It just happened to be the most common one and the only one easy to patch around.

 

The optional Terrain.DLL patch I put in for FSX-SE only did not sem to work so well so hasn't been continued. And it was only one specific crash out of several I've seen reported.

 

What Jordan seems to be saying is that the G3D fix I added seems to also fix the specific Terrain problem he was having -- which might be different to yours in any case.

 

Pete

Link to comment
Share on other sites

Just out of curiosity, I decided to perform one more test. KDTW->SBGR, this is approx. 10 hour flight. Around the 5th hour I got this error as usual.

 

Faulting application name: fsx.exe, version: 10.0.62608.0, time stamp: 0x54abe5b4

Faulting module name: terrain.dll, version: 10.0.62608.0, time stamp: 0x54abe5e1

Exception code: 0xc0000005

Fault offset: 0x00059be8

Faulting process id: 0xcb4

Faulting application start time: 0x01d053648e2b9558

Faulting application path: C:\Steam\steamapps\common\FSX\fsx.exe

Faulting module path: C:\Steam\steamapps\common\FSX\terrain.dll

Report Id: bfe04fd7-bf86-11e4-afb4-bc5ff4fcf0a1

 

Next I took a look at the FSUIPC logs and I did notice that several g3d.dll errors were captured, however I did not see anything being captured for terrain.dll

 

This bug is very frustrating. I've had a few email exchanges with DTG in regards to this problem. They are aware of it and they have assured me that this is a high priority fix. They suggested running the steam verification on my FSX-SE installation. That was one of the first things that I did several weeks ago, but that doesn't fix anything.

 

Is it possible to trap this terrain.dll error offset in FSUIPC?

 

********* FSUIPC4, Version 4.939 by Pete Dowson *********
Reading options from "C:\Steam\steamapps\common\FSX\Modules\FSUIPC4.ini"
Running inside FSX Steam Edition on Windows 7
Module base=617C0000
User Name="REDACTED"
User Addr="REDACTED"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 28/02/2015 09:42:47
        0 FLT path = "C:\Users\REDACTED\Documents\Flight Simulator X Files\"
       31 Trying to connect to SimConnect Steam ...
       62 FS path = "C:\Steam\steamapps\common\FSX\"
      328 LogOptions=00000000 00000001
      328 SIM1 Frictions access gained
      328 Wind smoothing fix is fully installed
      328 G3D.DLL fix attempt installed ok
      328 SimConnect_Open succeeded: waiting to check version okay
      328 Trying to use SimConnect Steam
     2418 Running in "Microsoft Flight Simulator X", Version: 10.0.62608.0 (SimConnect: 10.0.62608.0)
     2418 Initialising SimConnect data requests now
     2418 FSUIPC Menu entry added
     2449 FLIGHTS\OTHER\FLTSIM.FLT
     2449 simobjects\airplanes\Aircreation_582SL\Aircreation_582SL.AIR
    80060 simobjects\airplanes\PMDG 777-200LR\B777-200LR.AIR
   168855 System time = 28/02/2015 09:45:36, Simulator time = 09:42:49 (17:42Z)
   168855 Aircraft="PMDG 777-232LR Delta Air Lines"
   172397 Weather Mode now = Theme
   192131 Sim stopped: average frame rate for last 23 secs = 45.0 fps
   200992 Starting everything now ...
   202458 ASN active function link set
   202458 Ready for ASN WX radar
   202489 Advanced Weather Interface Enabled
   262113 Sim stopped: average frame rate for last 64 secs = 31.8 fps
   269850 C:\Users\jweston\AppData\Roaming\Microsoft\FSX\Previous flight.FLT
  1860327 Sim stopped: average frame rate for last 1218 secs = 27.0 fps
  2933786 *** G3D bad pointer trapped and crash prevented ***
  2935923 *** G3D bad pointer trapped and crash prevented ***
  3080567 Sim stopped: average frame rate for last 1219 secs = 22.8 fps
  4330135 *** G3D bad pointer trapped and crash prevented ***
  5892641 *** G3D bad pointer trapped and crash prevented ***
  6561527 *** G3D bad pointer trapped and crash prevented ***
  6737652 Sim stopped: average frame rate for last 3656 secs = 24.6 fps
 11003827 Sim stopped: average frame rate for last 4265 secs = 24.8 fps
 14657838 Sim stopped: average frame rate for last 3654 secs = 28.4 fps
 18923030 Sim stopped: average frame rate for last 4264 secs = 26.8 fps

 

Link to comment
Share on other sites

Just out of curiosity, I decided to perform one more test. KDTW->SBGR, this is approx. 10 hour flight. Around the 5th hour I got this error as usual.

 

Faulting application name: fsx.exe, version: 10.0.62608.0, time stamp: 0x54abe5b4

Faulting module name: terrain.dll, version: 10.0.62608.0, time stamp: 0x54abe5e1

Exception code: 0xc0000005

Fault offset: 0x00059be8

Faulting process id: 0xcb4

Faulting application start time: 0x01d053648e2b9558

Faulting application path: C:\Steam\steamapps\common\FSX\fsx.exe

Faulting module path: C:\Steam\steamapps\common\FSX\terrain.dll

Report Id: bfe04fd7-bf86-11e4-afb4-bc5ff4fcf0a1

 

Next I took a look at the FSUIPC logs and I did notice that several g3d.dll errors were captured, however I did not see anything being captured for terrain.dll

 

At present FSUIPC (registered only) will only even attempt to trap one specific Terrain crash the option is selected. I had planned to remove that option, as I thought it not working, but if you want to try it you need to set 

 

SteamTerrainPatch=Yes

 

in the [General] section of FSUIPC4.INI before starting FSX-SE.

 

If this does help, let me know, and I'll default it on as for the G3D trap.

 

Pete

Link to comment
Share on other sites

At present FSUIPC (registered only) will only even attempt to trap one specific Terrain crash the option is selected. I had planned to remove that option, as I thought it not working, but if you want to try it you need to set 

 

SteamTerrainPatch=Yes

 

in the [General] section of FSUIPC4.INI before starting FSX-SE.

 

If this does help, let me know, and I'll default it on as for the G3D trap.

 

Pete

Hello Pete

 

I will add that to my .ini file and try my test scenario again.

 

Thanks

Jamal

Link to comment
Share on other sites

I tried another test scenario. KDTW->SBGR, which is about a 10 hour flight using the SteamTerrainPatch=Yes fix, but looks like it does not catch the error like is done with the gd3.dll. My last flight crashed 5 hours and 28 minutes into the flight with terrain.dll error.

 

It's unfortunate as it seems like this terrain.dll error will never be fixed. Still holding out for DTG to come up with something, but another week gone by and still no news.

 

 

Faulting application name: fsx.exe, version: 10.0.62608.0, time stamp: 0x54abe5b4

Faulting module name: terrain.dll, version: 10.0.62608.0, time stamp: 0x54abe5e1

Exception code: 0xc0000005

Fault offset: 0x00059be8

Faulting process id: 0x11bc

Faulting application start time: 0x01d053be155d9fb2

Faulting application path: C:\Steam\steamapps\common\FSX\fsx.exe

Faulting module path: C:\Steam\steamapps\common\FSX\terrain.dll

Report Id: 312c7be4-bfe2-11e4-9ee8-bc5ff4fcf0a1

 

********* FSUIPC4, Version 4.939 by Pete Dowson *********
Reading options from "C:\Steam\steamapps\common\FSX\Modules\FSUIPC4.ini"
Running inside FSX Steam Edition on Windows 7
Module base=1DB60000
User Name="REDACTED"
User Addr="REDACTED"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
       62 System time = 28/02/2015 20:25:13
       62 FLT path = "C:\Users\jweston\Documents\Flight Simulator X Files\"
     1092 Trying to connect to SimConnect Steam ...
     1154 FS path = "C:\Steam\steamapps\common\FSX\"
     1419 LogOptions=00000000 00000001
     1419 SIM1 Frictions access gained
     1419 Wind smoothing fix is fully installed
     1419 G3D.DLL fix attempt installed ok
     1419 TERRAIN.DLL fix attempt installed ok
     1419 SimConnect_Open succeeded: waiting to check version okay
     1419 Trying to use SimConnect Steam
    10296 Running in "Microsoft Flight Simulator X", Version: 10.0.62608.0 (SimConnect: 10.0.62608.0)
    10296 Initialising SimConnect data requests now
    10296 FSUIPC Menu entry added
    10452 FLIGHTS\OTHER\FLTSIM.FLT
    10452 simobjects\airplanes\Aircreation_582SL\Aircreation_582SL.AIR
    36223 simobjects\airplanes\PMDG 777-200LR\B777-200LR.AIR
   173395 System time = 28/02/2015 20:28:06, Simulator time = 23:25:22 (04:25Z)
   173395 Aircraft="PMDG 777-232LR Delta Air Lines"
   205219 Starting everything now ...
   205468 ASN active function link set
   205468 Ready for ASN WX radar
   206358 Weather Mode now = Theme
   206467 Advanced Weather Interface Enabled
  3411414 *** G3D bad pointer trapped and crash prevented ***
 19081246 Sim stopped: average frame rate for last 18882 secs = 31.9 fps

 

Link to comment
Share on other sites

I tried another test scenario. KDTW->SBGR, which is about a 10 hour flight using the SteamTerrainPatch=Yes fix, but looks like it does not catch the error like is done with the gd3.dll. My last flight crashed 5 hours and 28 minutes into the flight with terrain.dll error.

 

It's unfortunate as it seems like this terrain.dll error will never be fixed. Still holding out for DTG to come up with something, but another week gone by and still no news.

 

 

Faulting application name: fsx.exe, version: 10.0.62608.0, time stamp: 0x54abe5b4

Faulting module name: terrain.dll, version: 10.0.62608.0, time stamp: 0x54abe5e1

Exception code: 0xc0000005

Fault offset: 0x00059be8

 

Hmm. That is the location of the Terrain error I was trying to plug, so your results confirm to me that it doesn't work.

 

I might have another look at that area to see if I can understand why, but meanwhile, yes, please make sure DTG have the details of this one -- yours does seem consistent. I know they said they were looking at it, we want to make sure they are looking in the right place.

 

Pete

Link to comment
Share on other sites

Hmm. That is the location of the Terrain error I was trying to plug, so your results confirm to me that it doesn't work.

 

I might have another look at that area to see if I can understand why, but meanwhile, yes, please make sure DTG have the details of this one -- yours does seem consistent. I know they said they were looking at it, we want to make sure they are looking in the right place.

 

Pete

All of my terrain.dll errors are at that memory location. Typically 5 hours is my limit before the crash. I never had this problem in the classic version, but then again my boxed version was Deluxe and not the Gold Edition.

 

The G3D.dll error is defiantly fixed. I have not seen that error again since the last version of FSUIPC was released.

 

If you come up with any ideas, let me know and I will be happy to run my test scenario. I can reproduce this defect consistently regardless of the route I fly, as long as it is more than 5 hours.

 

Thanks

Jamal

Link to comment
Share on other sites

If you come up with any ideas, let me know and I will be happy to run my test scenario. I can reproduce this defect consistently regardless of the route I fly, as long as it is more than 5 hours.

 

I've worked on this a bit more and have come up with a different work-around for that one specific Terrain.dll crash. The problem is I don't know whether it'll fix it or just move the error elsewhere. Perhaps you could test it please? Download

 

FSUIPC4939e_test.zip

 

and just copy the FSUIPC4.DLL into your FSX Modules folder. It doesn't need any parameters, it is just automatically applied, like the G3D fix is.

 

If you don't get the crash, please let me see the log after you've closed FS with a successful session. If it does crash, let me see the crash details, please.

 

I know that DoveTail are working on fixes for these crashes, so my interventions may not be needed for these much longer. We'll see ... ;-)

 

Pete

Link to comment
Share on other sites

I've worked on this a bit more and have come up with a different work-around for that one specific Terrain.dll crash. The problem is I don't know whether it'll fix it or just move the error elsewhere. Perhaps you could test it please? Download

 

FSUIPC4939e_test.zip

 

and just copy the FSUIPC4.DLL into your FSX Modules folder. It doesn't need any parameters, it is just automatically applied, like the G3D fix is.

 

If you don't get the crash, please let me see the log after you've closed FS with a successful session. If it does crash, let me see the crash details, please.

 

I know that DoveTail are working on fixes for these crashes, so my interventions may not be needed for these much longer. We'll see ... ;-)

 

Pete

Hello Pete

 

I will setup a long rang test flight today and post my results. Thanks for looking into this.

 

Jamal

Link to comment
Share on other sites

Below are my test results using version 4939e. I noticed in the logs a terrain.dll error was captured. However I got a crash at 5 hours and 32 minutes into the flight from another memory location with terrain.dll. The sim stops in the log are okay, it's just FS RealTime updating itself.

 

FSUIPC4939e test results

 

Faulting application name: fsx.exe, version: 10.0.62608.0, time stamp: 0x54abe5b4

Faulting module name: terrain.dll, version: 10.0.62608.0, time stamp: 0x54abe5e1

Exception code: 0xc0000005

Fault offset: 0x00057902

Faulting process id: 0x1498

Faulting application start time: 0x01d0553c36768fd3

Faulting application path: C:\Steam\steamapps\common\FSX\fsx.exe

Faulting module path: C:\Steam\steamapps\common\FSX\terrain.dll

Report Id: b5ada034-c15f-11e4-9490-bc5ff4fcf0a1

 

 

********* FSUIPC4, Version 4.939e by Pete Dowson *********
Reading options from "C:\Steam\steamapps\common\FSX\Modules\FSUIPC4.ini"
Running inside FSX Steam Edition on Windows 7
Module base=63410000
User Name="Jamal Weston"
User Addr="********@*******.***"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
       16 System time = 02/03/2015 17:58:02
       16 FLT path = "C:\Users\jweston\Documents\Flight Simulator X Files\"
       32 Trying to connect to SimConnect Steam ...
       47 FS path = "C:\Steam\steamapps\common\FSX\"
      312 LogOptions=00000000 00000001
      312 --- CONTROLS timer memory location obtained ok
      312 --- SIM1 Frictions access gained
      312 --- FS Controls Table located ok
      312 --- Installed Mouse Macro hooks ok.
      312 --- Wind smoothing fix is fully installed
      312 --- G3D.DLL fix attempt installed ok
      312 --- TERRAIN.DLL fix attempt installed ok
      312 SimConnect_Open succeeded: waiting to check version okay
      312 Trying to use SimConnect Steam
      952 Running in "Microsoft Flight Simulator X", Version: 10.0.62608.0 (SimConnect: 10.0.62608.0)
      952 Initialising SimConnect data requests now
      952 FSUIPC Menu entry added
      983 FLIGHTS\OTHER\FLTSIM.FLT
      983 simobjects\airplanes\Aircreation_582SL\Aircreation_582SL.AIR
    20982 simobjects\airplanes\PMDG 777-200LR\B777-200LR.AIR
    76924 Aircraft="PMDG 777-232LR Delta Air Lines"
    76924 System time = 02/03/2015 17:59:19, Simulator time = 20:58:02 (01:58Z)
    99841 Starting everything now ...
   101822 ASN active function link set
   101822 Ready for ASN WX radar
   103273 Advanced Weather Interface Enabled
   105176 Weather Mode now = Theme
  1315947 Sim stopped: average frame rate for last 1218 secs = 28.1 fps
  2275852 *** G3D bad pointer trapped and crash prevented ***
  4971830 Sim stopped: average frame rate for last 3655 secs = 27.2 fps
  5498022 *** G3D bad pointer trapped and crash prevented ***
  5501422 *** G3D bad pointer trapped and crash prevented ***
  9234370 Sim stopped: average frame rate for last 4261 secs = 32.3 fps
 13496442 Sim stopped: average frame rate for last 4262 secs = 35.3 fps
 16373709 Sim stopped: average frame rate for last 2877 secs = 32.6 fps
 16417218 Sim stopped: average frame rate for last 34 secs = 27.5 fps
 17034717 Sim stopped: average frame rate for last 609 secs = 33.2 fps
 20605689 *** TERRAIN bad pointer trapped and crash prevented ***

 

Link to comment
Share on other sites

Below are my test results using version 4939e. I noticed in the logs a terrain.dll error was captured. However I got a crash at 5 hours and 32 minutes into the flight from another memory location with terrain.dll. Faulting module name: terrain.dll, version:

 

...

10.0.62608.0, time stamp: 0x54abe5e1

Exception code: 0xc0000005

Fault offset: 0x00057902

 

Hmm. it is as I feared. I'm tackling the symptom, not the cause.. All I've succeeded in doing is moving the site of the crash. Without being able to reproduce it here, I've really got no way of tracking the bad pointer back up the chain to tackle the source.

 

I definitely think these crashes (G3D and Terrain ones) are down to sceneries or aircraft graphics which are slightly bending the rules, taking advantage of things not documented for normal FS use. I have lots of add-on sceneries (but Europe only, I don't fly long distance), and no aircraft panels, and have never had either G3D or Terrain crashes in either FSX-MS or FSX-SE.

 

Your crash at 5hours 32mins must be really the same one  as this:

 

 20605689 *** TERRAIN bad pointer trapped and crash prevented ***

 

 

That time on the left is 5hours 43mins from FSUIPC starting up.

 

DoveTail are definitely working on all this. I will be leaving out both G3D and Terrain fixes in the FSUIPC4 version aimed at the next FSX-SE update, as they should have "fixed" both. We'll see. Won't be long now.

 

Pete

 

Link to comment
Share on other sites

 

Hmm. it is as I feared. I'm tackling the symptom, not the cause.. All I've succeeded in doing is moving the site of the crash. Without being able to reproduce it here, I've really got no way of tracking the bad pointer back up the chain to tackle the source.

 

I definitely think these crashes (G3D and Terrain ones) are down to sceneries or aircraft graphics which are slightly bending the rules, taking advantage of things not documented for normal FS use. I have lots of add-on sceneries (but Europe only, I don't fly long distance), and no aircraft panels, and have never had either G3D or Terrain crashes in either FSX-MS or FSX-SE.

 

Your crash at 5hours 32mins must be really the same one  as this:

 

 20605689 *** TERRAIN bad pointer trapped and crash prevented ***

 

 

That time on the left is 5hours 43mins from FSUIPC starting up.

 

DoveTail are definitely working on all this. I will be leaving out both G3D and Terrain fixes in the FSUIPC4 version aimed at the next FSX-SE update, as they should have "fixed" both. We'll see. Won't be long now.

 

Pete

 

 

Thanks for looking at the issue. I think I will park the long haul jets until this error is fixed by DTG.

 

The last e-mail response I got from DTG assured me that this issue is being looked at as a high priority, so hopefully a new build will be released soon.

 

Thanks

Jamal

Link to comment
Share on other sites

Thanks for looking at the issue. I think I will park the long haul jets until this error is fixed by DTG.

 

The last e-mail response I got from DTG assured me that this issue is being looked at as a high priority, so hopefully a new build will be released soon.

 

If you want to test the Beta of their next version, to make sure they've fixed this, send me an email and I'll give you the details. Apparently I'm allowed to do this, but only for specific purposes like this. petedowson@btconnect.com

 

Pete

Link to comment
Share on other sites

I have suffered from this issue also. Can you please provide the exact procedures you used to resolve the issue. I downloaded and installed FSUIPC4, Version 4.939 but I still have terrain.dll exactly at about the 5th hour in flight every time, regardless of where I'm flying to. Can you confirm in your FSUIPC logs that the terrain.dll error has been captured?

 

Also Jordan thanks for the YouTube videos. Your videos are awesome! Keep up the good work.

 

Hey Hadoken, sorry i forgot to follow up here on the forums. Sorry if I gave any false hope, I realize that the terrain.dll is a very complex thing and produces different errors for different folks. On my system it worked but I know on some other folks platforms it may not so well. I do see that the terrain.dll and g3d errors have be captures but I also installed night environment from Aerosoft and they produced a new issue. So during flights without night environment I am good but using it I have trouble occasionally. Also thanks for the kind words about my videos! 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.