> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/releases/2025/2025.22.0-november-12-2025-preview-release.md).

# 2025.22.0 - November 12 2025 Preview Release

Changes are scheduled to go to production on January 7 2026

## New Features

We have now added support for the [GLTF/GLB Material Variants](https://gltf-transform.dev/modules/extensions/classes/KHRMaterialsVariants).&#x20;

When trying to import a GLB file that contains material variants, the import dialog will provide an option to import those variants as well.

<figure><img src="https://631883580-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBdhnsg0wyBQ1RrM9wHPt%2Fuploads%2F6KHlsG9BYxgF2iEo5daU%2Fimage.png?alt=media&amp;token=94e7e608-8be0-434b-bf3c-337f72857641" alt=""><figcaption></figcaption></figure>

The import process will proceed to create the following:

1. It will create material assets for all materials included in the GLTF (according to the import settings)
2. It will then add a Material Variant attribute of type String to the Model or Scene containing the imported geometry.
3. The Material Variant attribute will contain the full set of Material Variants as String options.
4. A set of rules will be generated on the Model/Scene for every variant option, with Set Material actions that will apply the extracted materials corresponding to each variant.

This will therefore be a configuration ready import, where the Variant attribute can be used to switch between the Material Variants.

If you wish to control this Variant attribute from the Item level, then you will need to add this attribute on the intended parent Item, with the same set of options, so that propagation can take place.

## Improvements & Bug Fixes

* **Analytics** - Fixed "analytics.get" permissions on all tokens, to prevent 403 errors on analytics requests for tokens created by certain types of users. The 403 errors would result in a lack of analytics events getting recorded.
* **Saved Configurations** - The SessionId is now properly getting populated for all newly saved Configurations, so they can be easily matched to user sessions in analytics.
* **3D player** - Fixed a regressionwhere in some cases the webgl shaders would not load at the item level.
* **Fast Compositor** - Fixed an issue with Fast Compositor requests returning a 502 Bad Gateway error under certain circumstances, and therefore failing to generate an image.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community.threekit.com/releases/2025/2025.22.0-november-12-2025-preview-release.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
