How to register/unregister custom extensions when using GLTF2Exporter

[Anupam_Das]

Greetings,
I would like to register my own KHR_texture_transform extension when i export GLTF from Babylonjs to override the default behavior. It would be nice not to have to make and track my own branch of serializer (im just trying to tweak a few lines of code in KHR_texture_transform to suit our own needs).

It looks like the loader has something that does exactly what im looking for…
https://doc.babylonjs.com/features/featuresDeepDive/importers/glTF/createExtensions

but on export, I dont seem to have access to GLTFExporter.RegisterExtension as it is internal.

I guess this is a feature request but can we have access to GLTFExporter.RegisterExtension / GLTFExporter.UnregisterExtension so we can do our own extension handeling just like the loader?

@Deltakosh @alexchuber

[alexchuber]

I like the idea of being able to export your own extensions, especially since the loader already has something similar. Could you open a different thread for this under “Feature Requests” so others users can add their votes?

[Anupam_Das]

moved to feature request. Feel free to close this topic.

Register custom extensions on GLTF2Export just like the loader

The proposal is to introduce the ability to register and unregister glTF extensions during export (e.g., KHR_texture_transform). Currently, the default serializer exports several extensions, but developers might need the flexibility to override this behavior or add support for custom extensions during the export process. The glTF loader already provides similar functionality, as detailed here: Babylon.js Documentation - glTF Extensions. It would be ideal to implement comparable functionality f…

[Anupam_Das]

^^ pretty sure this is a bot lol. as there is no such thing as RegistrationAttribute and this reply makes no sense.

[Deltakosh]

agreed!!