Jump to content

Holger Sandmann

Moderators
  • Content Count

    10,769
  • Joined

  • Days Won

    7

Holger Sandmann last won the day on January 3 2016

Holger Sandmann had the most liked content!

Community Reputation

1,077 Excellent

11 Followers

About Holger Sandmann

  • Rank
    Geospatial Lead
  • Birthday 02/16/1965

Profile Information

  • Gender:
    Male
  • Location:
    Sidney, BC, just east of CYYJ

Recent Profile Visitors

7,671 profile views
  1. Hi Michael, no news yet but I'll check with the "bridge maker". Cheers, Holger
  2. Hi there, actually, Vector's "airport elevation corrections" didn't really correct anything, they simply removed Vector's own version of the selected airport(s) to avoid compatibility issues with third-party airports. Since Vector in v5 doesn't include airports of its own anymore, adjusted or otherwise, any visual conflict now is between the default airports and your add-on, or more than one add-on airport active at the same time. With P3D v5 Lockheed Martin fixed the long-standing bug that prevented different airport reference altitudes from being influenced by relative position in the scenery library. Now, the add-on with highest priority will have its reference altitude used, as intended. If the airport doesn't display correctly then its local flatten polygons are somehow suppressed or overwritten. Make sure that no other add-on sits at higher display priority that might exclude or overwrite those files. Cheers, Holger
  3. Hi petfy, the fact that the seam/line moves ahead of the aircraft is due to the sim's LOD (Level of Detail) system; the lighter-colored seam in my screenshot above does the same. The color "shift" is actually a change between different landclass types with the same content but slightly different coloring. When we worked on manually placing landclass across Australia's 10 mio sq km more than a decade ago we had different people assigned to different areas and thus their selection of landclass types varied sometimes. For AUv2 we reworked many of the more obvious boundaries but it's still not going to be perfectly seamless everywhere. In any case, the landclass doesn't have anything to do with the dark seam and I still don't know what it might be as I don't see it myself. At a distance the display of the landclass tiles actually gets replaced by a coarse synthetic satellite image; at cruising altitude and with clear weather one can often see the sharp boundaries to this image, especially if hue and brightness are noticeably different. However, I don't believe that is the issue here as the line in Rick's screenshots is much closer to the aircraft than the satellite image would normally display. Another possibility is that it's a corrupt file associated with a specific add-on; sometimes these issues are seen thousands of miles away from the airport. To test that you could temporarily deactivate anything other than AUv2 in the scenery library. Cheers, Holger
  4. Hi guys, I went to the same area but don't seem to be able to replicate this, in either P3D v4 or v5. The location where the line appears is a boundary between P3Ds internal grid tiles. Along those boundaries there's always a bit of a visible seam, as in my screenshot, but not normally as a dark line in your respective screenshots. Are you using any other add-on that covers Australia, like a global mesh package? Also, have you noticed any correlation with specific display slider settings? Cheers, Holger
  5. Hi there, it's an ongoing process, and a tedious at that. I've just added the patch information for FTX GEN; Germany South and Norway are next. Cheers, Holger
  6. Hi there, if you load "FTX PNW Coverage and Features Map.kmz" into Google Earth you'll see that the markers include a separate category for "BC: unlisted/abandoned airstrips" and CBL9 is one of them, among 20 or so more, including Chaunigan Lake and Chilko Lake North. As the category implies these airstrips either don't have an official ICAO or have since been unlisted. Thus, they don't have airport facilities files and therefore can't be selected from the airport list. They do exist in the sim though, with PNW installed, and are meant to be discovered by flying to them. if you don't want to go hunting you can use the coordinates from the GE marker and copy&paste those into your FSX Map view to "teleport" to the location. Cheers, Holger
  7. Hi there, I can tell from the first screenshot that those objects aren't autogen but rather custom "generic" buildings usually found in the vicinity of airports, which actually suppress the local autogen. At and around default Airports around the globe, P3Dv5 has added a lot more of those, which may be what you're noticing. As Nick states though, without coordinates accompanying the screenshots we can't double-check on our end. Cheers, Holger
  8. Hi there, as far as the Salt Lake City "issue" is concerned please see here; https://orbxsystems.com/forum/topic/133217-persistent-winter-textures-aec-utility-issue/?do=findComment&comment=1183586 Cheers, Holger
  9. Hi there, files with those names don't exist anywhere within my PNW source files so it seems to be a misnamed texture within one of the model library files. If it was a commonly used file one would see black textures but I don't recall any reports of those so I'd say it's safe to ignore. Cheers, Holger
  10. Hi guys, thanks, this will be fixed in an upcoming service pack for FSX/P3Dv3/4. It's already been fixed with the recent compatibility service pack for P3Dv5. Cheers, Holger
  11. Hi there, if the problem area is in between PFJ and SAK then it could be that you have Tongass Fjords X installed but not properly configured. See https://return.mistymoorings.com/faq/ about three quarters down the page. Cheers, Holger
  12. Hi there, your scenery library looks odd because there should be four entries for Southern Alaska (SAK) but I'm only seeing two. Either it's an issue with the Scenery Library Manager or your installation of SAK is incomplete. For the latter you could run a Verify Files check in Orbx Central. SAK and PAJN have been checked for P3D v5 and are compatible. Cheers, Holger
  13. Hi there, KMPI is one of those airports with a changed ICAO in P3D v5, it used to be O68. Thus, with FTX NCA installed, there are two superimposed versions at different altitudes. This will be fixed in an upcoming service pack for NCA; please watch this thread: https://orbxsystems.com/forum/topic/192142-ftx-region-updates-for-prepar3d-v5/ Cheers, Holger
  14. Hi there, FYI, southern Oregon is actually included with FTX Northern California. With that region installed the default bug of the sunken part of Klamath Lake is gone. Cheers, Holger
  15. Hi there, if you have the P3D SDK installed then you can use its TMFViewer.exe tool to load any mesh bgl file and determine its compiled resolution using View > Level of Detail. The raster resolution values associated with a given LOD are listed here: http://www.prepar3d.com/SDKv5/sdk/world/terrain/terrain_overview.html#QMID and LOD Values Thus, LOD11 is about 19m per pixel, LOD10, about 38m, etc. PILOT'S mesh files are split into the standard QMID7/LOD5 tiles, which use a sequential naming system of columns and rows, starting at N90 W180; for a basic map that helps to determine the local file name see http://www.prepar3d.com/SDKv5/sdk/world/terrain/terrain_overview.html#Base File Information Cheers, Holger
×
×
  • Create New...