Jump to content

Holger Sandmann

Moderators
  • Posts

    10,959
  • Joined

  • Days Won

    8

Everything posted by Holger Sandmann

  1. Hi there, there is no separate placement file for the custom objects in Frankfurt, they are all in a couple of _PLC_ files in \FTX_EU\FTX_EU_GES_05_SCENERY\scenery. Your options are to exclude them individually with a tool like ADE or SBuilderX, or, if you know how to do it, decompile the placement file and remove the Frankfurt buildings before recompiling. The latter approach would be pretty tedious though as the xml files work with GUID codes rather than object names. Cheers, Holger
  2. Hi there, so I checked Cape Town's default Bing ortho, wondering whether perhaps it had been updated since we released Landmarks Cape Town. It hasn't, it's still the same typical coarse Bing imagery, which is why we licensed and created the custom orthoimagery in the first place. Here's a random location in the port. While our ortho may not be a huge improvement it's definitely noticeable. Also has less shadows baked in than the default, which is particularly noticeable on Table Mountain. In any case, if you prefer the default you can simple rename or remove "sai231.cgl", in \orbx-landmarks-cape-town-city-pack\CGL\300. Note that there will be slight discrepancies in the object placements compared to the default Bing ortho. Also, in our custom ortho we've removed the footprints of vessels in the harbour and made other enhancements throughout, which you will lose by deactivating the CGL. Cheers, Holger
  3. Hi there, indeed, all our FTX regions have a set of exclusion files that cover the entire area. If removed or deactivated, this will lead to tons of duplications and other display issues across the product's coverage area. With typically several hundred airports per region, it's just not feasible to cut "windows" in the area-wide exclusions for each airport and then create separate exclusion files for it. Probably wouldn't be particularly performance-friendly either. In other words, sorry but there's only one set of excludes to rule them all ;-) Cheers, Holger
  4. Hi there, glad you're enjoying our Brisbane renditions! The two products -- YBBN and Landmarks -- differ in their extent and features between the platforms. For P3D, the airport includes riverside detail from the Gateway Bridges east, including Fisherman Island, while the Landmarks product covers the downtown area west of the bridges. For MSFS, the Landmarks product wraps all around the YBBN area and includes the port and riverside industrial areas, while YBBN is focused on the airport itself. Cheers, Holger
  5. Hi guys, as with other flightsim platforms, add-ons can suppress the content of other add-ons if they have higher display priority. Perhaps you have third-party content, or your content.xml -- the registry file for add-ons -- isn't in the correct order? For the latter, you can open content.xml, located in C:\Users\[Username]\AppData\Roaming\Microsoft Flight Simulator, in Notepad or similar and check the position of the "orbx-z-frightsimming-pack" entry. It should be below any other orbx-entries and also any third-party pack that covers the same locations. If not, you can delete the .xml file and MSFS will automatically build a new one and re-sort it alphabetically. Alternatively, an add-on manager like Addons Linker will allow you to do the same, particularly with third-party content. Cheers, Holger
  6. Hi Andy, thanks for the feedback. Unfortunately, it's not possible at the moment to alter the height or shape of the generic buildings, and we couldn't possibly custom model each of the hundreds of downtown buildings. Generic buildings are generated from Open Street Map data and anyone can contribute to improve OSM accuracy and detail. Building heights tend to be one of the parameters most in need of improvement. Thus, anyone who wants to see better downtown areas in non-photogrammetry cities can do so by improving the OSM source data before the next time Microsoft & Azure update their building database. Noted on the wake trails, we definitely want to improve on those, especially for the animated vessels. Cheers, Holger
  7. Hi Cloudhunter, make sure you update Landmarks Frankfurt; a service pack has been released since World Update VI to make it compatible. Cheers, Holger
  8. Hi there, those light-blue slivers look like tears in terrain that can open up when mesh files of different shapes overlap. Very odd that they "follow you around" though, as they generally only occur occasionally at specific locations. Not seeing anything wrong with your setup and you don't appear to be using any terrain mesh add-on either. You don't happen to have deactivated any of the default DEM mesh files in the numbered subfolders in your \Scenery\ directory? Cheers, Holger
  9. Hi guys, Fulvio, the update for Paris -- compatibility with World Update IV -- has been on Orbx Central since May 14th and on the MS Marketplace since May 21st. Or do you mean something else? For the most part, yes. There are several models that aren't ours, but all of ours have been optimized with LODs for better performance. As mentioned though, there are additional custom models and enhancements included with the original Frankfurt Landmarks that will be made available in our update, which entered testing today. Cheers, Holger
  10. Hi there, hmm, according to today's release announcement, both London and Dubai service packs for PC have made it to the Marketplace, and London also to the Xbox. If they aren't visible yet they hopefully will be soon. Cheers, Holger
  11. Hi there, also, please see https://forum.orbxdirect.com/topic/209971-frankfurt-city-compatibility/ Cheers, Holger
  12. Hi all, we are working on an update for Landmarks Frankfurt to be released soon. While many of the custom buildings are now directly integrated into the photogrammetry version of Frankfurt delivered with World Update 6, there are many more features specific to Landmarks Frankfurt that we want our current customers to retain and enjoy. Those include custom trains and boats, improvements to vegetation and night lighting, as well as a few POIs outside of the city. In the meantime, please remove Landmarks Frankfurt from your Community folder as the current version is not compatible. Cheers, Holger
  13. Hi all, my apologies for not directly responding to the request for making the helipads landeable. We'll make an effort to get this done asap, also for the hospital pads we overlooked in Landmarks Adelaide. I certainly agree that helicopters are a fun and engaging way to explore these cities, we even specifically select buildings (and vessels) to model because they have helipads. Cheers, Holger
  14. Hi there, "End of the world" is a pretty good moniker as it's literally the outer edge of the landclass-based ground textures. Beyond, a global coarse map is displayed and its hues often don't match well with those of the landclass textures, especially at mid latitudes and during specific seasons. The only "fix" is to limit visibility via your weather settings so that these sharp edges become hidden. Also see https://forum.orbxdirect.com/topic/125487-total-desert-over-all-orbx-regions-and-lc/?tab=comments#comment-1120478 Cheers, Holger
  15. Hi there, unfortunately, autogen excludes don't work on autogen placed with photoreal imagery. That's not specific to TrueEarth but rather true for all autogen that isn't placed via landclass tiles. To manually remove or alter this type of autogen requires loading the corresponding orthoimage tile into Annotator.exe, along with the correct autogen definition .xml files; see the SDK documentation of autogen placement. A work-around, if it's only a few trees or buildings, is to place small objects on top of each autogen object, for example one of the default shrubs. If those objects have their suppress-autogen flags set the autogen will no longer display. Cheers, Holger
  16. Hi Marc, thanks for the kind words! We do think of our Landmarks products as "dynamic" meaning further updates and additions are planned, though depending somewhat on how well received a given city is. Given that the original selection of custom objects is necessarily a compromise we tend to have pretty long "wish lists". I'll certainly add your suggestions to it. Cheers, Holger
  17. Hi Brian, try verifying Orbx Libraries first. It's the "product" that checks and repairs the necessary entries to terrain.cfg that are then used by Vector, openLC, the regions, etc. Cheers, Holger
  18. Hi David, in Central's options menu, under Downloader, try setting concurrency to Hard Disk Drive, which reduces the number of parallel download threads. Another tip is to prevent OC from being the only app downloading data, e.g., running a random YT movie in the background helped in my case. Not sure if you're having the same issue though; for me it was that the multiple threads somehow "overwhelmed" my modem, causing the interruptions. Cheers, Holger
  19. Hi Paul, those MSFS bgl files can actually be loaded into the TMFViewer tool from the FSX/P3D SDK to examine their content and coverage area. In this case the file contains local terraforming and object/vegetation exclusion polygons limited to northern Orcas Island and Sucia Islands. Those are the yellow polygons I've circled in red. The blue water layer I just added for spatial reference. I don't know why the freeware mesh would be affected in other areas but that's probably due to nature of how it was made, presumably one of those heightmap mesh files. Heightmaps are essentially complex terraforming rectangles meant for airports and local adjustments. Since they work at the same priority level as other terraforming polygons (unlike a MSFS native mesh file compiled to .CGL format), conflicts of this nature are inevitable. The usual workaround is to remove the mesh heightmaps in the overlap areas. Cheers, Holger
  20. Hi guys, thanks for the kind words, much appreciated. We are experimenting with better terrain data for the local mountains including the entire Cape of Good Hope area. Google Maps extracts aren't an option for us but there are other possible approaches so stay tuned. ... and once we have a better and stable terrain model for Table Mountain we can implement a proper (animated?) cable car. Cheers, Holger
  21. Hi guys, the weird thing about those hovering lights above buildings is that their appearance is inconsistent; during some of my night flights across the city there are none, during others the entire road network seems to have lifted off. Possibly related to start location and flight path but I'm not sure. It's not a local issue though as it does happen in many default areas too. What would be helpful if MS/Asobo gave us the ability to exclude or place these floating orbs; at the moment we have zero control over their position and altitude. Cheers, Holger
  22. Hi guys, thanks for the feedback. The "water glitches" on Table Mountain are actually temporary tears in the terrain itself, the light blue being the colour of "nothing" meaning no textures get applied. It happens in mountainous areas across the world, at specific view distances, and the issue has one of the longest running threads in the official forums: https://forums.flightsimulator.com/t/transparent-strips-in-the-mountains/360660 We're experimenting with different ways to remove or minimize them in this area and elsewhere; fingers crossed. Cheers, Holger
  23. Hi there, sorry, but that's the way it works in FSX/P3D when placing landclass features as polygons: we developers have zero control over which part of the tiled texture gets displayed where because that is hard-coded globally. Think of it as a planet-wide layer of golf course textures, and each golf course polygon cuts a hole into the general landclass above, revealing bits of that layer. The only other option is to place golf courses as raster landclass. That would mostly avoid cutting through features but then the golf course will appear anywhere within about a square mile of its actual location and with incorrect outlines. Given that it's usually the spatial orientation and position that pilots use to navigate visually we believe the polygonal approach is better for clearly delineated features such as gold course, towns, forestry areas, etc. If golf courses are 'your thing' then some photoreal coverage would be the better solution for you -- with its specific downsides, like lack of seasons and huge storage requirements... Cheers, Holger
  24. Hi there, it's possible to create very large ortho CGL files as long as they don't cross one of those grid cell boundaries I mentioned, in which case they would need to subdivide the product into separate layers. When covering relatively small islands, the likelihood of crossing grid cells is, of course, smaller. In any case, the developers won't be able to sell these on the MS Marketplace, at least as long as MS has that 4GB cap for any single file in a package. Note also the product sizes for their higher-resolution (probably 60-100cm) version: ~20GB just for the 850 sq km of Lanzarote! Ortho coverage for New Zealand, for example, would require more than 300 times that Cheers, Holger
  25. Hi guys, no need to go 'dude' here. Big things that can't make it up or down the tricky stretch of the 'impossible' highway get shipped in by barge. There's plenty of large equipment in Bella Coola. Cheers, Holger
×
×
  • Create New...