NZFF

ORBX released NZNI SP1 for FSX only

Well spotted!


However, it's for both FSX and P3D. It "fixes Prepar3Dv2 issue with invisible taxiways on all hard-surfaced airports" according to the manual.

Dan

The release announcement says that the reference to P3D2 in the manual is for the yet-to-come triple installer.

toprob wrote:

QUOTE (toprob @ Sep 23 2014,8:29 AM) <{POST_SNAPBACK}>

The release announcement says that the reference to P3D2 in the manual is for the yet-to-come triple installer.

Exactly. Hence the title. I patiently await the P3Dv2 triple installer version.
I'll doubt they'll fix the issue AdamNZ has raised over on the ORBX forums, but just to have NZNI again will be great.
At least until you release the Waikato photoreal subscription.
Which reminds me: I must get out to Krippners place and get some photos for you.

Weather permitting this weekend, though, I'm trying to decide whether to:
- do my Controlled Airspace flight from Te Kowhai to Tauranga in the CH601
- do a practice flight for my not-that-far-away flight test
- go to a fly in at Te Kowhai (also with BBQ and buy/sell)

Ahh, what problems to have!
I'll bet ORBX release NZNI, and Vector 1.2 and Global 1.3 on Saturday morning to throw even more decisions my way!

What was the issue AdamNZ raised?

Ummm...

1. Dim beacons on skytower
2. Lights across the AKL harbour bridge (there are none), and the 'luminous' road surface on it
3. Floating houses; which someone else posted they didn't see (there were co-ords in the screen shot)

I'll have a look myself once ORBX release the P3D version

Umm...some very odd things happening here (unfortunately forgot to take screenshots). Get down on the deck and cruise around to the east of Auckland city - Many houses "floating" in mid-air! Anyone else see this? I don't know if this has always existed or whether its as a result of the update - its not an area I fly around usually but for some reason I just wanted to fly under the Harbour Bridge (taking off from Ardmore then heading to the coast) and noticed these artefacts on the approach path..




Sorry - should have added - this is in FSX

Certainly was like this in the past.
I have no idea about how scenery works in FSX / P3D but I simply can't understand why an object is simply labelled as "on the ground", and ground level is surely where the mesh says it is!
How hard can it be?! Why do we see floating artefacts/objects and airports in trenches or on plateaus when they should simply be "on the ground" as they are in RL? Bizarre
I'm sure there is a 'good' reason for it, but buggered if I know. Well, not literally, obviously.

I don't think the floating houses are an Orbx issue, this tends to happen occasionally no matter what the scenery, especially with an addon mesh. It may happen if there is a lot of autogen in the area -- I suspect that the sim may be running out of time and placing the autogen before the addon mesh, which puts it at the 'default' elevation. I could be wrong, though.
You can normally reload the scenery -- by Scenery Library | OK -- to fix this.

Perhaps a post on the FTX forum is in order?
There is nothing about NZNI SP1 there so far.


Edited: Had the wrong island.

steelsporran wrote:

QUOTE (steelsporran @ Sep 24 2014,1:31 PM) <{POST_SNAPBACK}>

Perhaps a post on the FTX forum is in order?
There is nothing about NZSI SP1 there so far.

NZSI is at SP3 for FSX and P3Dv2
You will find it on the support page at fullterrain.com
Or in your FSS account, of course.

NZ South Island
Version 003 (SP3)

Oops, that should have read NZNI Sp1 Force of habit, hardly ever go there.

Right here, hence why I started this thread...

http://www.orbxsystems.com/forum/topic/850...service-pack-1/

I don't think in the release announcements is the place for problems. I'm talking payware support.

toprob wrote:

QUOTE (toprob @ Sep 24 2014,1:30 PM) <{POST_SNAPBACK}>

I don't think the floating houses are an Orbx issue, this tends to happen occasionally no matter what the scenery, especially with an addon mesh. It may happen if there is a lot of autogen in the area -- I suspect that the sim may be running out of time and placing the autogen before the addon mesh, which puts it at the 'default' elevation. I could be wrong, though. You can normally reload the scenery -- by Scenery Library | OK -- to fix this.

Tried that - didn't work.

Thought about your possible explanation. If that were happening, would you not expect to see the effect in more areas (with approx.. same autogen density) rather than isolated areas?

dart15 wrote:

QUOTE (dart15 @ Sep 25 2014,2:51 PM) <{POST_SNAPBACK}>

Tried that - didn't work.

Thought about your possible explanation. If that were happening, would you not expect to see the effect in more areas (with approx.. same autogen density) rather than isolated areas?

Actually, the fact that there are just isolated patches was the reasoning for my theory -- just a single agn tile or two left 'stranded' at the incorrect elevation.

But I'm beginning to think that FSX (and P3D) is inherently buggy when it comes to autogen elevation issues -- this is particularly noticeable using FTX NZ mesh, as it seems that as the mesh is loaded LOD by LOD, the initial LODs might come from the default mesh, or Vector Land Class, if installed. So once the 10m LOD (which means FTX only, generally) kicks in, I sometimes get a huge 'thump' as the elevation changes substantially. This works both ways, dropping down a LOD causes changes in the opposite direction.

The only solution would be for LM to redo the mesh system, which might be on their list -- along with non-flat airports, for instance.