> For the complete documentation index, see [llms.txt](https://help.vectary.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.vectary.com/changelog/may-2026.md).

# May 2026

### May 20

{% tabs %}
{% tab title="Improvements" %}
{% hint style="success" %}

### May 20

* Added new [AI image-to-3D models](/documentation/other/image-to-3d-model.md)
  {% endhint %}
  {% endtab %}

{% tab title="Bug fixes" %}
{% hint style="success" %}

### May 20

* Fixed issue where [XLOOKUP](/documentation/3d-configurator/variables-and-expressions/functions.md) function was not working correctly
* Fixed issue where `Append parameters` feature in the [Link action](/documentation/3d-configurator/interactions/actions/link.md) was not working correctly
* Minor improvements and bug fixes
  {% endhint %}
  {% endtab %}
  {% endtabs %}

### May 6

{% tabs %}
{% tab title="Improvements" %}
{% hint style="success" %}

### May 6

* Added support for Gaussian Splats (.PLY)
* Added context menu triggered by right-click for importing project from **Workspace** tab
* Improved normal handling during mesh import
  {% endhint %}
  {% endtab %}

{% tab title="Bug fixes" %}
{% hint style="success" %}

### May 6

* Fixed issue where linked materials became unlinked in exported models
* Fixed bug preventing changing Smooth threshold value in Edit mode
* Fixed bug with Point light slider when using values above 100%
* Fixed UI bug with incorrect display of purple span in timeline
  {% endhint %}
  {% endtab %}
  {% endtabs %}


---

# 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://help.vectary.com/changelog/may-2026.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.