> 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.24.0-december-3-2025-preview-release.md).

# 2025.24.0 - December 3 2025 Preview Release

Changes are scheduled to go to production on January 7 2026

## Improvements & Bug Fixes

* **Player -** Fixed a bug that was causing nodes to disappear in the player under certain circumstances, with certain combinations of rules.
* **Vray** - The Vray Subdivision/Displacement operator was missing the Relative to BBox setting that is available in 3dsmax. As part of this bug fix, we have also exposed the global Vray Displacement settings on the Scene Settings. These settings will now get automatically added on a vrscene import as a Scene, and the settings will be populated with the settings from the imported vrscene.
* **Layered Rendering** - Fixed a bug that was causing the camera not to be included in the render when using composite assets for layered rendering, unless it was tagged. Now the camera should always get pulled into the render layers, regardless of whether it is tagged or not.
* **Logic** - Fixed a bug that was preventing the Set Model action from working correctly under certain circumstances.
* **Render Download** - Fixed an issue that was preventing certain render download jobs from completing successfully.
* **Asset Import** - Fixed a recent regression that was preventing VFBL files from being recognized as a supported file format on import.
* **Asset Import** - Fixed a recent regression that was preventing the Update option from working on imports of textures and some other asset types.


---

# 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.24.0-december-3-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.
