www.nl-2000.com

Hi the NL 2000 team !

First thanks for this wonderfull scenery I have been using it for the past 2 years and it is great !

Now on to the problem:

FS2004
NL 2000 2.91
Other sceneries from FS france (http://www.fsfrance.com), LFLL, LFPO, LFPG
Extra scenery LFOT, and 2 AC carriers from http://joel.maillot.free.fr/fs2k2_Porte_avions1.html (the CDG in med & britany)

My scenery.cfg (onle extra scenes):
[Area.038]
Title=Addon Scenery
Active=TRUE
Layer=38
Local=Addon Scenery

[Area.039]
Title=NOVA * TEXTURES
Active=TRUE
Layer=39
Local=SceneDB\Nova

[Area.040]
Title=CDGBrest
Active=TRUE
Layer=40
Local=SceneDB\CDGBrest

[Area.041]
Title=CDGToulon
Active=TRUE
Layer=41
Local=SceneDB\CDGToulon

[Area.042]
Title=LFOT
Active=TRUE
Layer=42
Local=SceneDB\LFOT

[Area.043]
Title=LFPO
Active=TRUE
Layer=43
Local=SceneDB\LFPO

[Area.044]
Title=LFPG
Active=TRUE
Layer=44
Local=SceneDB\LFPG

[Area.045]
Title=LFLL
Active=TRUE
Layer=45
Local=SceneDB\LFLL


[Area.046]
Title=The Netherlands 2000 V2.91
Local=e:\Program Files\Microsoft Games\Flight Simulator 9\SceneDB\nl2000_V2_91
Active=TRUE
Layer=46

My problem is when I get around 10 000 ft coming from one of these airports or from germany for ex.

I always get handed to an ATC that was near my departure (i.e. Bricy, Cambrai etc...), then I get Amsterdam approach, and if miss the approach or declared a go around, I am also handed over to an ATC in France, this seem to happen for around EHAM, or any other NL 2000 airport.


I don't know what to do about this, it makes the whole experience very unrealistic ( Now I am checking from west (EGLL)

This sounds strange, but we have not changed anything in the ATC structure.

Does the problem also happen when you don't have NL2000 active?

I have tried to fly IFR from Berlin and London, the problem does not show up, I f I fly from Luxembourg (i.e. from the south and over belgium) I am also handed over to a french ATC in the order Brussels/Amsterdam/Bricy/Rotterdam. This occurs as I descend through 10000 ft.

I have also disabled the NL 2000 scenery in FS9, and the problem vanished. Looks like a bug. Can you try to reproduce this problem ?

Regards,


Eric

Eric, this has nothing to do with NL2000 I believe. This is a bug in FS9. It happens more frequently than just around Amsterdam. Once you get to know more ATC stations by their name, you will notice that also during approaches elsewhere this happens. And it already happened before I installed NL2000. I got used to it........


Menno

I do not understand then why on earth the problem would disapear, if I disable the NL 2000 scenery ? Why would this only happen when I fly in the NL ?

Hello all,

I still have the french ATC coming into play when I transition to 10000. Has anyone else reproduced this behaviour yet ?

I fly now IFR@FL28 from ELLX to EHAM (VOR to VOR in the FS9 flight planner), as I found out this bug could be reproduced 100% of the time using these parameters.


Now I have one further problem, which is being directed for a visual approach and landing to EHAM in the middle of the night, which I find very odd.

I I request another approach, the ATC instruct vectors to the new landing strip, with a circle to land on the initial visual strip.... Once I get there I still get a clearance to land visual on the initial ....

We are still working on the problems, in the Dutch discussion part there is a discussion going on about the AFCAD files and it seems some of them give some trouble (but not always, as the team can not reproduce most of the errors).

About the ATC problems, I think that is something in FS, in the ATC algorithm, that has nothing to do with our scenery.

Hello Arno,

First thanks for the very fast answer, about the aproaches to EHAM, may be it would be worth publishing the known bugs and problems on the web site, in english for us the non dutch speakers.


On the first issue, which is the ATC reverting to a departure aproach, I can open a ticket with Microsoft without a problem and I will get an answer (the company I work for is one of their biggest customer).

But the first question the tech is going to ask, is to remove NL 2000, and when I remove NL 2000, the ATC is correct (as mentioned earlier in the thread). So the guy will tell me that NL 2000 is the problem, he will close the case asking me to contact the NL 2000 team.

.... So what do we do now ? Looks like we are going to run into a dead end on this issue. Is there anything I could do to help further ?


Regards,


Eric.

But I think the problems you mention about going from VFR to IFR are not only related to EHAM, but could also happen when you did that switch somewhere else in the world. If I am not correct there, please let me know.

About the other bugs, as we are still searching and have not yet found a definate answer. So therefore we do not publish them yet, as we don't know what the bug exactly is.

For most users it seems that the EHSB AFCAD files gives most trouble (crashes etc), so maybe you could try if that file is also ruining the ATC?

FYI, I do not fly VFR, only IFR from takeoff to landing. No switch involved.


So ok, my next tries will be remove that BGL you mention. Second step try to reproduce the problem flying VFR from takeoff to landing, but using about the same altitudes, ans see if I also have the pb when I fly VFR.


Good night


Eric.

Hello,

I found several, should I remove EHSB*.BGL ?

Eric,
the afcad-file you should remove (temporarely, you might need him after all) is AF2NL2K29v1_EHSB.BGL.

Bert

I have removed and recompiled without this scene, no happyness here. Ok, I will do some more investigation (remove half of the BGL etc...), when I come back from my vacations, this means I will not have any oportunity to fly until mid september.


Eric.