FS crash at Wellington

[ZK-MAT]

Whenever I start a flight at NZWN anywhere other than on the runway the sim loads to about 50% 'loading terrain' then quits out. No error report.

I can start on the runway and slew to a gate ok. I don't have 'crashes' on so it's not a building clash issue.

Perhaps it's an afcad problem? I had a AF2_NZWN.bgl in addon scenerey/scenery that perhaps is an older one, however it works fine for the ILS etc.

I can't see a new Real NZ afcad either in addon scenery/scenery or in the RealNZWgtn folder. I removed the older afcad and on restarting the sim still have all the gates etc to choose from but it still wont load

Edit: I have just deleted a folder named NZWN from my add on scenery, which I think was an old version of the airport and not activated within FS, but by deleting it at least now I can start up at a gate. I have put that AF2_NZWN AFCAD back in as it has west and se parking options, and it appears to match up with the gates nicely, the 'no afcad' method places me in hills and inside buildings....

[toprob]

The AFCAD in Addon Scenery\scenery is hopefully mine. The airport would look noticably strange without it, as it defines many taxiways and the tarmac.
You can search for extra AFCADs if you have AFCAD2.exe, otherwise there is a tool here.
(This is AVSIM so you'll need to be logged in.)
HOWEVER, be aware that my installer installs two AFCAD files, and both are required!
One is in Addon Scenery\scenery and the other is in Scenery\World\scenery.
It would certainly be worthwhile doing a check in your scenery library for any other scenery items which may conflict. This is normally the main cause of inexplicable crashes.
Does this happen with any aircraft? I wonder if it is a conflict with the Actigate module which controls the gates? You can turn this off from the Modules menu, from memory, and see if it makes a difference.
However it would be strange if it caused a crash while the scenery is still loading.
Let me know your specs if nothing here helps.

[ZK-MAT]

Hi Robin thanks for the reply.

The afcad in add on scenery/scenery is dated 26 Sept 06, the scenery / world / scenery one is there and dated 21 Sept 06.

It must be related to the plane. I just tried the FFX 737 300 at gate 26 and it quit out. The Posky 767, a Kittyhawk 737-700, and a default Landmark 777-300 also quit out at gate 26. A default Cessna loaded up ok on the runway then again at a heavy gate, so I switched off the Active Gate on the modules toobar and tried again with the FFX 733 at gate 26 & 27 & 28 and it crashed.

I tried then with the FFX on RW34 and RW16 and it quit out where they were ok earlier I thought.

I then tried a RealAir Spitfire at gate 26 and it was fine, so was a default Cessna 172. The ActiGate setting under modules had been switched back on though (?) so I unticked it and started again with the FFX 733 and it crashed.

Once again the dafult Cessna loaded ok at gate 26 and the ActiGate had been re-ticked.

Perhaps it's a non ga plane issue?

My specs:
AMD2600+
1 gig RAM
GT6600GT 256meg AGP
FPS locked at 24 - get 23.8 all around Wellington

Its no problem to start with a diff plane and swap once in place, but hopefully you may be able to find the glitch.

[ZK-MAT]

After spending up to 2am via email with Lawrie swapping afcads around I gave up. I deleted the actigate ini and dll from the modules folder and it works fine now. No moving jetways but that's not a biggie

[toprob]

As a matter of interest, what do you use to load the aircraft? It'd be nice to know what causes the conflict here.

[ZK-MAT]

Just the normal method I think. Start FS, choose plane, airport click start and away i go.

Here's a 30 sec vid of it working ok with ActiGate modules deleted...

http://www.splatty.orcon.net.nz/nzwn_sml.zip

Just under 3 meg, zipped avi.