Real NZ Dunedin
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.
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.
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....
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.
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.