NZFF

Very nice!

yea that was it Robin thanks heaps, as somebody who regularly flew out of chch you've done a great job mate!

I'm not aware of any custom Ashburton scenery apart from Godzone. Of course this will still work in FSX, although I had to do some searching to find a download. Luckily the VLC download pages are archived here. Although not custom, Orbx do a reasonable NZAS in NZSI, but the best 'modern' version would be the default in MSFS. There's a youtube video which shows the airport and town, although you should mute it, the constant stall warning stresses me out.... P.S. I see that the Godzone NZAS is coming up 10 years old.... a lifetime in FS.

zk-gd, Thanks for awesome explanations and hyperlink . Regards, Aharon

PARTY TIME

Toprob, Thanks for answers. Regards, Aharon

A bit of searching and I found the problem. In case anyone else has a similar issue I found another instance of a Godzone_NZCH.xml file in the ProgramData/12bPilot/SODE/xml folder. The duplicate was Godzone_NZCH.bak but was still an xml file. I'm not sure how it got there but I was using the GSX editor to adjust some parking/vehicle positions at some point prior to noticing the change. Removing that file fixed the problem and I could reproduce the error by putting it back. On the bright side at least I installed NZCH with the surrounding PR scenery.

How is beta testing doing for FSX version of NZCH scenery, please? Regards, Aharon

The good thing is that you can activate and deactivate large areas of scenery very easily with improved load times.

Eureka...windsocks! Having a look around there seemed to be duplicate SODE folders here and there. I am wondering if updating SODE via ORBX central is the culprit. In the end I uninstalled and deleted all the related SODE folders and reinstalled. Then I added the saved objects and XML files back in. I had heard that some simmers were having trouble with SODE after updating to 1.7.0 with ORBX Central. Most seemed to cure it by deregistering and reregistering. Funny how it only affected the windsocks.

First, sorry Bug, I overlooked your previous post. Sorry about that. Thinking this over once more, I do wonder if it an issue with the Orbx installation. Although I only cover this in relation to an Orbx reinstall or update, it does apply for a 'verify' of NZSI as well -- any changes to Orbx NZSI, and you should really uninstall NZDN first, then reinstall after any update/reinstall/verification. And it would be worthwhile to check the Orbx NZSI folders for any disabled NZDN files after the initial uninstall of NZDN. The issue is that Orbx Central will try and reverse any changes which my...

Ah that did the trick thank you. I have been mucking around with 4.5 and settings etc and the building shadow setting must have been changed....not that I would have connected the two. It's not something you notice until you notice if you get what I mean. Was it always like that just that I never noticed before? I must say I am quite happy with my current set up. It looks nice and is performing ok. I just updated to the 4.5 client only as I really didn't want to bother reloading all my add ons. Is there anything in particular in the Content and Scenery modules that is worth upgrading them...

Much appreciated. Thanks. :)

Hi Rob, Are you able to offer any more help to resolve this issue? Even if i can find out which tree files is the culprit and delete it. Thanks Les

4.5.12.30293, I just installed it 4 days ago so it should be the latest.

Hi Rob, I am very grateful for the time you took to explain in such detail how the jetways setup works. And it is good to hear that it wasn't something I did wrong during the install. I regularly travel to NZCH for work (on ANZ's A320s) and I think you are right about the jetways that work : gates 27, 28 and 34 are all at International and that's where I see, for example, the QANTAS 737-800s docked IRL. Now I know at which gates the jetways work for the 737 as things are, I'll just use those, at least for now. Same will apply to the 777 in due course (that's all I fly, other than eventually...

Prior to NZCH, the VLC Libraries installer was a stand-alone installer run during the Real NZ installation, so you needed to choose the install location separately. To make this easier, with NZCH the Libraries will install to the same 'root' folder as NZCH, unless they are already installed, in which case they will just update the current version. So it seems that with Dunedin (or prior?) you let the libraries install to the 'default' location. (Default as defined by Lockheed Martin.) The Libraries are not large, so you could leave them there, or wait for the coming stand-alone installer and...