question

Hi,

we're facing the same problem. Our CGL file is > 1 GB, so we cannot publish our add-on for the Xbox and reducing the quality is not an option. We already reduced the quality to be able to meet the 4 GB limit.

Someone on the Marketplace team told us that they've seen other developers split the CGLs into multiple files to work around the file size limit. While we can split the files, it remains unclear how to put them in the same package. Has something about this changed since July?

Kind regards

Following. Additionally it would help a lot not to be stuck to LOD20 in terms of aerial imagery, so the filesize of the CGL could be reduced considerably for some projects - particularly away from the immediate airport vicinity.

Just curious, I've been trying to find the limitations that references this. Is this limit still a thing, and if so, does anyone have a link? I assume this file size is of the extracted package as well.?

Hi all,

Can anyone please elaborate on these two choices indicated earlier;

-splitting into two separate packages, means we need to publish two scenery packages (ie, as A-West, A-East) ?

That doesn't seem preferable for an airport project. Is there another way to do that?

-reducing quality of what exactly in order to reduce cgl size, how?

Thank you

Hi!

We are also stuck on this. Does anyone have a clear explanation of whether splitting one large aerial imagery CGL into several adjoining ones (forming a mosaic of CGLs) works?

We have a large aerial imagery covering 170 sq.km., for a total CGL size of 4.4GB.

• This works fine for non-Marketplace vendors, in fact, our product is out already with 2 3rd party vendors.
• The problem is that when we try to create a package for MSFS2020 Marketplace, we get the "over 4GB limit" error.
• To address this, we can split the scenery into 2 (or more if needed) components which are within the SAME package (@Orcusiok @Sunay, to answer your question, you don't need 2 separate packages, all you do is, set up your project to contain 2 or more CGL asset groups, with the output pointing to different folders whose names MUST contain "CGL", in our case "CGL_NORTH" and "CGL_SOUTH") (this "MUST contain CGL in the name" requirement popped up as an error in the console while we were figuring out how to do this)
• This project set up results in a single package, containing two CGL components in separate folders. The RESULTING layout.json then looks like this:
  
  

  {
    "content": [
      {
        "path": "CGL_NORTH/300/sai110.cgl",
        "size": 182002528,
        "date": 133113881906400486
      },
      {
        "path": "CGL_SOUTH/300/sai110.cgl",
        "size": 325773245,
        "date": 133113882842953733
      },
      {
        "path": "ContentInfo/photoreal-project/Thumbnail.jpg",
        "size": 118977,
        "date": 133107878906204924
      }
    ]
  }

While this works on the compiler side (as in "Build All" command produces the package without any errors), the produced scenery package simply does not work, either causing a freeze, CTD or no-show in the area.

We've seen users successfully splitting their CGLs as per above, but we are unsure if these were aerial imagery projects or something else. So, does anyone know if there are any limitations on multiple aerial imagery CGLs existing side-by side, as a mosaic, comprising a large coverage scenery area?

Thanks!