NZFF

Here's the promised patch for Southern Lakes Adventure. Note that this is not just for FTX compatibility, it includes enough minor improvements to make it worthwhile for anyone who owns Southern Lakes to install.
However it also lets you patch the scenery for FTX compatibility. There's a manual included in the download, please read it before you install!

The most important thing is that if you DON'T have FTX NZSI installed, you will need to de-select the FTX compatibility patch when you run the installer. This will all become clear when you read the manual:)

I'm interested in feedback, it is well-tested on systems with FTX NZSI installed, but I'm particularly interested in those who don't have this. That's either Vector Land Class or default FSX users.
This is a quiet test release, once I get some feedback I'll release it officially.

You can now download the patch from the Southern Lakes Adventure product page.

WARBIRD CENTRAL ... COOL

Looks great ....hopefully will give this a go tomorrow night

[quote name='toprob' date='Mar 18 2012,1:39 AM' post='8306048']
Here's the promised patch for Southern Lakes Adventure. Note that this is not just for FTX compatibility, it includes enough minor improvements to make it worthwhile for anyone who owns Southern Lakes to install.
However it also lets you patch the scenery for FTX compatibility. There's a manual included in the download, please read it before you install!

The most important thing is that if you DON'T have FTX NZSI installed, you will need to de-select the FTX compatibility patch when you run the installer. This will all become clear when you read the manual:)

I'm interested in feedback, it is well-tested on systems with FTX NZSI installed, but I'm particularly interested in those who don't have this. That's either Vector Land Class or default FSX users.
This is a quiet test release, once I get some feedback I'll release it officially.

etc

Robin

I am running NZSI within FSX + acceleration on a dedicated computer with an FSX configuration that has on it no other third party scenery except the FS-creations (NZMF etc) scenery which is fully compatible with NZSI. With the exception of some third party aircraft and the FS product mentioned above there was nothing but stock default FSX and NZSI on it.

1. I did an ex DVD install of "Southern Lakes Adventure" (scenery only including its 20M files) with FSX in Default mode.
It was activated in the normal manner with scenery level activations in the following order 1. NZMF etc, 2 RealNZtekapo % 3 RealNZwanaka etc.

2. With FSX in Oceanic mode I installed your updating file; WillowTreeTextures not selected, ORBXNZSI compatibility selected. no apparent problems

3. After the installation was "finished" I ran the FTX configurator to find that the mode had changed to "Default" [I carried out 1 2 twice and reached this postion both times]

4. After selecting "Oceanic" mode the scenery config file at this stage showed firstly the ORBX files, then the NZMS etc file followed by the tekapo and wanaka files and then the normal FSX scenery
config entries.

FSX restarted and Wanaka selected. I found that there were some elevation problems and also both building sceneries visable

5. I "deactivated" the RealNZtekapo and RealNZwanaka sceneries

FSX restarted. Only the NZSI building sceneries were displayed but the elevation probem (sealed runway only visable in "lookdown" mode) persisted

6. Found an NZWF file within scenery\world\scenery. file name changed by adding .bak

FSX resstarted.Taxiways and sealed strip now found in deep ditches.

I found no other NZWF entries

Clyde Williams
LEVIN

rayclyde wrote:

QUOTE (rayclyde @ Mar 14 2012,2:44 PM) <{POST_SNAPBACK}>

Robin

I am running NZSI within FSX + acceleration on a dedicated computer with an FSX configuration that has on it no other third party scenery except the FS-creations (NZMF etc) scenery which is fully compatible with NZSI. With the exception of some third party aircraft and the FS product mentioned above there was nothing but stock default FSX and NZSI on it.

1. I did an ex DVD install of "Southern Lakes Adventure" (scenery only including its 20M files) with FSX in Default mode.
It was activated in the normal manner with scenery level activations in the following order 1. NZMF etc, 2 RealNZtekapo % 3 RealNZwanaka etc.

2. With FSX in Oceanic mode I installed your updating file; WillowTreeTextures not selected, ORBXNZSI compatibility selected. no apparent problems

3. After the installation was "finished" I ran the FTX configurator to find that the mode had changed to "Default" [I carried out 1 2 twice and reached this postion both times]

4. After selecting "Oceanic" mode the scenery config file at this stage showed firstly the ORBX files, then the NZMS etc file followed by the tekapo and wanaka files and then the normal FSX scenery
config entries.

FSX restarted and Wanaka selected. I found that there were some elevation problems and also both building sceneries visable

5. I "deactivated" the RealNZtekapo and RealNZwanaka sceneries

FSX restarted. Only the NZSI building sceneries were displayed but the elevation probem (sealed runway only visable in "lookdown" mode) persisted

6. Found an NZWF file within scenery\world\scenery. file name changed by adding .bak

FSX resstarted.Taxiways and sealed strip now found in deep ditches.

I found no other NZWF entries

Clyde Williams
LEVIN

Hi Clyde
Just a few questions.
When you say FTX configurator, do you mean FTX Central?
Did you follow the steps in the manual to set the FTX Scenery Library Insertion Point?
Have you installed Orbx's own NZSI patch?
How sure are you that Oceania was selected in FTX Central before you installed the Southern Lakes Patch?

The main culprit here is the scenery priority. The ONLY way to set the correct scenery priority for FTX NZSI is using Orbx's own Insertion Point tool, if you don't use this, using FTX Central will ALWAYS place NZSI at the top of your scenery library, and you need it to be lower in the Scenery Library, so that all NZ airports sit above it.

However something else is happening here as well -- I'm not aware of any way in which my patch can influence the currently selected FTX Region. Did your FTX Central work ok before this?

I may have to make it clearer that you need to set the Insertion Point otherwise FTX Central will keep resetting it incorrectly.

Just piping in here again, mainly so that I can be the 150,000th post:)

I've been giving some further thought to the installer's options screen. At the moment this relies too much on every user reading the instructions, which doesn't really happen, so I'll put in some more error checking.

I was thinking that the FTX compatibility patch should be able to work even if Oceania is not selected. I'll change the code.

I'll add a check so that the installer only attempts to install the FTX compatibility fix if FTX NZSI is actually installed.

Installing the patch without first setting the FTX Insertion Point shouldn't be a real problem, as long as the Insertion Point is actually set before trying Wanaka or Tekapo in FSX. The real danger is that someone will run FSX and see there is a problem, then try and fix it themselves. This is a tricky issue, which must have a solution. Hmmm.....

toprob wrote:

QUOTE (toprob @ Mar 19 2012,5:35 AM) <{POST_SNAPBACK}>

Just piping in here again, mainly so that I can be the 150,000th post:)

I've been giving some further thought to the installer's options screen. At the moment this relies too much on every user reading the instructions, which doesn't really happen, so I'll put in some more error checking.

I was thinking that the FTX compatibility patch should be able to work even if Oceania is not selected. I'll change the code.

I'll add a check so that the installer only attempts to install the FTX compatibility fix if FTX NZSI is actually installed.

Installing the patch without first setting the FTX Insertion Point shouldn't be a real problem, as long as the Insertion Point is actually set before trying Wanaka or Tekapo in FSX. The real danger is that someone will run FSX and see there is a problem, then try and fix it themselves. This is a tricky issue, which must have a solution. Hmmm.....

Robin

Having had two or three good wines before dinner I will need time to consider what you say: but will think about it until tomorrow. Just one thing - when you you ask about the order of the sceneries (the scenery cfg file) I interpret lower in order as meaning anything numbered greater than 1 is lower in order. eg the first entries (numbered 1,2,3 etc) are the highest. In my case numbers 1-5 are the ORBX entries and those following will be be NZMF, Tekapo and Wanaka in that order. Or are you saying than NZMF, Tekapo and Wanaka should be 1,2,3 followed by the ORBX entries?

Sileni's Savignon Blanc has a lot to answer for

Clyde

rayclyde wrote:

QUOTE (rayclyde @ Mar 14 2012,7:19 PM) <{POST_SNAPBACK}>

Robin

Having had two or three good wines before dinner I will need time to consider what you say: but will think about it until tomorrow. Just one thing - when you you ask about the order of the sceneries (the scenery cfg file) I interpret lower in order as meaning anything numbered greater than 1 is lower in order. eg the first entries (numbered 1,2,3 etc) are the highest. In my case numbers 1-5 are the ORBX entries and those following will be be NZMF, Tekapo and Wanaka in that order. Or are you saying than NZMF, Tekapo and Wanaka should be 1,2,3 followed by the ORBX entries?

Sileni's Savignon Blanc has a lot to answer for

Clyde

Good to see your priorities are impeccable:) I mean the wine, not the scenery....
Speaking of priorities, I always refer to the way they appear in the Scenery Library within FSX, which co-incidentally is the same way they appear within the FTX Central Insertion Point tool. So when I said