Thank you for the new feedback! I plan to make a video how-to this week. I’ll try to answer your doubts as well as possible:
-
Sometimes, I stumble upon a bug while using the software. It happened with the Savage Cub (for which I’ve made revision 1.6.2), and it happened again with your tip on the F/A-18. I’ll look it better and create a new revision shortly. While this doesn’t happen, you can use the “Convert DDS file” to extract the textures inside the “texture” (or “texture.something”) folder. If there is a missing texture, you should look at the fallbacks inside the “texture.cfg” file, until I create the revision. This button should be used to convert textures from liveries without a model file too.
-
The airframe textures can usually be extracted using the corresponding airframe model. E.g.: Extra-330 has a “E330_LOD00.gltf” for the exterior view and a “E330_interior_lod00.gltf” for the cockpit view – “E330_LOD00.gltf” should be used to get the exterior textures. Let me know if it doesn’t happen with another aircraft, giving the details.
-
As for the payware, I need at least a screenshot of the related folders. If it doesn’t have separate texture files, this tool won’t be able to extract the textures now – I theoretically know how it should be done, but I don’t have anything to test on, and testing a generic glTF file with embedded textures may not work, since Asobo extensions are very peculiar.
-
This software has no use case in which you should select “.bin” files directly.
I’m sure you know how transparency works. I only said all that because it isn’t immediately clear how those files are used in the models and there are at least two use cases (one to simply define colors, the other with a more classical texture map), and both live outside the main fuselage and wing texture files. It may help some users, not necessarily you.
Once again, thank you for the feedback, It is an invaluable contribution!