• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

What tolerance is in Scenproc for (not quite) right angles and paralel lines?

I used both the Smooth and Simplify options individually and in combination and found that Smoothing and simplifying in combinaton had the same result as simply simplifying. I haven't done the oversampling thing tho, will give that a go. My image is 210,000 by 180,000 pixels as it is, but I can break it down into many smaller chunks if I have to. I have a Multi-layer PSB file that is 100GB in size, so the PC should handle a 400MB LZW compressed TIF exploded a bit.

Ideally I could have taken background images at LOD20 instead of LOD17 in SbuilderX, but then I'd have had hundreds of images to geo-reference and been manually downloading them all (and unloading and reloading the background and redefining the download area several times for each when it stalls on the last few tiles). Scenery development can be tedious, but that would be just soul destroying...

cheers

Braedon
 
Hi Braedon:

That looks like a very large data load to keep in (1) *.PSD file ! :yikes:


FYI: SBuilderX creates a 1-piece BMP and a matching TXT Geo-referencing 'world' file when one performs these steps:

1.) SBuilderX Menu > File > Add Map > From Background ...

2.) Select desired aerial imagery area, then download all tiles as directed in "Add Map From Background" dialog

3.) Select desired aerial imagery area from resulting aerial imagery Background displayed in SBuilderX work-space

4.) SBuilderX Menu > File > BGL Compile ... < DO NOT 'click' [Compile] button >

5.) SBuilderX pre-assembles a 1-piece aerial imagery BMP and a matching TXT Geo-referencing 'world' file in:

[SBuilderX install path]\Tools\Work\ sub-folder

...without having actually compiled a BGL. ;)


The resulting BMP and its matching TXT Geo-referencing 'world' file can next be imported into ScenProc via "ImportGDAL":

https://www.scenerydesign.org/2014/01/import-resample-configuration/

...and then exported as a GeoTIFF via "ExportImage". :pushpin:


Possibly GeoTIFF files might prove a bit easier to manage in discrete assigned sub-folders ? :scratchch


NOTE: Although a TIF source file working set size processed by MSFS SDK Resample 'may' approach 4 GB in size in a 64-Bit Windows CMD mode task session, Resample can only create BGLs up to 2 GB in size.

Additionally, if TIF LZW compression is used, the source file working set size may double that of the aerial imagery TIF file size on disk, and could still result in a failure of compilation, as the output BGL might otherwise have exceeded 2 GB in size.

In some cases compilation of a larger submitted volume of source data within a working set may succeed when the INF file requests Resample to apply compression to the output BGL.

For example, a Resample compression level of "85" correlates with an approximately 40% reduction in output BGL size (...but may visibly reduce FS run time perceived quality of one's custom aerial imagery display).


Even if Resample tolerates the submitted volume of source data within its working set, the processing of TIF files using LZW compression reportedly can take a much larger time to complete than it does with non-compressed aerial imagery source files. :alert:

http://www.fsdeveloper.com/forum/threads/resample-cm-pixel.13637/


IMHO, it may prove more manageable to keep ones custom aerial imagery scenery source files in smaller sized tile groups in separate sub-folders. :idea:


BTW: Arno has some interesting ideas for working with folders containing many aerial imagery source files: :wizard:

https://www.scenerydesign.org/2013/06/nantucket-photo-scenery/


Hope this helps a bit more ! :)

GaryGB
 
Last edited:
The image is large to get consistency of colour correction across the whole area. I then break it down into 20 areas that are small enough to be exported by Photoshop then bring them into Global Mapper and carve them into about 55 georeferenced, uncompressed TIF images. Same again for the Blend and Water masks (The process is a bit more stramlined than that). I then pass the 150+ sources through resample and voila.

The most tedious step is getting all the tiles and masks out of photoshop because the tools that would automate the slicing (eg. the web slice tool) are not designed to work with anything on the scale of GIS imagery.

upload_2017-7-15_20-34-42.png



If I could get PS to slice it up into tiles automatically it would save a lot of time. If i had a lot of tiles that I worked on separately, the tedious bit would be synchronising adjustment layer changes across all the tiles, and making sure that what works on one tile doesn't have an undesirable adjustment on another.

I'm trying the oversample technique you mentioned now.

cheers

Braedon
 
Last edited:
You must log in or register to reply here.
Back
Top