> For the complete documentation index, see [llms.txt](https://insync.gitbook.io/interactive-studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://insync.gitbook.io/interactive-studio/spline-control/limitations-and-problems.md).

# Limitations & Problems

This page lists current limitations and known issues when using **Spline Control**, along with tips to avoid common problems.

We are actively improving the app, and many of these limitations are planned to be addressed in future updates.

***

### Current Limitations

#### Single Element Animation

> At the moment, you can only animate **one object per Spline scene at a time**.
>
> Animating multiple objects in parallel within the same scene is **not yet supported**, but this is a planned feature for future versions.

#### No Multi-Step Animations

> Currently, animations only support:
>
> * a start state
> * and a final end state
>
> You cannot define intermediate animation steps yet (for example: move → stop → rotate).
>
> More advanced multi-step timelines are planned for future updates.

#### Limited Animation Parameters

> Right now, only the following parameters are supported:
>
> * **Move (X / Y / Z)**
> * **Rotate (X / Y / Z)**
>
> Upcoming parameters will include:
>
> * Scale
> * Opacity / Fade
> * and additional transforms

***

### Known Compatibility Issues

#### ⚠️ GSAP NPM Package in Wix Studio

> If you have installed the **GSAP npm package** manually in your Wix Studio project, it may conflict with Spline Control.
>
> Spline Control already includes its own GSAP runtime, so loading another GSAP version can cause:
>
> * animations not triggering
> * unexpected behavior
> * console errors

{% hint style="info" %}
**Recommendation:** Do not install GSAP manually when using Spline Control.
{% endhint %}

***

### Performance Considerations

#### ⚠️ Large or Heavy Spline Scenes

> Very large Spline scenes with many objects, high-poly models, or heavy textures can reduce website performance.
>
> This may lead to:
>
> * slow loading times
> * less smooth scroll animations

{% hint style="info" %}
**Recommendation:** Optimize your Spline files before exporting.

* reduce geometry where possible
* compress textures
* remove unused objects

Always test performance on the live site.
{% endhint %}

***

### Spline Export Settings

#### ⚠️ Incorrect Export Configuration

> Make sure your Spline scene is exported correctly.
>
> In the Spline Export panel:
>
> * **Scrolling should be enabled**
>
> * use the **Viewer → Production URL**
>
> * do not use Public URL links
>
> Incorrect export settings may cause:
>
> * scenes not loading
> * scroll animations not working correctly

***

### If Something Is Not Working

If you experience issues:

1. Check that you are using the correct Production URL
2. Make sure GSAP is not manually installed in your project
3. Test with a simpler Spline scene
4. Republish your site and test on live

If problems persist, please contact <support@interactive-studio.io> and include:

* your site link
* screenshots of your Spline export settings
* what exactly is not working


---

# 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://insync.gitbook.io/interactive-studio/spline-control/limitations-and-problems.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.