Has anyone successfully made a livery with the paintkit? I feel like there must be missing steps. I modified a few of the files, exported all 8 to png (And also tried .png.dds), placed them in texture.N121PB in the flysimware_Cessna_414A folder (where the other texture.NXXXX folders are) and modified the aircraft.cfg file by adding the lines shown below. But the livery is completely in that pink "missing texture" appearance. What am I missing? (The "Flightsimulator cannot run..." line is in each of the sections in the original file I just didn't bother changing it)

[FLTSIM.12]
Title="Cessna 414A N121PB GTN750"
Model="GTN750"
Panel="GTN750"
Sound=""
Texture="N121PB"
KB_Checklists=""
KB_Reference=""
description="Flight Simulator cannot run because the version of Microsoft DirectX(R) installed on your computer is incompatible. Please reinstall DirectX 9.0 by running Flight Simulator Setup, or download the current version from www.microsoft.com\/directx."
wip_indicator=0
ui_manufacturer="Cessna"
ui_type="414A"
ui_variation="N121PB GTN750"
ui_typerole="Twin Engine Prop"
ui_createdby="Flysimware"
ui_thumbnailfile=""
ui_certified_ceiling=14600
ui_max_range=920
ui_autonomy=6
ui_fuel_burn_rate=13.5
atc_id="N121PB"
icao_airline=""
atc_id_enable=1
atc_airline=""
atc_flight_number="N121PB"
atc_heavy=0
atc_id_color="0x00000000"
atc_id_font=""
isAirTraffic=0
isUserSelectable=1
isFlyable=1
canBeUsedByAITraffic=1
Effects=""
atc_parking_types="RAMP"
atc_parking_codes=""

Hmmmm I think we're going to want to do it the Community folder way.

I've only glanced at the paint kit so far.  But they should all be .dds afaik.  I will try to take a look shortly.

 

Yeah - putting them in there as DDS didn't make any difference, sadly. 

38 minutes ago, Grothauser said:

Yeah - putting them in there as DDS didn't make any difference, sadly. 

You have the texture.cfg right?  It has the fallback info so you shouldn't get pink textures

Also youll need .json files for the associated .dds file

I might try this https://flightsim.to/file/27707/msfs-textures-toolbox

 

Edited March 26, 20224 yr by ryanbatc

I tried doing a community test mod for this...but it's not showing up in the aircraft livery options.  Every time I am making a new livery that no one has done it never works LMAO.  I'm missing a comma or something stupid.

I've attached my files here for anyone to investigate!

https://www.dropbox.com/s/54004gdrshxzwdk/C414_crazylines_GTN750Xi.zip?dl=0

Yeah - I have the texture.cfg - the one from the paintkit which is a duplicate of the one in all 4 of the included liveries.

5 hours ago, Grothauser said:

Yeah - I have the texture.cfg - the one from the paintkit which is a duplicate of the one in all 4 of the included liveries.

I tried as well....  I'm doing a community version but still pink textures.  We'll get it eventually!

I also tried following the instructions in the SDK documentation to build a project using my textures and the sample info from the paintkit, but it keeps erroring out on the build. I'm clearly doing something wrong, but it would be nice to get better step-by-step directions.

15 minutes ago, Grothauser said:

I also tried following the instructions in the SDK documentation to build a project using my textures and the sample info from the paintkit, but it keeps erroring out on the build. I'm clearly doing something wrong, but it would be nice to get better step-by-step directions.

I got it.  Actually, another member found a typo in my files.  I needed a PNG before the .DDS and also needed a FLIGHTSIM.0 instead of FLIGHTSIM.1 in the aircraft.cfg

See - texture 01 sheet loaded great!

Try this file and look at the folder structure.  You also need the .json files to match the DDS files for Community repaint version

https://www.dropbox.com/s/xqveimvqbtc5glr/C414_crazylines_GTN750Xiv2.zip?dl=0

workingnow by Ryan Butterworth, on Flickr

Edited March 26, 20224 yr by ryanbatc

How did you generate the layout and manifest.json files? I modified an example one with file names and file sizes for my livery but it didn't work for me. And I tried to generate a package in the SDK using my files, but I get a build error: 

PackageBuilder | Starting the build...
PackageBuilder | Generating commands for package h2air-aircraft-c414a-livery-kap...
PackageBuilder | Done, 3 asset groups registered.
PackageBuilder | Preparing asset groups...
PackageBuilder | Reading C:\FS Livery Working\KAP-C414\KAP-C414\KAP-C414.xml...
PackageBuilder | Finished, 0 skipped, 0 done and 1 failed, took 0s019ms.
PackageBuilder | Ready, 0 commands added.
PackageBuilder | Failed to spawn lister for asset group c414-livery-kap (type SimObject) (package: h2air-aircraft-c414a-livery-kap)
AssetBuilder | Could not find a valid simobject in 'C:\FS Livery Working\KAP-C414\KAP-C414\PackageSources\SimObjects\SimObjectType\c414-livery-kap'. Does it have one of [aircraft.cfg / sim.cfg / container.cfg] and does it reference the correct model folder(s)?
PackageBuilder | Preparing commands for asset group c414-livery-kap...
? false returned by Command=BuildPackages Comment=Rebuild the packages whose name correspond to the given filter, and for the given project (default fs-project.xml) NbParam=2 Line=BuildPackages h2air-aircraft-c414a-livery-kap * "C:/FS Livery Working/KAP-C414/KAP-C414/KAP-C414.xml" "C:/FS Livery Working/KAP-C414/KAP-C414" 1 1 1

Edited March 26, 20224 yr by Grothauser

I don't use the SDK at all.  For the layout json use this amazing exe program.  All you do is drag any layout.json onto the exe and it populates a new correct file.

https://github.com/HughesMDflyer4/MSFSLayoutGenerator

For the manifest I just open another one from somewhere else and add in my own data - it's a small file so easy to change.

For the .DDS json files just copy the ones right from the paints in the C414 folder... that's what I did!

OK - I'll try this out. *fingers crossed* 

So the only things you generated were png files which you converted/exported as DDS. Those went into the txture. folder along with matching json files from one of the pre-existing liveries. Then you took a copy of layout.jso and ran it through this converter. Anything I missed?

Also, I assume you will need to modify some part of it to have the 750NXi

2 minutes ago, Grothauser said:

OK - I'll try this out. *fingers crossed* 

So the only things you generated were png files which you converted/exported as DDS. Those went into the txture. folder along with matching json files from one of the pre-existing liveries. Then you took a copy of layout.jso and ran it through this converter. Anything I missed?

Also, I assume you will need to modify some part of it to have the 750NXi

Don't forget the texture.cfg - it needs to have the path of the simobjects airplane folder name.  But this is only if doing the Community way.  If you're just adding it to the addon's aircraft.cfg I guess it could just be a copy of the existing texture.cfg

Also check your aircraft.cfg - again if doing Community way it needs to say FLIGHTSIM.0 - if older way then flightsim.xx or whatever is next in order.

Just now, ryanbatc said:

Don't forget the texture.cfg - it needs to have the path of the simobjects airplane folder name.  But this is only if doing the Community way.  If you're just adding it to the addon's aircraft.cfg I guess it could just be a copy of the existing texture.cfg

Also check your aircraft.cfg - again if doing Community way it needs to say FLIGHTSIM.0 - if older way then flightsim.xx or whatever is next in order.

Question on the layout generator. It talks about dragging the json onto the exe file. I don't see an exe file in the package.

Never mind - I found it - I was downloading just the source code package, not the compiled exe