Our aircraft is a complex product consisting of a main package and several
additional packages (Gauge package, Liveries, FX package, Material library
pachage) These additional packages are an integral part of the product. They
cannot be installed or sold separately from the main package (aircraft ). In
the documentation, we did not find a section that describes the process of
exporting a product consisting of several additional packages. In particular,
we do not understand what kind of marketplace data needs to be filled in
additional packages. (they have no price, screenshots and can’t be visible in
marketplace as separet products) Hovewer, without this marketplace data these
packages can’t be exported. So we need additional instructions on this. Second
issue - during the export we are getting error messege “wrong_size_files” -
there no any information in the SDK documentation what does it mean and how we
can solve the problem Please advice
Assets from several packages can be combined in the single one. They can be
different types - aircraft, effects, custom data (like instruments). Usually I
do it manually by XML edits, or you can re-create asset groups in SDK editor (
Add asset group button) and copy files over.
@thealx is right: for now the solution is to merge everything into one single
package. We will provide a better solution in a future update but we don’t
know yet when it will be made available. As for the “wrong_size_files”
message, it means that the size indicated in the layout.json file is different
to that of the real file, which could create issues further down the pipeline.
This usually occurs when you edit your package files manually after building
the package which we strongly discourage (chances are a mistake will be made
somewhere and the package will be rejected at the ingestion stage). If you
believe there is another unknown reason for this message (i.e. you do not edit
files manually), we’ll have to investigate. Best regards, Eric / Asobo
Having the ability to flag some packages to be depending on others from a
licensing point of view is very important for the Marketplace in the long run.
Many developers will start to offer multiple products that might need to share
libraries of objects, textures, sounds, and it will be very useful, efficient,
less prone to errors and will even save Microsoft some bandwidth if, instead
of having multiple “fat” packages, each one including all its dependencies, a
package could be sent to the Marketplace as a “shared library for developer
xxxx”, with references to it from all the other packages the needs it, so it
will be downloaded automatically when any of the related packages are
downloaded, and can be submitted and updated separately, instead of requiring
a resubmission of all the other packages as well, which is what’s happening
today, with self-contained packages.
@thealx Could you please share how to make it with XML edits? Add asset group
button (described above) creates new sub-packages only Actually we have all
packages - we just need to assemble everything in to one (attach to main
package)
Open XML files \PackageDefinitions\your_project_name.xm l both from main
project and the one you want to merge This file contains links to the assets
(parts of the project), like this one (custom smoke effects)
VisualEffectLib
false
PackageSources\VisualEffectLibs\touchingcloud\touchingcloud-effect-jw1-smoke\
VisualEffectLibs\touchingcloud\touchingcloud-effect-jw1-smoke\
All you need to do is copy this block to the main project XML, and migrate
files from PackageSources. In this example folder to copy is
\PackageSources\VisualEffectLibs\touchingcloud\touchingcloud-effect-jw1-smoke\
ignore output dir, it will be generated automatically Then open your project
in SDK, build package, ensure new files copied into Packages properly. If
not - open logs window (`) and type folder name in search field.
@EPellissier & @thealx first of all thank you for the answers. We have
assembled all packages in to one and it is works well. We able to build it and
test in flight. But now we have faced with another issue. During procedure of
build&export; to marketplace (PC) we have CTD without any notification. I
noticed that just before the crash, the package folder becomes empty and the
only folder that is re-created contains empty marketplace data. This issue
appeared after merge of packages. Cold you please share your thoughts what can
be reason of sutch crash? I have attached screens of project and Asset Package
xml
AIRCRAFT
Mig21
GKS
GKS
true
true
Copy
false
PackageDefinitions\gks-mig21jet\ContentInfo\
ContentInfo\gks-mig21jet\
MaterialLib
false
PackageSources\MaterialLibs\gksmig21\GKS_Materials\
MaterialLibs\GKS_Materials\
Copy
false
PackageDefinitions\gks-mig21jet\MarketplaceData\
MarketplaceData\gks-mig21jet\
Copy
false
PackageSources\Copys\gksmig21\MiG-21Bis_Gauges\
html_UI\pages\vcockpit\instruments\GKS_Mig21_gauges\
SimObject
false
PackageSources\SimObjects\Airplanes\MiG-21Bis_LP_Cro1\
SimObjects\Airplanes\MiG-21Bis_LP_Cro1\
SimObject
false
PackageSources\SimObjects\Airplanes\MiG-21Bis_LP_Cze1\
SimObjects\Airplanes\MiG-21Bis_LP_Cze1\
SimObject
false
PackageSources\SimObjects\Airplanes\MiG-21Bis_LP_Cze2\
SimObjects\Airplanes\MiG-21Bis_LP_Cze2\
SimObject
false
PackageSources\SimObjects\Airplanes\MiG-21Bis_LP_Ddr1\
SimObjects\Airplanes\MiG-21Bis_LP_Ddr1\
SimObject
false
PackageSources\SimObjects\Airplanes\MiG-21Bis_LP_Ddr2\
SimObjects\Airplanes\MiG-21Bis_LP_Ddr2\
SimObject
false
PackageSources\SimObjects\Airplanes\MiG-21Bis_LP_Pl1\
SimObjects\Airplanes\MiG-21Bis_LP_Pl1\
SimObject
false
PackageSources\SimObjects\Airplanes\MiG-21Bis_LP_Rom1\
SimObjects\Airplanes\MiG-21Bis_LP_Rom1\
SimObject
false
PackageSources\SimObjects\Airplanes\MiG-21Bis_LP_Rom2\
SimObjects\Airplanes\MiG-21Bis_LP_Rom2\
SimObject
false
PackageSources\SimObjects\Airplanes\MiG-21Bis_LP_Ussr1\
SimObjects\Airplanes\MiG-21Bis_LP_Ussr1\
SimObject
false
PackageSources\SimObjects\Airplanes\MiG-21Bis_LP_Ussr2\
SimObjects\Airplanes\MiG-21Bis_LP_Ussr2\
SimObject
false
PackageSources\SimObjects\Airplanes\MiG-21Bis_LP_Ussr3\
SimObjects\Airplanes\MiG-21Bis_LP_Ussr3\
VisualEffectLegacyLib
false
PackageSources\VisualEffectLegacyLibs\gksmig21\MiG-21Bis_Lights\
effects\
SimObject
false
PackageSources\SimObjects\Airplanes\MyCompany_Simple_Aircraft_Jet\
SimObjects\Airplanes\GKS_MiG-21Bis\
VisualEffectLib
false
PackageSources\VisualEffectLibs\gksmig21\gksmig21-mig21vfx\
VisualEffectLibs\gksmig21\gksmig21-mig21vfx\
Is your aircraft installed into Community? sometimes package tool crashing sim
if same data already loaded. Only advice I have is remove asset groups one by
one to figure out which is responsible. And I would start with legacy effects
and MyCompany_Simple_Aircraft_Jet.