> 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/2026/2026.4-february-18-2026-preview-release.md).

# 2026.4 - February 18 2026 Preview Release

Changes are scheduled to go to production on March 11 2026

## New Features

* **Studio Versioning** -  Production deployments will no longer auto-update with new releases, minimizing regression risk and enabling implementations to upgrade on their own schedule. Each org can select which official Studio Version is used for the player (embedded and platform), editor, and most jobs. Existing orgs will be set to the first version, which is the current state at the time of this release. New orgs will default to the latest version when provisioned. See guide [here](https://community.threekit.com/platform-documentation/org-setup/project-settings/studio-versioning.md).

## Improvements & Bug Fixes

* **Error Handling** - Resolved an issue where certain temporary service errors returned a 401 instead of a 503, which prevented automatic retries.
* **Player** - Resolved an issue in the 2d player where fully transparent configuration layers were cropped to 1×1 pixels and then downscaled to 0×0 dimensions, resulting in 400 errors due to invalid image sizing.\*\*
* **Player** - Resolved an issue in the 2D player where prefetched layer images were refetched on configuration change even if the layer images did not change.\*\*
* **Product Import** - Resolved an issue where special characters were not being encoded in tag names.

\*\*These fixes have already been deployed to production.


---

# 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/2026/2026.4-february-18-2026-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.
