Does filament plan to support 'MSFT_texture_dds' extenstion?

[seker]

Is your feature request related to a problem? Please describe.
I’m using glTF files that have DDS textures and found out that Filament does not support them.

Describe the solution you'd like
I think it would be really helpful if Filament could add support for the 'MSFT_texture_dds' extension. That way, we could use DDS textures directly in our projects. As a solution, maybe Filament could use the GLI (OpenGL Image) library to handle DDS textures. GLI is good for this because it's made for OpenGL and supports a lot of the DDS formats.

Describe alternatives you've considered
Right now, the only other option seems to be converting the DDS textures to a different format before using them in Filament. But converting is extra work and not very convenient.

OS and backend
Adding support for 'MSFT_texture_dds' would be helpful for all Filament users, no matter what system or backend they are using.
By the way, i am using :
OS: Ubuntu 22.04.5 LTS
GPU:NVIDIA Corporation TU117M [GeForce MX450]
Backend: Vulkan

[seker]

Hello, @poweifeng, could you please answer this question?

[poweifeng]

There is currently no plan to support this extension. In my brief look at online resources, adding it seems non-trivial since it's a container format. But of course, we'd welcome contributions if this can be done by folks externally.

[poweifeng]

Commented in the PR on the team's perspective.

Copying the comment here for posterity:

@seker , after discussion with the team, we feel that it's probably best to keep this code at the client level, where you'd implement the dds provider in your code and give it to gltfio.
The reasoning is that Filament is a fairly small team, and we cannot afford to take on additional maintenance at will (like adding dep like gli). Additionally, there is already a mechanism for client's to plug in their image format encoder/decoder in gltfio. So weighing the trade-offs here we feel this work can be deferred to the client.
We appreciate your contribution, and please continue to do so. Thank you!