Hi @bghgary .
I am sorry, after further debugging it seems this must be something specific due to the strange nature of our environment (we inject 3d content with babylon on any website with a browser extension). As there are websites with strict CSP policies (like this forum for example), we are not able to instantiate workers, that is why we are trying to make ktx2 work without workers… somehow I am seeing that our code doesn’t find the global "KTX2DECODER" although I can see that it is loaded if I just check with window.KTX2DECODER on the console.
I think this must be related to the fact of the content scripts having their own context, we will try to maybe load the babylon.ktx2Decoder.js specifically