'Real New Zealand' scenery
Finding a download for a Real New Zealand scenery is different from a Subscriber or Godzone Compilation (hese are the same thing) download. Anyone who is used to the way in which subscription downloads work may be confused when ordering a 'normal' scenery product, so here's a quick intro to finding your download!
First, this applies to Real NZ Scenery only -- the Godzone photoscenery, whether purchased as a Subscription or Compilation, is not added to your account downloads, but it is always available from the 'quick downloads' page.
There are a couple of ways to download your Real NZ purchase. First, you should receive a confirmation email from the Store, which includes a download link. However you can access your downloads at any time via the Store, by clicking on the 'My Account' menu link at the top of any page (except the home page), provided you are logged in of course.
This is a trick question, isn't it?
Some people are seeing the extra folder chooser box which all Godzone installers display for the very first Godzone Prepar3d v3 install, and thinking that this means that the installer needs to know where Prepared is installed. This is not the case! Please read the manual, if you are unsure about this.
From Prepar3d version 3, Lockheed Martin have recommended that addons are no longer installed within the Prepar3d folder system. So when you first install Godzone scenery (the Subscription, plus Real NZ Dunedin) the installer will ask you to choose a location where it will place all subsequent Godzone scenery. This is explained in the manual,
There is also some info on how to find and delete the Godzone.xml file which remembers this location for subsequent installs. Please remove this if you plan to shift ALL your Godzone scenery, via an uninstall and reinstall. So really you should only reset this if you chose the wrong location, and need to fix it.
Yes, starting with Real NZ Nelson all Real New Zealand scenery is designed to work with the most popular 'base' scenery packages for New Zealand -- Vector Landclass, FTX NZSI/NZNI, and the default simulator.
Note that 'works with' means that it will work as intended, it doesn't imply any FTX features. The border between Real NZ Nelson and FTX NZSI is blended for a good match, but in general I do not match colours to FTX scenery -- FTX have their own colour 'palette' which makes New Zealand nice and green, but isn't the way I see New Zealand. As all Godzone/Real NZ photoscenery is derived from summer photos, the blend may be more noticeable depending on the season.
The Real NZ installer will make some changes to both Real NZ Nelson and the FTX Nelson when it detects FTX NZSI. Therefore it is always best to have FTX NZSI installed BEFORE you install Real NZ Nelson. If you install FTX NZSI later on, you really should uninstall Real NZ Nelson first, then reinstall after. However this isn't the only way, you can make the necessary changes yourself, just contact me for details.
This can be thought of as a 'global', shared scenery folder. At the moment it includes:
- Elevation Stubs, which used to be included in Scenery\World\Scenery, but are now separate from your flightsim installation;
- Autogen building textures, which used to go in the global 'texture' folder but are now separate from your flightsim installation.
This follows the recommended method of adding 'global' features, which should no longer be put in the simulator install folder system.
You should leave the Godzone entry active, as it should not affect any third party scenery, unless there are conflicting elevation stubs. In this case you can try disabling specific files which include the airport code for the relevant airport! Disabling the addon itself is not recommended unless you intend to delete all Godzone scenery.
There is a larger post here, explaining how to prevent the overlap between the Southern Alps subscription scenery, and the Real NZ NZCH photoscenery area.
Yes, All Real NZ and Godzone scenery released since Real NZ Nelson, and including the Subscription, works with FTX NZSI. There is some extra information here.
There is also a great set of screenshots from Mallard on the FTX forum, although you may need to be a member over there to view it:
Southern Comfort, a flight from FTX NZQN to Real NZ Dunedin. Note that this starts at Orbx's Queenstown, and ends at Real NZ Dunedin.
Hey, floating houses are cool:)
The consensus is that floating houses are a limitation of the simulator, rather than an issue for an individual scenery addon -- in fact, I have seen floating houses at the same places in both VLC and FTX NZSI, so I suspect that this is more geographical than anything a developer does or doesn't do. Lockheed Martin have done really well to minimise this in recent releases, and I hope that at some point it will become a thing of the past, but at the moment, the only other option would be to remove huge chunks of houses completely, and even then there would be no guarantee that they won't pop up -- and I mean all the way up -- in another location.
If you wish to explore the city without floating houses, you can reload the scenery when you get to the city -- the best way is to go to the Scenery Library and immediately press 'ok' to exit again The scenery will reload and everything should drop to ground level (hopefully except your aircraft!) and remain there while you stay in the area.
It should, and if it doesn't, it may most likely be one of three reasons:
- A conflicting airport scenery -- I would normally recommend that any other addons for Real NZ airports should really be deactivated. However this isn't normally a problem, in that Real NZ Dunedin is designed to exclude most other underlying scenery. However some addons may sneak through the process.
- The installer could have been unable to disable the FTX NZTI elevation stub for some reason -- this is the only FTX file which conflicts with a normal Real NZ Dunedin install, and the installer attempts to disable it by changing the extension from .bgl to .bak. This file is located in Scenery\World\Scenery in your simulator's main folder, and includes 'NZTI' in the file name. If this still has a .bgl extension, then you could change the extension to .bak yourself.
- An incorrect FTX Insertion Point -- if you have never set the FTX Insertion Point, then you will need to do so to get the best out of Real NZ scenery. There is some information in the Real NZ Dunedin manual on how to do this.
If you need help with any of these steps, or they don't fit your elevation problems, then please contact me via this site. The same thing apples to NZDN, but I don't think that FTX actually changes the elevation of their NZDN. so there isn't a stub to mess things up.
No, the scenery is designed as a complete package, so there is no official way to turn off aspects of the scenery. Unofficially, you'll have to experiment....
The Dunedin jetways are controlled by the third-party SODE modules. SODE also controls -- and displays -- the windsocks, and any flags which respond to wind direction. The Real NZ Dunedin installer will install SODE if it is not already installed, or update an earlier version. This is all explained in the manual, but it does require some input from the user -- after SODE is installed, you must activate it for the simulator versions that will use Real NZ Dunedin.
Since the SODE installer is separate from the Real NZ Dunedin installer, it is possible to overlook the activation step, unless you follow the instructions in the Real NZ Dunedin manual. If you do miss or skip this step, then you can activate the module at a later date, by running the SODEPlatformManager.exe which is installed by the SODE installer, the default location is:
C:\Program Files (x86)\12bPilot\SODE
...although you may have chosen to install SODE elsewhere. Activation simply adds the SODE modules to your exe.xml and dll.xml files for each of the chosen simulators.
Some users choose not to activate SODE, I assume because they consider it an added complication, but I would recommend that you give it a try. The third-party tools which Real NZ Dunedin installs -- SODE and the Autogen Configuration Merger Tool -- are both designed to solve problems which stem from multiple developers' methods of adding advanced features to their scenery. Both are well-tested, and are not found to cause any issues beyond poor developer implementation, or users messing around with things without a good understanding of the consequences.
SODE implementation in Real NZ Dunedin was a test case, really, and I will continue to use it going forward, although future releases may offer the ability to replace SODE features with more 'default' options -- static jetways, default windsocks (I hate those!) and normally wind-oriented objects like flags with static models. All of these would be compromises, and would detract from the full experience of a Real NZ scenery.
I've always wanted to add some more realistic New Zealand vegetation to the autogen system, but until recently this has not been possible. Well, it has been possible, for example Orbx do this for FTX NZSI and NZNI, but the way in which they implement this means that they simply replace the autogen descriptions file -- of which there can only be one -- with their own. So if another developer added their own autogen descriptions, these would be overwritten every time Orbx scenery was installed, a FTX region was changed, or FTX Central was run.
Arno, who designs some amazing development tools and runs the FSDeveloper.com website, looked at ways to overcome this issue by developing a tool which would 'self-manage' and 'self-repair' any autogen description additions if they were accidentally -- or purposefully -- overwritten. This is the Autogen Description Merger Tool, which runs each time the simulator runs, checks the autogen description files, and makes sure that any extra descriptions are there, and adds them if they are not. It doesn't remove any entries from the descriptions, so it can't affect other existing descriptions, so it is a safe, reliable method of maintaining the autogen descriptions.
The Autogen Description Merger Tool installer is called and run during the Real NZ Dunedin installation process. There are a couple of steps which the user must take, these are explained in the Real NZ Dunedin manual.
However it doesn't help my assertion that this is safe and simple that my original Real NZ Dunedin installer didn't properly run this, resulting in a patch. So if you installed the scenery prior to mid-November 2016, you should download and run the patch. Note that the current download is already patched, so you shouldn't have problems, and won't require the patch.
If you have installed Real NZ Dunedin from a recent patched installer, or run the patch over the original installer, and still have problems with missing trees, then you should contact me for a solution.
Prepar3d v4.4 has a bug which affected how some scenery objects appeared, including any Real NZ airports, objects and ground polygons. This was a listed fix in Prepar3d v4.5, so if you still use 4.4, I really do recommend that you upgrade.
As far as I am aware, there is no known fix for those who choose to remain with v4.4.
I know a lot of people were interested in this, the replica Spitfire on a stick outside the shopping centre on Memorial Ave. I did have a go at modelling this, but my aircraft skills are not good. However this is the ideal project for someone keen -- if anyone is capable and talented enough to model a Spitty on a Stick then go for it! You can release it any way you like, or I can put a download on my website.
NZCH was always going to have some GSX support, mainly for the Visual Guidance Display Systems. I'm a big fan of GSX, it just adds so much atmosphere to an airport. However during the NZCH beta there were a number of issues with GSX users. All these testers actually came up with a different solution themselves, so in the end we decided that this was a GSX problem, and shouldn't hold up the release any longer.
However it did turn out to be one tiny error in my coding, as simple as typing 'Addon' rather than 'AddOn'. A local simmer figured this out after installing the release version, and I'm very grateful to him. So I pulled the original download and uploaded the fixed version.
A few early customers received the original version, and they may have issues with GSX, such as the Real NZ airport not being recognised, and Level 2 users may see both Real NZ and GSX jetways.
To fix this without having to download the entire installer again, you can edit the Documents\GodzoneRealNZ\add-on.xml file, in something like Notepad, or your favourite text editor.
There is one instance of 'Addon.Component'.
Simple change this to 'AddOn.Component' and save the file.
You may need to deactivate the addon within the simulator while at NZCH, wait for the default scenery to reload, then reactivate the addon. You can do this from the Options | Addons menu.
If you still have issues, let me know.
There are a lot of jetways at NZCH, controlled by SODE (SimObject Display Engine), and they should all be able to dock with a suitable aircraft, even AI if you have that featured active. There's even the dual jetway Gate 30, which will dock both jetways to larger aircraft!
The NZCH installer will check to see if you have SODE installed, and will install it if not, or update it if your version is older. The SODE installer than runs the Platform Manager, which allows you to register and activate SODE in your simulator(s). This is explained in the Real NZ NZCH manual, with screenshots.
When you run the simulator, you should have a SODE menu -- Addons | SODE. If you don't, and you are sure that you installed SODE and activated it, then it may be worthwhile uninstalling it, and reinstalling. The Real NZ NZCH installer puts the SODE installer in the Godzone\OtherInstallers folder.
This was quite a well-received feature of Real NZ Dunedin, being able to see inside the terminal as you pulled up to the gate. However with NZCH, I wasn't able to get inside access at all, and all the front of the international and domestic terminals are security areas. There is no place to sit and look at the tarmac without booking a flight. As I've said quite often, if I can't see it, I can't build it. I don't have the imagination to make stuff up, so I rely on photos almost exclusively.
I don't think this is a major issue during the day, as the angle, type of glass and reflective nature means that you don't see much of the inside anyway. In fact, you are likely to only see reflections of life on the tarmac, and I've allowed dynamic reflections to handle this. (Mid-low settings work best for me.)
At night, though, things are different. You don't get the 3D effect of internal lights coming into view, and just painting on lights isn't really a great solution. So I've left the night view of the terminals rather dark, and relied on dynamic lights on the tarmac to punch some light into the scene.
From Prepar3d version 1.05 of Real NZ NZCH, I've added a separate release download which excludes the City/Banks Peninsula/Central Canterbury photoscenery. This is mainly aimed at those with Orbx NZSI, who would prefer to see Orbx NZSI landclass outside the airport bounds.
You only need to download and install one of these, and each installer will 'overwrite' the other, so you can in fact only have one version installed at once. However you can download both, and each installer will effectively 'toggle' the scenery between the full and airport-only versions.
There is now also a FSX/FSXse version as well. This is a separate download.
The 'Download' button normally includes enough detail to show which is which. Here, the first is shown as the 'full' installer, and the second is 'airport-only'. the third is the full installer for FSX, note that there is no airport-only version for FSX.
The full download release is 2.44GB for the download, and the airport-only version is 1.48GB approx. The airport-only version includes seasonal adjustments in the included photoscenery, to blend with Orbx NZSI landclass.