Thanks for the additional info, Gary. The initially-reported slope issue was due to hydro-polys not needing (or wanting) the slope=0 definition added by TS Pro. The solution was simply to delete those definitions.
Conrad, as I reported a short time ago, the current issue is two-fold. First, the vertices for hydro polys were being submitted to xml2vec in the wrong order. (TS Pro maintains all poly vertices in counter-clockwise order. xml2shp - and Flightsim - expects the vertices for hydro polys in clockwise order.) TS Pro now conforms.
But, as I reported earlier, while this put the water where it was supposed to be, the "outside rectangular area" remained and operated as a large flatten. Since TS Pro did not define any such area, its source could only be xml2shp or shp2vec - both outside my control. Upon further investigation, I discovered that your project lies on a QMV15 boundary and, in fact, the "outside rectangular area" extends over both QMV15 areas. To test whether this bisection of your project was the cause , I offset the latitude of each vertex as the project was loaded sufficient for the project to clear that QMV15 boundary. Lo and behold, the "outside rectangular area" was no longer there.
TS Pro follows the SDK recommendation of using QMV11 clipping in the absence of freeway data and there is no freeway data in your project. Nonetheless, I tried using QMV15 clipping with your project and all is well, i.e., there is no "outside rectangular area". So, it would seem that one or both of those other apps has an undocumented sensitivity to projects lying over a QMV15 boundary.
I will modify TS Pro to check for QMV15 boundary overlap and re-release later today.
Conrad, as I reported a short time ago, the current issue is two-fold. First, the vertices for hydro polys were being submitted to xml2vec in the wrong order. (TS Pro maintains all poly vertices in counter-clockwise order. xml2shp - and Flightsim - expects the vertices for hydro polys in clockwise order.) TS Pro now conforms.
But, as I reported earlier, while this put the water where it was supposed to be, the "outside rectangular area" remained and operated as a large flatten. Since TS Pro did not define any such area, its source could only be xml2shp or shp2vec - both outside my control. Upon further investigation, I discovered that your project lies on a QMV15 boundary and, in fact, the "outside rectangular area" extends over both QMV15 areas. To test whether this bisection of your project was the cause , I offset the latitude of each vertex as the project was loaded sufficient for the project to clear that QMV15 boundary. Lo and behold, the "outside rectangular area" was no longer there.
TS Pro follows the SDK recommendation of using QMV11 clipping in the absence of freeway data and there is no freeway data in your project. Nonetheless, I tried using QMV15 clipping with your project and all is well, i.e., there is no "outside rectangular area". So, it would seem that one or both of those other apps has an undocumented sensitivity to projects lying over a QMV15 boundary.
I will modify TS Pro to check for QMV15 boundary overlap and re-release later today.