Progressive gltf load - preprocess url

Questions
1

I have a question about the progressive loading logic.
I can see in the inspector network tab that multiple calls are made to the same gltf file, I assume one for each LOD.
Is it possible to modify these url calls, so that each of them uses a different url? I would need this beacuse the CDN I use invalidates the gltf url after it’s called, so I would need to generate a new one each time.
I tried with loader.preprocessUrlAsync, but it doesn’t seem to do anything.

Here’s a PG: https://playground.babylonjs.com/#ARN6TJ#347
I was expecting to see logs at each LOD. Unless I’m using it wrong?

Thanks

2

ping @bghgary

3

This PG (probably modified from this doc?) loads a .glb which uses HTTP range requests on the original url. This is why it doesn’t call preprocessUrlAsync. I suppose we can call preprocessUrlAsync for this, but it might get a bit clunky.

This won’t be a problem if the asset is stored as a .gltf with corresponding external files on the server. Maybe that would be a better option?

4

Yes the PG is modified from the one in docs.
I was thinking I could maybe make a loader extension (IGLTFLoaderExtension)?

5

I don’t think that will work. There are no extension points that will allow you to intercept the HTTP range requests.

If you are sure you want to load a GLB like this, I can try to add calling preprocessUrlAsync to the code to see how it looks. Or if you are willing to contribute a fix, the code is here.