MSFS24 Textures won't compile

[TBryson2]

I also am running into an issue where ONE texture (and its associated normal map texture) simply will NOT compile into the finished scenery. Not sure why, it works fine for 2020, but not 2024. ALL of the other textures will compile properly.

Believe me, I would rather find out WHY my files are not compiling properly, but this allowed me to continue the project and stop spending days trying to figure out why they would not compile. In my case, I'm creating an airport, and the missing files are for a complex terminal with many parts and textures. I'm sure someone out there will have an issue with my technique, and may be able to improve on it, but it got me past a roadblock.

To get around this issue, I downloaded "Image to KTX2 texture script for MSFS 2024 livery creation - ImageToMSFSKTX2" from Flightsim.to This allowed me to compile the two wayward image files into KTX2 format AND create the associated .json files. I then plugged them into the texture folder and modified the layout.json file to reflect the files in the texture folder.

It gets a bit tricky, especially if you're not done with your project, because you HAVE to do this each time you compile your project. The steps I follow are,
1. Use the utility above and compile any images and .json files you need and place them in a unique directory.
2. Compile your project as you normally would
3. Go into the finished PACKAGES /.. /... texture folder and see if they actually compiled.
4. IF, or whatever files you need are missing, copy them from the ones compiled utility and paste them into the PACKAGES / ... /... texture folder
5. THEN, find the "layout.json" file for your project in the "PACKAGES" folder
6. DRAG that "layout.json" file into MSFSLayoutGenerator so that it updates the previously missing files into the layout.json file

I then copy the finished project (from the Packages folder) into my Community folder and it seems to work out for me.

TB2

 

[danielsjam]

Attach the texture files (I assume diffuse, normal and maybe AO) that you're having an issue with and let others take a look. I will also try Image to KTX2. I found LiveryConverter2024 that is about the same.

 

[TBryson2]

The "normal" map does not look like a "normal" map should, and I'm not sure why, (haven't researched it), but it seems to meet my needs and looks appropriate when applied.

TB2

 

[danielsjam]

I used your textures with the 1.3.3 exporter in Blender 3.4.1 and it works just fine. I tried using the textures in a project using exporter 3.3.2 in Blender 3.6.22 and none of the textures will export. The strangest thing is, I loaded a project that I used for an airport that I already released and none of the textures in that project will export now. I'm not sure if this is a problem with the new exporter or my version of Blender. I tried using exporter 1.3.3 with Blender 3.6.22 and it did export the textures including yours. The images attached shows what happened in Blender and to the exported file after using 1.3.3. The image with the blue background is from Model ConverterX, and grey is Blender. There are no LOD's in this project. According to the documents, you can have both versions of the exporter installed in the same Blender but not with both active at the same time. I will say that 1.3.3 does not work in Blender 3.6.22. I think I'm going to do a clean install of Blender, because for my latest upgrade, I imported all my settings and scripts from the previous version.

 

[TBryson2]

I used your textures with the 1.3.3 exporter in Blender 3.4.1 and it works just fine. I tried using the textures in a project using exporter 3.3.2 in Blender 3.6.22 and none of the textures will export. The strangest thing is, I loaded a project that I used for an airport that I already released and none of the textures in that project will export now. I'm not sure if this is a problem with the new exporter or my version of Blender. I tried using exporter 1.3.3 with Blender 3.6.22 and it did export the textures including yours. The images attached shows what happened in Blender and to the exported file after using 1.3.3. The image with the blue background is from Model ConverterX, and grey is Blender. There are no LOD's in this project. According to the documents, you can have both versions of the exporter installed in the same Blender but not with both active at the same time. I will say that 1.3.3 does not work in Blender 3.6.22. I think I'm going to do a clean install of Blender, because for my latest upgrade, I imported all my settings and scripts from the previous version.

I guess I should have included what I'm exporting with and Blender version but didn't think of it at the time. My issue happens when exporting into MSFS 2024 only, and I'm using exporter version 2.3.3 for MSFS 2024. Blender version is 3.6.21. I have not tried using 1.3.3 exporter for MSFS 2024. I have not had any issues with any of the textures in my project (and there are many), other than this one. Thanks for tinkering with it.

TB2

 

[danielsjam]

OK I tried again with exporter 3.3.2 and 1.3.3 but this time I changed the export directory to D:\Temp and it works with my original project and your textures. It seems that exporter 3.3.2 and 1.3.3 is picky about where you export using Blender 3.6.22- at first I was trying to use Desktop\Temp which didn't work, I guess because it's in my home directory and need some special permissions. Both exporters worked just fine using D:\Temp.