100% ad-free
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!--
Jeff, ChCh, NZ

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)--
Jeff, ChCh, NZ
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?Dart 15![]()
Asus P6X58D Premium | i7 930 @2.8 OC 4.2 Ghz | Radeon 5850 | 3x2 GB Corsair Dominator DDR3 1600 7-8-7-7-20 |
OCZ Vertex3 120GB SSD | Corsair H50 | Corsair HX650W | Cooler Master Gladiator 600 | Win7 x64 | FSX Acceleration
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.
Users browsing this forum: No registered users and 8 guests