NZFF

Hi there everyone.

I am running FSX with ORBX NI & SI and all 8 subscriptions with real NZ Scenery

With NZWN however i have some flat houses between the taxiway and runway in some places and not tarmac on the western apron.

Also in places it looks like i have a runway floating above the runway.


Is this a scenery library order problem? and if so what order should they be in? Cheers

Pac

Bear in mind that the western parking is unfinished in the 'transitional' airport. The next issue will tidy it up a bit, although it still won't be finished.

I don't think that you should be having floating runways, though. As far as scenery priority is concerned, as long as you have followed the instructions which come with the Subscription to set the Orbx priority using FTX Central, then priority shouldn't be an issue. So the rule is, use FTX Central to set FTX priority so that it loads before any Real NZ or Godzone scenery.

Very sorry to be a hassle but i do believe that there is a problem with the order on my library now. (i had done some playing around)

To try and save me re installing all the scenery again can someone please post a snapshot of how the library SHOULD look on fsx.

At the moment i have ditches between taxiways. Trees on hard stands and roads where there should be rivers

One thing I found was re-installing the scenery over the top again, something with FTX , the switch's not working or even levels .. One answer was to reinstall the scenery into a Clone directory (create a bogus FSX) , select the contents and over write your FSX file.

Ian Warren wrote:One thing I found was re-installing the scenery over the top again, something with FTX , the switch's not working or even levels .. One answer was to reinstall the scenery into a Clone directory (create a bogus FSX) , select the contents and over write your FSX file.

Ok thank you for the advice Ian Warren, Will give it a go tomorrow.

Note that when the Godzone installers edit the scenery.cfg, they archive it first, so you will always have a pre-install version to revert to. Maybe you could just revert to this if you have made too many changes.

This is one area i think got Screwed .. why have a 'ADDON SCENERY' in the FSX main directory and its not used as such , ..

Ian Warren wrote:This is one area i think got Screwed .. why have a 'ADDON SCENERY' in the FSX main directory and its not used as such , ..

Not sure why you would say that Ian, I use it plenty and in many of the addon sceneries I have downloaded over the years, it's kinda what that folder was put in for), randomly odd and incorrect statement there mate..

Anyways as for Wellington. When I install my NZ scenery, I install ORBX Vector and Global first, then NZNI and NZSI and Queenstown second then Rob's Godzone Subscriptions 3rd (In order from 1-8). My sliders are to the far right and his interim Wellington shows up fantastically well in my sim. I don't have the problems I did trying to match the original release so it shows me he is well and truly on the right track. You may just have to play around with your install order or how you have it placed in your layers in the scenery.cfg file...

omitchell wrote:Not sure why you would say that Ian, I use it plenty and in many of the addon sceneries I have downloaded over the years, it's kinda what that folder was put in for), randomly odd and incorrect statement there mate..
...

It was a simple choice and it keep the main FSX directory tidy, after the amount of scenery I personal have worked on and working on and done over the last 20 years its the way I have done ii.

When you think about it ....... Whats the point Microsoft putting in a folder called 'ADDON SCENERY'

I too am having elevation issues with NZWN and overflowing rivers in the Mt Cook Airport area. FTX Central is set for Global Hybrid with LC EU and Vector. The Vector configurator doesn't offer NZWN as a possible 'disable". Godzone installed itself directly under ORBX airports/sceneries in the Library and I've tried it above NZSI/NZNI with no change. Did a 'scenery' search for .bgl's and found these - 'NZWN_ADEX_GVF.BGL' and 'ADE_FTX_NZNI_NZWN_elevation adjustment.BGL'. Any suggestions ?
EDIT. Just installed your Issue 9a - NZWN problems gone.

One I have not installed for a very long time is the VLC package, simply kept everything ORBX based , Wellington has never looked better and I flew into Mount Cook couple of days back in the F-27 , one thing I have found is adjustments don't always load , as silly as it seems .

Mesh Complexity : 75
Mesh Resolution : 10m

Olderndirt wrote:I too am having elevation issues with NZWN and overflowing rivers in the Mt Cook Airport area. FTX Central is set for Global Hybrid with LC EU and Vector. The Vector configurator doesn't offer NZWN as a possible 'disable". Godzone installed itself directly under ORBX airports/sceneries in the Library and I've tried it above NZSI/NZNI with no change. Did a 'scenery' search for .bgl's and found these - 'NZWN_ADEX_GVF.BGL' and 'ADE_FTX_NZNI_NZWN_elevation adjustment.BGL'. Any suggestions ?
EDIT. Just installed your Issue 9a - NZWN problems gone.

Glad to hear it's sorted, and before I got up this morning... That's my kind of support issue.

Just a couple of points about these elevation issues. First, I'm glad that installing 9a sorted this out, but really it didn't. Issue 9a is simply photoscenery, and doesn't affect the elevation at all. This is always going to be a bit of a house of cards, a breeze can send it all tumbling down, so there can be intermittent problems. Each time I release something new, I'm aware of the pitfalls, and although the installers try to deal with the obvious few incompatibilities, just a simple reinstall -- of Orbx, Godzone, Real NZ, anything really - can upset the balance.

One hard and fast rule is that Godzone/Real NZ scenery always belongs above any 'base' scenery. That's in the simulator's Scenery Library, not the scenery.cfg, which lists them the other way around. That's why you should set the FTX Insertion Point at least once, so it drops down the list below any local addons, such as Godzone/Real NZ.

NZWN is a bit of a special case, as the Subscription NZWN includes it's own 5 metre mesh and matching flattens, so provided NZWN is ABOVE anything else mesh/elevation-related in the Scenery Library, it should sort itself out. Subject, of course, to the western parking mess which is not yet finished.

While working on Issue 9, I was acutely aware of the balancing act, even with a simple airfield like Turangi. There is a VLC Airfields Turangi, a simple NZNI Turangi, and there might even be some older Turangis lurking about. The Issue 9 installers attempts to deal with these in this way:

• If it finds the VLC Airfields Turangi, it will shift the NZTN files into the Inactive folder, which is the 'proper' way to disable VLC Airfields;
• It'll disable the matching Stub file in Scenery\World\Scenery;
• If it finds FTX NZNI, it will disable the new Godzone Turangi Airport facilities and flatten files, as the FTX elevation is vastly different. So with FTX NZNI installed, you'll see the Godzone airport models on the FTX NZNI facilities/elevations.

But this only happens at the time you install Issue 9. If you do anything in any other order -- such as reinstall NZNI -- or even change the FTX Central Region to disable FTX NZ, then you might need to sort out some mismatches. In this case, it's probably best to contact me, unless you are 100% sure of what each file does.

I missed the previous post about the Addon Scenery folder. I admit that I have a 'problem' with this, mainly relating to my OCD. I'll see if I can explain it...

The Addon Scenery folder has a Scenery and a Texture subfolder. This is the normal format for scenery folders. I look at a normal scenery folder as a property, on a street. The scenery folder name (in this case Addon Sceney) is the address of the property, the Scenery and Texture folders are the inside of the house and the yard, and the scenery files themselves are the rooms.

So for me, putting another scenery folder system inside Addon Scenery, is like putting a house inside your house. It just isn't right. In fact, it freaks me out.

What is the Addon Scenery folder then? This was designed to be a PRE-ACTIVATED scenery folder for simple scenery additions which didn't warrant their own folder. AFCADs were a common example of this, you would just drop an AFCAD into Addon Scenery\Scenery, and it would be automatically activated. It was never designed to be a repository for all addon scenery. In fact the main Scenery folder makes more sense -- that's the FSX\Scenery folder -- as it already includes other scenery folders, each with their own Scenery/Texture subfolders.

How do I know this? I can remember when MS added the Addon Scenery folder, they explained that it was to speed up activation, since it was pre-activated when you installed the simulator.

With Prepar3D, this becomes clearer, as there is no pre-activated Addon Scenery folder, in fact there is no Addon Scenery folder.

I am aware that it does clutter up your main folder to have a lot of scenery folders, which is why I've shifted to the Godzone\addonscenery format.

First, I'm glad that installing 9a sorted this out, but really it didn't.

A thing I've learned with FSX - "don't kick a gift horse in the mouth".

Olderndirt wrote:

First, I'm glad that installing 9a sorted this out, but really it didn't.

A thing I've learned with FSX - "don't kick a gift horse in the mouth".

One thing again with FSX, things still happen with the asking too and when you do that damn horse turns its butt to you and walks away from ya

Ian Warren wrote: I flew into Mount Cook couple of days back in the F-27

A CFIT, eh? Sounds like the traditional ORBX elevation problem ... yashoulda stuck with VLC and Godzone

emfrat wrote:

Ian Warren wrote: I flew into Mount Cook couple of days back in the F-27

A CFIT, eh? Sounds like the traditional ORBX elevation problem ... yashoulda stuck with VLC and Godzone

They really give ya those UPS and DOWNS problems ..... Now Rob is really hooking into photo real wonder if I could get a money back ...... I don't think so

Hey Robin,

I've been having the same problem reported by PacBlue earlier in the thread. Wellington has a floating runway and additionally the land between the taxiways at the lower runway level is sunken into the earth about 10-15 feet. The sunken sections are where the taxiway linking sections are and it makes them about 10-feet wide which means aircraft slip off and into the trench. BTW I have both FTX/Global and NZNI/SI installed with Oceania active and Global is not in hybrid mode.

I spent a good couple of hours mucking about temporarily removing FTX/Orbx BGLs with "wellington" or "nzwn" in their file-names but nothing made a difference. If I disabled "Wellington Godzone" in the scenery library the elevation problem went away but then I lost your much better looking airport details (buildings etc)

I checked the FTX insert order and that also seems fine, is a long way down the list well below any of the GZ*** stuff. I've also tried re-installing the GZ Phototreal packs etc.

My solution has been to re-enable GZ Wellington but to remove the ADEX, runway and tarmac files which has given me a sort of frankenstein which works fine in the interim. This may help PacBlue, probably not anyone else at this point. My directory listing of the GZ Wellington Scenery folder follows...

./000_NZWN_SBX.BGL
./000_WgtnCity_SBX.BGL
./NZWN_lib.BGL
./tempTestLib.bgl
./Turbines.bgl
./wgtnairport.bgl
./wgtncarlib.bgl
./wgtncity.bgl
./WgtnCityFSXp.bgl
./WgtnCity_lib.BGL
./WgtnCity_pl.bgl
./WgtnFSXlib2.bgl
./WgtnLibNew.bgl
./WgtnPenObjects.bgl
./Wgtn_NgaioTrees.bgl
./_removed
./_removed/CVX_NZWN_SBX.Bgl
./_removed/NZWN_ADEX_GVF.BGL
./_removed/NZWN_ADEX_GVF_CVX.bgl
./_removed/NZWN_runway.bgl
./_removed/NZWN_tarmac.bgl

Hi Dean have you removed from world scenery ADE_FTX_NZNI_NZWN_elevation_adjustment.bgl by renaming the .bgl to .BAK

The only odd thing I have in Sub9 is a photo of a giant mushroom It seems to be a new Sports Centre. I only use VLC and Godzone, and all the scenery looks great