{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiayggljokkfvpmxgqdltgxkinrxnm3jtl56dtrtvzmex2jlhxzuia",
    "uri": "at://did:plc:dxjzgxe7cvirxkwfjr2tjspt/app.bsky.feed.post/3mijqmdnri2l2"
  },
  "path": "/t/adding-full-support-for-custom-materials-to-gltfloader/49444#post_3",
  "publishedAt": "2026-04-01T22:19:10.000Z",
  "site": "https://hub.jmonkeyengine.org",
  "textContent": "Good point. In fact, this is true for the whole `GltfLoader` and all of its subcomponents in general. You made me realize that there is no good way to access the `GltfLoader` for configuration. This makes things rather difficult for what I want to achieve.\n\nMaybe we could declare the internal list of `GltfMaterialFactory`s in the `GltfLoader` as protected. With this, one could simply extend `GltfLoader` and set up this list directly _(edit: or better by using apropriate add and remove methods)_ in the constructor. I don’t like this approach, but I currently have no better idea.\n\nBtw, `GltfLoader` already has some public configuration methods (e.g. `registerExtension(...)` and `registerDefaultExtrasLoader(...)`) that are practically inaccessible.",
  "title": "Adding full support for custom materials to GltfLoader"
}