Didn't see a forum for FSNav legacy products or the newer FSTramp for FSX, so I'm asking this here.

 

I get a CTD every time I run FSTramp in both full screen and windowed mode.

It always lists terrain.dll as the faulty module.

I know others had this issue from the other the thread (which is dead) but wondered if anyone managed to solve it on their own.

 

I emailed the developer and he told me it's because of unstable overclocked hardware...well I don't overclock anything and my system is stable as a rock.

I have yet to hear back from him after telling him that.

 

Any user fixes out there? I can't even run the trial.

Anyone else try contacting the developer?

This is an automatic message.

 

This topic has been moved from "MS FSX Forum" to "Crash To Desktop (CTD) Forum". This move has been done for a number of possible reasons.

• The most likely reason is that the post was off topic.
  
• The topic could also have contained images or a video that were not appropriate to the original forum it was posted in.
  
• The images might not have been "illustrative" or "explanatory" in nature.
  
• The topic could have been moved because we deemed it to be more appropriately placed elsewhere.
  

Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums.

 

Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated.

It's possible your dll.xml file collocated with your fsx.cfg file became corrupted when your trial number of uses ended. That seems to be the time I had this problem, and every addon I tried to open that had .xml code would crash.

 

About the same time my trial period FStramp ended, I had loaded and unloaded another .xml code using fsx program, so that also may have been a culprit -I can't verify which did the damage. I'm sure it was one or the other. In any case, xml addons seem to add an entry into the dll.xml file so the xml code is initialized once you load that addon. It seems most of those xml related addons will leave a backup, renamed copy of dll.xml so you can revert if you have a problem. So look in the same folder as your fsx.cfg, and see if you can find an older dll.xml file you can revert to - see if that resolves your problem.

Ok thanks. I'll have a look, but I didn't run out of my trial uses for FSTramp yet.

I've double checked my dll.xml file and the pathname for FSTramp goes to the correct place.

What's really weird is that for the first 2 or 3 times I tried the trial, it worked fine. After a week of work I tried it again on the weekend and then this started happening. I didn't install anything new. Nothing changed with FSX.

According to the flight sim community, the terrain.dll crash is most likely caused by having your sliders set too high in FSX. Go into the fsx settings page and save your current configuration -- name it something like My Fsx config number one. Now go into the customize pages and in the scenery tab, click on restore defaults. Go Fly and see if this didn't fix your problem. If not, then go to the AI tab and restore defaults there and then Go Fly. If the problem still exists, then you have a computer system problem. If you computer is overclocked, you'll need to reduce the overclock. Also check your installed memory and make sure it is configured properly in the BIOS. Download and install CPU-Z if you haven't already then look under the SPD tab. Your timings, frequencies, and voltages must be the same as shown in one of the columns in the SPD tab. If you have your memory settings set to Auto, change to one of the configurations shown in the CPU-Z SPD tab.

 

Best regards,

Jim

Jim with all respect you didn't read my original post. I don't overclock anything and my system is completely stable. I have the correct memory and it's configured correctly in the BIOS.

I run FSX no problem with my sliders where they are. It's ONLY when I run FSTramp that I get a CTD and it lists terrain.dll as the culprit module.

 

There are two other threads floating in the MSFSX general forums about FSTramp, and multiple people have reported the same thing; they can't run the trial of FSTramp because it crashes FSX.

My system is fine, it's the developer's software that is faulty here, and he has refused to answer my emails asking him for help to help troubleshoot the problem.

Jim with all respect you didn't read my original post. I don't overclock anything and my system is completely stable. I have the correct memory and it's configured correctly in the BIOS.

I run FSX no problem with my sliders where they are.

 

Respectfully I did read your OP when it was first posted several days ago. I was just stating "IF" you overclock and providing you other suggestions. Via a Google search I did not see any problems between FS Tramp and terrain.dll. I still think you have a memory issue or a configuration problem in your BIOS (CPU voltage too high or too low) as these are the known solutions to terrain.dll CTD's. Virtual memory configurations has also produced this error and, as I mentioned above, your fsx settings may be set too high. You could also have a bad 'tweak' in your fsx.cfg.

 

I can understand why the FS Tramp developer has refused to respond to your e-mails. People are trying to help you but you refuse to believe anything they are saying as you already know what the problem is. That's not going to get you anywhere....

 

Respectfully,

Jim Young

The software is fairly new so I wouldn't be surprised that a solution isn't published yet.

Even so, I did lower my sliders and I still got the error.

 

As for my hardware/settings, before I installed FSTramp I had zero problems with terrain.dll. I have run REX, AS2012, FSCommander, FSWidgets GMAP, and countless other addons on my FSX machine. None of them has ever given me a terrain.dll error.

None of the aircraft I own from PMDG give it, or Level-D, or Captain Sim. FsDreamteam sceneries that I have don't give it, or FSDT's GSX software either.

 

Over 20 different types of 3rd party addons have run on my FSX machine but not once have I gotten a terrain.dll crash until I tried to run the trial of FSTramp, which unlike anything else I've used runs as a module within FSX instead of externally.

Also, I already use CPU-Z and all my memory freqs and timings are correct. I build my own computers so I make sure that everything is installed, configured, and set up correctly with compatible hardware.

 

As for the developer, how can you say you completely understand why he hasn't emailed me back? Every email I sent the developer was polite and respectful. The ONLY answer he gave me in the beginning was that I had overclocked hardware that I needed to tune down.

As said multiple times I have ZERO overclocked hardware. I told him this and he has ignored me since, as if he doesn't want to deal with any alternate solutions.

 

Saying I refuse to believe anything is a bit of an exaggeration. I checked my dll.xml file has suggested earlier and thanked that person for their help. I tried your suggestions and I'm still getting the error.

In the end, I think it's ridiculous that out of the 20+ addons I run, I haven't had a single problem but as soon as this software gives me the error somehow it's a hardware problem with my memory timing.

Doesn't make sense.

I feel your pain...I too am having the exact same issue. Unfortunately it appears that this is just one of those times where for whatever reason there is an unknown incompatibility with an application and certain systems/setups and where the author has not been able to find a cause/resolution (again, for whatever reason).

 

I too received the same response from the dev and had zero luck even after turning off the overclocking on my SandyBridge setup (which by the way has also not given me any crashes in any addons in fsx nor any other apps/games until i try to call up fstramp).

 

Frustrating isn't it...the responses you get sometimes (or lack of)?

 

When cases like this come up once in a few years (where you know your system is running everything else ok but cant get support on a specific app issue) I simply don't bother with the new app. I delete it and never look back...which is what I have done in this matter. If the dev doesn't care then why should we?

Just an update, I tried reinstalling (again) FSTramp, and on the first try it CTD'd but it listed FSX.exe as the focus, not terrain.dll.

There is something very, very wrong with this software and an incompatibility with something else.

 

Too bad the developer refuses to try and help find it.

Thanks to the help of someone from the other thread, the problem was the FXAA shading injector I had forgotten I installed shortly after installing the FSTramp trial.

 

Uninstalling the dx9 files from the mod let FSTramp start with no problems. In the end it was a compatibility problem with another mod, and had nothing to do with overclocked hardware or memory timings.

Hey! Great news! Glad you found a fix. I figured it had to be something else other than an issue with FSTramp. It's amazing how many things can bring down FSX. Wish there was a way to pinpoint every error but unfortunately there is not. I just make suggestions to people who are having issues and hope my suggestions work. This is the first time I have heard of the FXAA shading injector causing a problem. I think that was a replacement for the ENB Series Mod which caused a lot of crashes too. I'll have to remember that!

 

Best regards,

Jim Young