> 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.7.5-may-27-2026-release.md).

# 2026.7.5 - May 27 2026 Release

## Improvements & Bug Fixes <a href="#improvements-and-bug-fixes" id="improvements-and-bug-fixes"></a>

* **Configurations** - Resolved an issue where the first change of an attribute returned an error due to configuration updates being evaluated before the latest attribute selection had fully propagated through the scene graph hierarchy.
* **Infrastructure** - Reduced the delay between WebGL Renders being requested and new workers starting up.
* **Jobs** - Resolved an issue where the export-paths job was considered successful despite errors, resulting in empty SVG files.
* **Plugins** - Resolved an issue where element Ids were not accessible from the player API.


---

# 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.7.5-may-27-2026-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.
