www.nl-2000.com

Hi,

My Dutch being not so good , please allow me to post in Homer Simpson's language.

Here's my problem: I've succesfully managed to fly from Holland to other countries (France, UK) in Europe. But a flight TO Holland (I was trying a Cork,IE to Schiphol flight) resulted in a total crash of FS9 as soon as the add-on scenery would have to be loaded into the memory. Since I have quicksave.dll installed, I could repeat the crash everytime I could, trying different routes and altitudes and everytime it crashed at the exact same distance to the Dutch coastline.

I have installed all of Pietro Mauri's great Europe meshes as well as Belgium2000 and tons of more detailed sceneries for France.

NL2000 looks so great with a heck of a user interface that I really feel bad about posting bad news about this great - and free! - add-on.
But then it might just be a matter of settings within FS or the NL2K interface to have everything work smoothly.

Funny you mention it. I posted my problems with FS9 crashing to desktop in the Dutch forum the other day. I found that disabling the Mauri mesh of Germany (GERMANY 2004 SRTM MESH SCENERY Version 1.0, which covers parts of Holland as well) solved the problem for me. Just disabling it in the scenery library is enough.
Hope this helps, would very much like to hear if it does the trick for you too.

Cheers
AJ

I get the FS9 crash trying to fly into the Netherlands from the UK. I don't have any other European add-ons insatlled either!

Frustrating

Phil

Frustrating....to say the least
In the Dutch forum several "fixes" have come up that seem to work for some people. None of them did for me, until I disabled the Mauri mesh. Maybe one of these solutions works for you. They are:
- remove the NL2000_2.bgl, NL2000_3.bgl and NL2000_4.bgl from your nl2000_V2_91\scenery folder (cut and paste them to a folder on your desktop in case you want to put them back later).
- In Flight Simulator, set colors to 16 bit instead of 32 bit
- disable NL2000 navaids and AFCAD in the featurepanel.

Hope this helps
Cheers
AJ

PHAJH wrote:Frustrating....to say the least

- In Flight Simulator, set colors to 16 bit instead of 32 bit
AJ

Buhh!

Alternatively, wait for the next version...

...but none of the designers are experiencing the CTD's so I won't hold my breath waiting for an official fix.....

About the colours: you're right about that but then again...CTD's are not funny at all either

Cheers
AJ

Hi There!

I also found FS9 crashed at the real-live desktop when i flew from The Netherlands towards west/north-west (Shetlands, Norway), just a little past by the (Wadden) islands.

I've tried some features enabled/disabled in the Feature Panel and found out that when you disable FS2004 NAVAIDS and Afcad - FS2004 only FS9 stays stabiel and more important, on-air!

Althoug I'm not sure if this works for everyone who has encountered the same problems as mentioned above, so far it works for me.

However, when FS2004 NAVAIDS has been disabled, MSFS' original Afcadfiles will be used so the instruments, AI, etc, won't fit anymore

We don't have the same problems but we want of course to know what eactly is the problem, so we can create a fix.

Beside of the afcad files, you can also try to disable the altitude and enable afcad (although this is not something you want to do normally). But can you check if this solves the problem too?

I have posted this message at AVSIM and FlightSIM and found one other person is having a similar problem. Then I saw the post on crashing when flying towards Holland, so my conclusions may have some relevance:

Flying around Leeds/Bradford in the UK I kept getting a CTD when I activated the GPS; when I de-activated my AFCAD scenery folder the CTD disappeared.

So after much trial and error analysis, I found that the three modified files in NL2000 (AP948130; AP949120; AP949130) which were to be copied into the eurw\scenery folder, had also been inadvertently copied into the AFCAD scenery folder. I did a manual installation and so do not believe the fault is with the NL2000 installer.

When I removed these three files from my AFCAD scenery folder, the CTD disappeared, with our without the GPS. I am getting the sense that CTD’s are occurring with some kind of overload within the system, I have been able to trigger them before with the GPS and ATC but have usually found the specific culprit is elsewhere, usually a faulty AFCAD file.

Of particular interest is how far from Holland I was and that I had not been experiencing CTD’s elsewhere in the region.

Nigel
Vancouver

Well removing the nl2000
_3 etc bgls did not work for me.

I will try the others next.

I will say this - I was using GPS to control my flight each time this happened - I should maybe try one without too - though it all takes time!

Phil

johanc wrote:Beside of the afcad files, you can also try to disable the altitude and enable afcad (although this is not something you want to do normally). But can you check if this solves the problem too?

I did and also re-enabled Afcad, but same error occured. Something wrong within the afcadfiles?

AP948130; AP949120; AP949130 are the modified FS altitude files, because afcad 2.2x can't change the altitude of the fields like afcad 1.x could (so ai is hanging of digged into the ground).

Johan

In my setup, these three files were appearing in two locations - eurw and my AFCAD folder hence the conflict. When I removed them from the AFCAD folder this eliminated the CTD

Nigel

Nigel,

What do you mean with your afcad folder. Is this a folder you created yourself and is this folder defined in the scenery.cfg? Or is this the afcad folder in the featurepanel directory.

(I assume the first, but I want to be sure)

Instead of putting all my AFCAD files in AddonScenery, I create an AFCAD folder with a scenery folder and empty texture folder in it. I put all my AFCAD files in this scenery folder which makjes it a lot easier to isolate potentially corrupt AFCAD files (I also think this is quite common practice with simmers). Somehow those three AP files ended up in that scenery folder. I could well have inadvertently put them there but it is of interest to me that others are experiencing a similar CTD problem.

Nigel