• 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.

FSX File Naming Convention with SplitFileLOD?

I'm doing a largish 1m photoreal with a single .inf using SplitFileLOD=9 to keep the .bgls from going over 2Gb. It works great, but there are 27 .bgls so far with filenames like this:

valles_photo_1m_03110305.bgl
valles_photo_1m_03110306.bgl
...etc

I use DestBaseFileName="valles_photo_1m_" in the .inf and SplitFileLOD appends the numbers, but for the life of me I can't figure out how they relate to any particular LOD9 cell or geographic location. Does anyone know? I'd like to be able to isolate a particular .bgl because it takes 3 hrs to resample this whole mess. I've got a couple .tifs I've changed and if I knew which .bgl is which I think I could make a cut-down .inf and only resample the .bgls affected by the changes in the .tifs. I can open them one by one in TMFViewer of course and by process of elimination (nope, that ain't it, that ain't it either... :) ) figure it out, but there must be some logic behind the numbers?

Thanks,
Jim
 

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Hi Jim,

It's the same naming convention as used for AGN files, except that these so down to another LOD level. So these numbers define the LOD tile of your scenery.
 
Thanks Arno, I thought they looked suspiciously like .agn filenames. TBH I never understood those either, lol. I get it now, QMID11 cell 313,305 becomes 03130305 in the .bgl filename. I should have caught that but I missed it completely! :oops:

That was slick, I just changed BoundingCell=7,19,19 in my .inf to BoundingCell=11,313,305 and it pooped out a new valles_photo_1m_03130305.bgl with the .tif modifications in about 5 minutes flat! I didn't remove any superfluous sources or anything, resample just ignored the ones outside the BoundingCell. Perfect!

Thanks again!
Jim
 
Top