> 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/september-2025.md).

# September 2025

### September 16

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

#### September 16

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

### September 4

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

#### September 4

* Added new [Embed](/documentation/3d-configurator/floating-ui/embed.md) element to [Floating UI](/documentation/3d-configurator/floating-ui.md) for embedding external code and links directly into Vectary project
  {% endhint %}
  {% endtab %}
  {% endtabs %}

### September 2

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

### September 2

* Improved [interactions](/documentation/3d-configurator/interactions.md) optimization, which led to improved performance in projects with performance problems caused by interactions
* Improved resolution and performance in [WebXR](/documentation/project-settings/webxr-beta.md)
  {% endhint %}
  {% endtab %}

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

#### September 2

* Fixed issue preventing use of [variables](/documentation/3d-configurator/variables-and-expressions.md) for [Normal map](/documentation/design-process/materials-and-textures/basic-materials/normal-map.md) and [Opacity](/documentation/design-process/materials-and-textures/basic-materials/opacity.md) properties
* Fixed bug preventing AR file generation in Studio when a video texture was used in [Emission](/documentation/design-process/materials-and-textures/basic-materials/emission.md), [Roughness](/documentation/design-process/materials-and-textures/basic-materials/roughness.md), or [Metalness](/documentation/design-process/materials-and-textures/basic-materials/metalness.md) properties
* Fixed bug where AR could sometimes fail to open on the first attempt if AR files were generated in the [dashboard preview](/documentation/getting-started/workspace.md#preview-mode)
* Fixed bug where [aspect ratio](/documentation/design-process/camera.md#custom-aspect-ratio) was not applied when switching cameras via interaction
* Fixed bug causing **Hue** value to change when adjusting color in the palette
  {% endhint %}
  {% endtab %}

{% tab title="Details" %}
{% hint style="info" %}

#### Performance and WebXR improvements

We’ve improved how [interactions](/documentation/3d-configurator/interactions.md) are handled, resulting in smoother performance for projects that previously struggled with too many interactions or heavy calculations. Today’s improvement has significantly increased FPS not only when running interactions, but also while rotating the camera and in [UI](/documentation/3d-configurator/floating-ui.md) responsiveness. Projects that used to lag due to interactions should now feel noticeably faster and smoother! :tada:

This improvement has also boosted performance in the [WebXR](/documentation/project-settings/webxr-beta.md) experience.\
In addition, we’ve improved resolution in WebXR, so projects that previously opened in low resolution should now appear much sharper.
{% 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/september-2025.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.