> 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.23.0-november-19-2025-preview-release.md).

# 2025.23.0 - November 19 2025 Preview Release

Changes are scheduled to go to production on January 7 2026

## Improvements & Bug Fixes

* **Importing Assets** - There was a problem with the Material and Texture import from Model or Scene imports of FBX, GLTF, and other files, where the Update Materials and Update Textures checkboxes were not behaving as expected. This is now fixed, and in addition to that fix we have also improved the Importer Dialog to include some additional options:
  * The ability to Reuse existing materials and textures from a selected folder
  * The ability to choose which folders to reference for Reusing materials
  * The Reuse setting will look in this folder for existing materials/textures with the same name as the ones in the uploaded file, and assign those instead to the mesh nodes in the upload.


---

# 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.23.0-november-19-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.
