> 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.5-february-25-march-11-2026-preview-release.md).

# 2026.5 - February 25, March 11 2026 Preview Release

## New Features

* **V-Ray 7** - Orgs can now select to render and import assets using the latest V-Ray engine for improved compatibility and forward support. *Note: New features specific to V-Ray 7 are not yet supported in the Threekit platform.*

## Improvements & Bug Fixes

* **Data Transfer** - Resolved an issue where the “Include Deleted Production Data” flag was not being honored during data transfers, preventing archived assets from being migrated.
* **Product Import** - Resolved an issue where tokens tied to an active Service Account but created by a disabled user were incorrectly treated as anonymous by auth middleware, resulting in 401 errors.
* **Renders** - Resolved an issue where V-Ray renders were saved with non-standard sRGB metadata, causing certain browsers and image processing tools to misinterpret colors and display incorrect pixel values.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://community.threekit.com/releases/2026/2026.5-february-25-march-11-2026-preview-release.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.