Page 1 of 1

PostPosted: Mon Jan 06, 2014 4:36 pm
by steelsporran
Just done a complete re-install and this is how Milford looks with nothing added, surprised about the water though.

PostPosted: Mon Jan 06, 2014 5:01 pm
by Ian Warren
ohmy.gif AirTruk Me ... step back into the time tunnel pirate.gif

PostPosted: Mon Jan 06, 2014 5:02 pm
by Dash8captain
It's pretty terrible really isn't it - I cant even recognise that part as Milford - it looks as though you have a scenery error! laugh.gif

I could never fly without Orbx or VLC etc

PostPosted: Tue Jan 07, 2014 5:30 am
by Splitpin
Was there scenery in that screen .... winkyy.gif

PostPosted: Tue Jan 07, 2014 9:06 am
by toprob
Yes, Milford was always 'broken' in FSX, due to the SRTM (Shuttle Radar Topography Mission) data they used. It looks to me like low cloud cover over Milford, but whatever caused it, it certainly wrecks one of the most dramatic parts of NZ. Luckily this is just an isolated issue, the rest of NZ did pretty well with the default mesh.

PostPosted: Tue Jan 07, 2014 9:31 am
by Ian Warren
Just think had that been real, Sir Pete would have been in making another movie .. maybe he still could.. the movie Dambusters ?

PostPosted: Tue Jan 07, 2014 11:48 am
by ZK-LGD
Actually, it's easily fixable.

Go to FSX/Scenery/1105 folder and make a copy of APX92470.bgl. Extract the data from APX92470 using BGLAnalyzeX and edit the resulting .xml file in Notepad. Change all NZMF elevations from 846.00m to read 3.05m (with the exception of Tower), save, and recompile with the BGLComp executable (found in the FSX SDK/Environment Kit/BGL Compiler SDK).

Remember to keep the original APX92470.bgl safe.

Edit: Technically, NZMF's elevation is 10 feet, so the correct elevation is 3.048m, but I don't know how well FSX handles that sort of accuracy.