My first time to create a Livery Addon Package. I have done the MSFS 2020 SDK Livery Plane, studied it. But in doing mine, it will not fully compile, stating its missing a SimObject detail. This is the message I get;
AssetBuilder | Could not find a valid simobject in ‘D:\MSFS_Projects\LHC_Super_Viking_Livery_Pack_1\PackageSources\SimObjects\Airplanes\lhc-super-viking-livery-addon-pack-1’. Does it have one of [aircraft.cfg / sim.cfg / container.cfg] and does it reference the correct model folder(s)?
also…
Failed to spawn lister for asset group. Type SimObject. …
It has what the SDK LIvery Sample has. I have a Aircraft Config. Here is a sample of my entries;
[FLTSIM.9]
title =“LHC Super Viking V10”
model =“”
panel =“brown”
sound =“....\LHC_Bellanca_Super_Viking”
texture =“V Coffee and Bronze”
kb_checklists =“”
kb_reference =“TB_Reference”
description =“This is the Bellanca Super Viking, manufactured in Alexandria Minnesota. These planes were considered the Corvette of General Aviation in the United States, able to cruise at speeds around 200 plus MPH. This model variant is of the 17-300A twin turbocharged Viking model that has a ceiling of 24,000 Ft and featured a range of 700 NM. These featured a Century III autopilot and this particular build features an Asobo Garmin 500 series for NAV1 navigation, a NAV2 system, and also an ADF. This flight simulation model is packed with unique animations and details throughout. There is a manual for it in the Bellanca Manual folder in MSFS where this planes folder package is located. Happy flights!”
wip_indicator =0
ui_manufacturer =“Bellanca Aircraft”
ui_type =“Bellanca_Super_Viking”
ui_variation =“Coffee and Bronze”
ui_typerole =“Single Engine Prop”
ui_createdby =“Lionheart Creations”
ui_thumbnailfile =“”
ui_certified_ceiling =25000
ui_max_range =709
ui_autonomy =5
ui_fuel_burn_rate =90
atc_id =“N221MA”
atc_id_enable =1
atc_airline =“”
atc_flight_number =“”
atc_heavy =0
atc_parking_types =
atc_parking_codes =“”
atc_id_color =“0x00000000”
atc_id_font =“”
isAirTraffic =0
isUserSelectable =1
icao_airline=“”
What could I be missing?
I have created the folder system to be just like my plane.
It worked on mine, msfs 2020 non Beta. But it has the plane (Container) in the package. How are you supposed to know how to build a Livery Package that is not attached to the Plane? How do people compile liveries in the SDK without the planes they are for, if this system needs them. That would be flawed. Surely not…
Your effectively just placing the everything from the “airplanes” folder down, from community folder friendly package into that “copys” folder, then it will put it into a marketplace package.
So I did ‘exactly’ what the Livery Sample has, putting the plane in with the texture pack, 2 packages, and used the Sample’s dual (or 3) packages. I then found I could compile, but only one texture is produced and the sim crashes.
Can it be that this Asobo process only works with one single texture? I have 13 textures in the package I wish to export.
I also only compiled one of the two packages, the textures, not the plane. You can run ‘build all’, but I chose to just run the single texture package which is all I want.
Trying to figure out if the compiling issue was just too high on memory and crashed MSFS…
I got it to work now in 2020 SU 16 beta. Missing the core project data in the project files. Also had to do a build all from the project tab, not the inspector.
Ok, just tried it using the Build All in main project panel. I also had to delete the Package and let it make a new one. But… It only makes one texture. I have 13 in there and it only builds one folder. Also it makes the plane as well, which I can delete.
I wonder how I can get this to compile all 13 textures…
I now have it Building, but I cannot export to a Community or MarketPlace package.
Works inside the sim. All textures show up.
I tried exporting both the plane and the addon texture pack as well as just the texture pack, as that is what I need, and neither worked.
Curious… Is there a way to create a Multi-Pack Livery Package ‘manually’ that would have the built in MarketPlace section with photos/screenshots and product data? This has taken me days to get to this point, and still do not have it exported and ready for testing in the MS system.
I am curious how others are doing these that make them for planes they didnt make. How are they doing this? What is the secret to compiling a good Livery multi-pack and uploading it to the store?
So it came to me last night… The files have been compiled via the Build All function. They show up in the sim. So they are compiled and working in the ‘active’ mode when their Project is opened and active. I was thinking, all I need is to copy out that folder and create the package (manually) from that; create the folder system, install the Marketplace folders and data, and I would then have it.
Now to figure out how to run that MSFSLayout Generator and start arranging things, see if I can get a Community Version going.
How on Earth can I create the Marketplace version, lol…
It is now working…
I tried to run the Layout Generator and it said the naming system I had was too long. I renamed the package with a shorter name, and now it exports the package fine, so no need to do a Manual Build.
I have to put my model folders in this, my panel folders in this, and now my sound folders.
This is supposed to be a Livery pack. If I do not have those in the folders, it does not compile. It crashes the sim to desktop. If I put the folders in my Livery package, then it compiles. No sim crash.
The ‘Container’ (Variant) is supposed to link to the actual folder of the plane the liveries are made for. Why isnt it doing this?
I went to test the plane today in flight instead of checking their paint schemes in the Asobo hangar view mode. No sound…
Now I do not need my ‘model’ and ‘sound’ folders in there. I could have also kept the panel folders out, but thought I would just through them in there. No worries on those. It all compiled fine.
I found that if you have a crash in the compile, rename your Package folder to ‘Package 1’ (or something like that) and reboot the sim and redo the Build All once again, and it should all go smoothly, hopefully.
