How to save .ktx2 files?

Apologies for the late response - there isn’t yet because nobody asked for it on 2020. However I guess this will now be required when a proper livery pipeline is available.

Best regards,

Eric / Asobo

Again, apologies for the late response.

I am not sure why you disagree with the last sentence of the quoted post - if the package builder is improved so that it makes livery creation easier, how is it not “helping a portion of the customers to enjoy that very product to its fullest”?

Best regards,

Eric / Asobo

Hi @EPellissier no worries about the late response :wink: sure you have a few more topics to keep an eye on :slight_smile:
But thanks for the response, a tutorial or a step by step guide would be very helpfull.
Also helpful would be a blender plugin to import the 2024 gltf for 3D painting in blender if that would be possible.
Best Regards
Dominik

Hi Eric,

As he noted, many people who create liveries do not develop for MSFS on a 40 hour / week basis. Getting into the package builder takes a good amount of experience as there are essentially no step by step guides for even creating a project, and, absolutely no offense intended, for the uninitiated, the interface is quite obtuse unless you use it a lot.

Now, you could very easily argue that these people are not your intended audience, and there’s nothing wrong with that. Hence, why people are looking for a .ktx2 file converter outside of the package builder.

Authors provide Photoshop and GIMP livery templates all the time because they realize the marketing potential of users creating and distributing liveries for their aircraft (it also alleviates the need for them to provide liveries… everybody is happy). If you haven’t already, I highly recommend you peruse the liveries and many other packages available over at www.flightsim.to. Most liveries are done without using the package builder, because there are plenty of png → .dds converters out there. Their quality can be quite good. Without a standalone ktx2 converter, this source of addons will start to lose a lot of authors, a fun hobby for a lot of people that brings them joy.

I highly recommend you check out the work of JanKees Blom, he’s colorblind, and yet the quality of his work is amazing…

https://flightsim.to/profile/jankees

A solution like a plugin for Photoshop would be a much easier way. Or make the source available for the Asobo KTX2 implementation so others can make a tool for it. Same for the Asobo EXT_meshopt_compression btw. which added another issue for modding.

No worries. I took a long time to come back as well. Due to the time consuming nature of the indicated method for paintings, I haven’t come back to the simulator ever since (neither for flying or painting).

The response from FlyingsCool pictures well why although the improvements are welcome, it does not contemplates a lot of small creators out there, and I include myself here.

Thanks for the reponse and attention

Do we have any update on this?
I tried using
ImageToMSFSKTX2
but textures are not working, and they’re pink checked.

The KTX2 files should not make textures be pink. The base textures are not KTX2 as far as I know.

From the SDK:
" IMPORTANT : AO/Roughness/Metal (COMP) textures will be compressed into ktx2 format files when packaged by Microsoft Flight Simulator 2024 for distribution."

It sounds like you have a layout.json issue (or you’ve converted your main textures, too). You shoudn’t have “pink” textures just because the comp texture is bad, I don’t think. It should just be missing its PBR features. Unless MSFS is now checking total integrity?

I wrote this script - it simply calls the fspackagetool.exe and puts your images in a dummy project structure so the sim can compile the KTX2 files. If you are seeing pink textures I don’t think it’s caused by my script!

You might want to check if your .gltf is trying to load .ktx2 files or .dds

    "images": [
        {
            "uri": "TEXTURE_ALBEDO.PNG.KTX2"

Hey thanks, but I figured out, My layout.json was not correctly exported, so I fixed the issue by using some other “MSFSLayoutGenerator.exe” .

I hope this helps anyone facing same issue.

NVIDIA texture tools (Texture Tools Exporter | NVIDIA Developer) can write and read KTX2 files - I’ve used it extensively to create files that need customized mipmaps (as mentioned by @noolaero above), not to bypass the PackageBuilder.

When comparing the files however it becomes clear that PackageBuilder does modify some textures (particularly ground textures in my experience). As mentioned by @EPellissier it does quite a bit more than just converting the textures, which should be kept in mind when doing direct conversions through external tools.

The Asobo Kxt2 files have extensions so are not exportable using normal tools. You have to use the SDK tools to write them properly for FS24

+1; 3rd-party livery creation with MSFS2024 KTX2 files is still very low compared to what it was with 2020 (ref flightsim.to).

Technical point: the KTX2 container used in MSFS2024 looks standard to me so could be written by any ktx library if it added those Asobo key/values.

Hi,
A quick question about KTX2 files. I don’t have 2024 but a friend asked me to paint an aircraft.
Is it not possible to paint and save with nVidia tool without installing 2024?