KTX2 support for Babylon Native

Questions
1

Hi all, curious if there is any support/planned support for KTX2 on babylon Native?. We are seeing some nice advantages for ktx especially for heavy scenes, but our backend renderer (native based) need to work with ktx as well. WebP was added and that has already been great for faster network transit (thanks BJS team) @thomlucc @bghgary

1 Like
2

Hi @Anupam_Das - It is in the backlog but not for this current release. I’ll make sure to bring it up to our next prioritization discussion. Here is the issue to track: Add support for more texture formats · Issue #1479 · BabylonJS/BabylonNative · GitHub

1 Like
3

Hey! Just to clarify, do you mean loading or exporting? KTX or KTX2?

1 Like
5

@alexchuber

we mean loading ktx2 textures.

1 Like
6

Thanks for discussing this with your team. For a bit more context — the main motivation here is to reduce memory usage on mobile. As our customizers grow in complexity, we’re hitting mobile memory limits and seeing occasional crashes. Reducing GPU memory consumption could help significantly.

The push for KTX2 support in BabylonJS is so we don’t have to fall back to PNG or WebP (though those could work in a pinch). Having KTX2 supported on the backend would also ensure consistency and improve efficiency, since our instances often handle multiple concurrent rendering requests. A lower memory footprint would be an advantage in that environment.

That said, I’m also curious — in software-only rendering scenarios (without GPU acceleration), what would be the trade-offs or limitations to watch for?