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

# June 2025

### June 18

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

### June 18

* Added new action [**Look at**](/documentation/3d-configurator/interactions/actions/look-at.md)
* Added new condition Look at
  {% endhint %}
  {% endtab %}

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

#### Look at

* We’ve added the new [**Look at**](/documentation/3d-configurator/interactions/actions/look-at.md) action which allows objects to automatically rotate toward other elements in the scene (cursor, camera, or other objects).
* We’ve also added the **Look at** condition, enabling more precise control over interactions.
  {% endhint %}
  {% endtab %}
  {% endtabs %}

### June 17

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

### June 17

* Added support for uploading 3D files in the dashboard
  {% endhint %}
  {% endtab %}

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

#### Dashboard uploader + "new project" button

* We’ve added the ability to import 3D files directly from the dashboard — now you can quickly upload a file and generate a project link without even opening Studio.\
  More details here: <https://help.vectary.com/documentation/getting-started/dashboard#upload-3d-file><br>
* We’ve also moved the <kbd>New Project</kbd> button to a different location.
  {% endhint %}
  {% endtab %}
  {% endtabs %}

### June 9

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

### June 9

* Added [**Explore**](https://www.vectary.com/dashboard/?demo_page=true) page to the dashboard
  {% endhint %}
  {% endtab %}
  {% endtabs %}

### June 5

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

### June 5

* Fixed bug where duplicating [3D text](/documentation/design-process/design-mode/3d-text.md) caused the entered text to reset
* Fixed bug where pasting [3D text](/documentation/design-process/design-mode/3d-text.md) onto the canvas from clipboard did not work
* Fixed several issues related to [expressions](/documentation/3d-configurator/variables-and-expressions.md) in the [Set variable](/documentation/3d-configurator/interactions/actions/set-variable.md) action
* Minor bug fixes
  {% endhint %}
  {% endtab %}
  {% endtabs %}

### June 2

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

### June 2

* Improved import settings for USDZ files exported from Vectary
  {% endhint %}
  {% endtab %}

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

### June 2

* Fixed bug where changes to `Duration` in one interaction affected another
* Fixed bug where switching between `Stroke` and `Fill` tabs in [Highlight](/documentation/3d-configurator/interactions/actions/highlight.md) action reset highlight settings
  {% endhint %}
  {% endtab %}

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

#### USDZ import

We adjusted `USDZ` import so that files exported from Vectary now retain the **correct scale**. Previously, such files were imported at a **very small size**. Unfortunately, due to format limitations, this change may cause USDZ files from other software to appear oversized in Vectary. We hope to improve this behavior in the future.
{% 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/june-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.