Hi Gary,
I reviewed the tutorial by Jim Robinson and the only thing that was comparable to mine is regarding the moving of the cvx9232.bgl file from it's default location. Jim answered the very thing I was concerned about regarding the tutorial I'm was following. In the tutorial I was following, the author mentioned to move the cvx9232.bgl to another folder. That seemed strange to me since we're supposed to exclude them and not move them. I did move the file but I at least backed it up. Jim stated one should never move a default file from it's original location and that it should be excluded, not moved.
Indeed, the "Best Practice" for SDK compliant FS Development is to Exclude then Replace default and/or other custom scenery content.
Tiberius, author of the Nauru tutorial assumes end users do that for use
only on their own FSX installation; but still a "No-No", IMHO.
But, Nauru is out in the middle of nowhere, and anything one does locally is unlikely to impact any other FSX scenery in the region.
Furthermore, at that time, ACES and the FSDEV community did not know of a way to exclude GPSHydroPolys.
CvxExtractor had not yet been developed, so FSX default CVX9232 output could not be used to fix GPSHydroPolygons within the file.
CVX9232, shows typical FSX misaligned GPSHydroPolys, could not be 'fixed' at the time, so was best dealt with by being replaced entirely.
Tiberius "moved" CVX9232 out of FSX \Scenery\1104 folder, and makes a replacement via SBuilderX / ADE CVX vector files rather than making a corrected CVX9232 by name, and then restoring it to FSX \Scenery\1104 folder.
I would have left CVX9232 intact, then CvxExtracted / Excluded / Replaced its CVX vector content via SBuilderX and ADE CVX vector files.
I also would have "fixed" GPSHydroPolygons that use a mesh-clinging attribute, by copying accurate Hydro Polygon coordinates.
In a
*.BLN extracted from FSX default CVX9232 output by
CvxExtractor, we find code used for GPSHydroPolygons within the file:
NOTE: X,Y,Z record field 3 (Z) = Altitude in Meters;
-9999 is a legacy pre-FSX "No-Data" fallback to terrain-mesh-clinging
5,1,
GPSHydroPolygons_0_0
165.234375,0,
-9999
165,0,
-9999
165,-5.36441802978516E-06,
-9999
165.234375,-5.36441802978516E-06,
-9999
165.234375,0,
-9999
Compare the above to an actual Hydro Polygon from the same extracted
*.BLN CVX vector data file:
NOTE: X,Y,Z record field 3 (Z) = Altitude in Meters;
0 forces terrain mesh to 0 Meters AMSL
5,1,
HydroPolygons_0_0
165.234375,-5.36441802978516E-06,
0
165,-5.36441802978516E-06,
0
165,-0.17578125,
0
165.234375,-0.17578125,
0
165.234375,-5.36441802978516E-06,
0
BTW: AFAIK, FSX Terrain.Cfg does not define
GPSHydroPolygon,
WaterPolysGPS or anything containing the string
GPS.
Jim Robinson
Posted February 26, 2015
I just tested and noticed an oddity at Nauru, it's like the hydro polys set at "0" are submerged or something.
I have no idea what he's talking about. It would have been nice if he had posted images showing exactly what he's talking about. I don't see any hydro polys that look submerged. If the hydro polys are set at 0, they are not submerged. If set to 0.01, that would put the poly at 0.01 meter above sea level. I don't see how setting the altitude to 0.01 meters would make a hydro poly fall into place. 0.01 meters is less than half an inch.
There are numerous areas of water visibly at Altitudes below 0 Meters AMSL adjacent to Nauru RWY; I have not checked all shorelines.
These areas 'may' render from GPSHydroPolygons used to form water that are not aligned to accurate fully SDK manageable Hydro Polygons.
These are referred to in the SDK SHP2VEC docs as "
WaterPolysGPS".
GPSHydroPolygons are "terrain-mesh-clinging, and will drape onto any area at any Altitude assigned in the terrain surface beneath them.
So, without a local flatten to 0 Meters AMSL, the water will
not be flat / level.
CVX vector hydro / water tiles must be assigned flat / level Altitudes at 0 Meters AMSL to also flatten SRTM-derived terrain mesh.
GPSHydroPolygons also require an underlying local flatten to force them to 0 Meters AMSL.
A underlying local flatten "should" be provided by Hydro Polygons normally present in CVX9232 and/or its replacement CVX Vector BGL.
Perhaps something went wrong with creation of Hydro Polygons normally present in CVX9232 and/or its replacement CVX Vector BGL?
If the "Hole" was not formed properly surrounding Nauru's land mass to separate it from the adjacent water, Hydro polys may 'fail'.
In that scenario, water displayed at run time may "fall back" to GPSHydroPolygons currently assigned to be "terrain-mesh-clinging".
I will need to examine further the CVX vectors used with the intention to create the "hole" cited above.
BTW: Nauru tides IRL, would likely not exceed 1 Meter max except with storm surges; FSX "Living Water" levels alternate +/- 1Ft. only.
Jim Robinson
Posted February 26, 2015
I see land in the entirety of both QMID cells when I tried to repeat your scenario. I've never had to do this before but I "set altitude" of .01m on the hydro polys and everything fell into place.
Again, I have no idea what he's talking about.
Why is he using QMID 11? The original cvx9232.bgl is QMID 7.
It may be that there is a quirk in the way GPSHydroPolygons "fall back" to underlying terrain mesh via FSX' rendering engine.
Perhps only
GPSHydroPolygons are displayed locally near Nauru RWY, rather than with 'accompanying'
Hydro Polygons ?
Might this be due to Hydro Polygon CVX object failure, causing them to not be flat, and not flatten terrain and GPSHydroPolygons ?
FYI: Most CVX vectors are clipped at LOD-9 / QMID-11 boundaries in the FS TMF Quad Grid system for terrain.
Only Freeway Traffic CVX vectors are clipped at LOD-13 / QMID-15 boundaries in the FS TMF Quad Grid system for terrain.
Numbered \Scenery 'Areas' contain numerous CVX BGLs, each of which are LOD-5 / QMID-7 in their extent of coverage.
By the way, did you found out anything regarding the last files I've sent you?
They are still undergoing analysis; I may be able to post more regarding my findings this afternoon or evening.
GaryGB