RealNZ Wellington - I've stuffed up the airport elevation

[Adamski]

A new system and a clean install. I was working my way through adding all my RealNZ sceneries one by one.

When I first installed NZWN, all was fine, but after I (mistakenly) added it again from the "Across the Straits" package, I got this:





I also added the little freebies (Taranaki, Coromandel, Paraparaumu etc.) that came with the "Straits" package. Re-installing the original NZWN (FSX) version hasn't cured it.

I seem to remember this happening to me before, but can't remember what the cure was. BTW - I always install from the full archive.

All my other sceneries (including Tauranga, Rotorua and AKL Super-City) are fine. VLC 1.1 installed.

HELP!

Also - I've always had a grey block sea-wall ... is that a missing texture or does it look like that in RL?

[toprob]

I don't think your elevation is the issue, more likely the underlying mesh and/or mesh settings. A couple of ideas -- do you have Tim's 2 metre Wellington mesh installed? This isn't quite compatible, so isn't recommended at the moment. Also, setting the mesh resolution too high within FSX can cause problems, the recommended setting is 10 metres.

There is a concrete texture on the tunnel, but it isn't great -- this was being built when I photographed the airport, so I really had no idea how it was going to turn out.

Real NZ Wellington is definitely in the 'legacy' category now, and is showing its age, lacking a number of FSX features which we take for granted these days. There is a completely new Real NZ/VLC Wellington coming shortly, with a feature set similar to Real NZ Nelson -- 10 cm airport textures, 50cm city textures, and completely FSX-compliant models, including custom animated airbridges (to catch up with the FS2004 version:) and the Rock, formerly known as the Pumpkin....

It isn't an update, so it won't be offered as such, but there will be a special price which takes into account the existing user base.

Look out for some early screenshots around Christmas.

[Adamski]

QUOTE (toprob @ Dec 1 2011,7:28 PM) <{POST_SNAPBACK}>

I don't think your elevation is the issue, more likely the underlying mesh and/or mesh settings. A couple of ideas -- do you have Tim's 2 metre Wellington mesh installed? This isn't quite compatible, so isn't recommended at the moment. Also, setting the mesh resolution too high within FSX can cause problems, the recommended setting is 10 metres.

There is a concrete texture on the tunnel, but it isn't great -- this was being built when I photographed the airport, so I really had no idea how it was going to turn out.

Real NZ Wellington is definitely in the 'legacy' category now, and is showing its age, lacking a number of FSX features which we take for granted these days. There is a completely new Real NZ/VLC Wellington coming shortly, with a feature set similar to Real NZ Nelson -- 10 cm airport textures, 50cm city textures, and completely FSX-compliant models, including custom animated airbridges (to catch up with the FS2004 version:) and the Rock, formerly known as the Pumpkin....

It isn't an update, so it won't be offered as such, but there will be a special price which takes into account the existing user base.

Look out for some early screenshots around Christmas.

THanks for the quick reply, Rob. I don't have any other mesh or sceneries other than those mentioned above (and VLC). This is a brand new install, so pretty "clean" so far. I'm intrigued as to how/why it was fine then only "broke" after "Across the Straits".

I also suspected mesh - and tried all sorts of settings - 1m all the way to 300m ... no difference.

I agree about NZWN showing its age (but it's still pretty good!) ... and will look forward to a new version!

[toprob]

I'll take a look at this tomorrow, and see if I can recreate it. I do need to reinstall it myself, since mine is seriously dismantled at the moment...

[Adamski]

QUOTE (toprob @ Dec 1 2011,8:29 PM) <{POST_SNAPBACK}>

I'll take a look at this tomorrow, and see if I can recreate it. I do need to reinstall it myself, since mine is seriously dismantled at the moment...

Arrrgh ... that sounds like a lot of trouble (for you). I'm way out of my depth here, but I seem to remember that "things" can sometimes overwrite values in the global FSX [elevation] data. Is it possible that the value for NZWN has been changed (somehow)?

Is there a single file that we could scrutinise (or replace)? I still have my old (working) setup and can always copy files over if needs be.

I also very dimly remember some sort of issue with the Taranaki (or some other) scenery - possibly messing something else up. Did I imagine that? My memory is so vague these days :-(

[GlennAV8R]

Great news, its my home airport.

There have been a few changes with the aeroclub relocating now and the new execujet hanger having been built. I have access airside if you need any photos or info. Cant wait for this one.

[Nzeddy]

Wooohooo!

[Adamski]

Rob!!!! Hold your horses!!!! I'm ashamed to say it looks like a real stuff-up on my part ... and all my theories were just red herrings. I'd forgotten that I'd placed that DTM file (DTM_Wellington_2m.bgl) in the VLC DTM directory. I could've sworn I had to do that on my previous install - but have long since forgotten what that file was for - whether it's needed (any more) or even whether I had it in the right place.

I removed the file and it's all back as it was. So ... back to enjoying NZWN and whizzing over to NZNS, which is a beauty!

[toprob]

Glad to hear it's sorted.

By the way, here's a pre-preview...



I know I've got into trouble for putting a Godzone sign into a scenery before, being accused of pushing my religion down people's throats, but um... I don't care.

[Naki]

Haha ..it should be Godzone up there for real!

[Adamski]

QUOTE (Naki @ Dec 2 2011,2:51 PM) <{POST_SNAPBACK}>

Haha ..it should be Godzone up there for real!

Thanks for your help, Rob ... I'm looking forward to the New version. If it's anything like Nelson, we're in for a treat.

Is NZAA or NZWP on your "to-do" list - or are other people doing them?

[toprob]

QUOTE (Adamski @ Dec 2 2011,3:02 PM) <{POST_SNAPBACK}>

Is NZAA or NZWP on your "to-do" list - or are other people doing them?

My 'to-do' list consists of those airports where I have high quality aerial images bought and paid-for -- which won't include anything in Auckland in the near future.
So that means NZWN (payware) and NZCH (freeware) at the moment. Some much smaller projects as well, of course.

[Ian Warren]

Wonder in lite to what - how CHCH has started to get a fix ... Maybe ' BOBZONE' Cool looking screen .... I can hear Rob mubble 'I don't think so'

[Nzeddy]

Sloped flattens!

http://g.co/maps/tqee9

EDIT: Or a GMAX sloped model.

[NZ255]

QUOTE (Nzeddy @ Dec 2 2011,10:22 PM) <{POST_SNAPBACK}>

Sloped flattens!

+1000000

[NZ255]

QUOTE (Nzeddy @ Dec 2 2011,10:22 PM) <{POST_SNAPBACK}>

Sloped flattens!

http://g.co/maps/tqee9

EDIT: Or a GMAX sloped model.

To sort of revive this topic, Ed, are you talking about sloped polygons/gMax model so the runway is sloped? Or just for the terrain?

I assume you mean the terrain as I'm sure you know that a sloped runway will mean no AI, which wouldn't be good.

It does get a bit hard with the terrain in Wellington though...one end of the runway is 41 feet, the other 24 feet and the apron is about 20 feet near the runway sloping up to 30 odd feet near the terminal.
I've been mucking around with Wellington before I heard Rob was doing it and you have to make compromises somewhere because unfortunately FSX ground has to be FLAT for AI Arghhh!!!

It's annoying when you know your own airport so well and you want it to be perfect in every way

Very much looking forward to this though, Robin! No pressure

[Nzeddy]

QUOTE (NZ255 @ Mar 21 2012,11:27 PM) <{POST_SNAPBACK}>

To sort of revive this topic, Ed, are you talking about sloped polygons/gMax model so the runway is sloped? Or just for the terrain?

The terrain.

FSX doesn't make slope polys that well... it's all jagged and mucked up. lol

I worked on this last year as a personal project (canceled). Using Tims 2m mesh and SBuilderX.