> 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.4-may-20-2026-release.md).

# 2026.7.4 - May 20 2026 Release

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

* **AR** - Resolved an issue where AR generation could fail with a “No geometry to export” error when exporting a model using a stored scene graph state.
* **Renders** - Increased GPU-based WebGL render worker capacity.
* **Rules** - Resolved an issue where Rules using the “has changed” condition on Asset Attributes did not trigger when scenes were viewed through an Item with linked Asset Attributes.
* **Rules** - Resolved an issue where conditions using Array Attributes incorrectly displayed warnings indicating the Attribute had been deleted.


---

# 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.4-may-20-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.