> 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/aura-suite/limitations-and-problems.md).

# Limitations & Problems

This page lists current limitations and known behaviors when using **Aura Suite**, along with important notes to avoid confusion during setup.

We actively improve the suite, and some of these limitations may change in future updates.

***

### Current Limitations

#### Only One Cursor at a Time

> Aura Suite currently supports **only one active cursor style at a time**.
>
> This means you cannot combine:
>
> * a WebGL background cursor
> * and another foreground cursor
>
> Using multiple cursors simultaneously is only possible through custom code and is not supported by Aura Suite at this time.

#### Only One Overlay at a Time

> You can apply **only one overlay effect at a time**.
>
> Layering multiple overlays together (for example grain + grid) is not supported through the UI and would require custom code.

***

### Page Duplication & Templates

#### Effects Not Visible After Duplicating Pages

> If you duplicate a site or create a new site from a template, Aura Suite settings will not automatically appear on that new site.
>
> To apply the effects:
>
> 1. Open **Aura Suite** from the Editor Add-Ons menu
> 2. Wait a moment while settings are synced
> 3. The app will automatically generate a new script file for the page
>
> After that, all selected effects will work normally.

***

### WebGL Cursor Requirements

#### Transparent Background Needed

> WebGL cursors are rendered **behind the page content**.
>
> To make them visible:
>
> * the **page background must be transparent**
> * the **section background must also be transparent**
>
> If either background is solid, the WebGL cursor will not be visible.

***

### Text Animation Class Usage

#### Entrance & Scroll Classes

> CSS classes for:
>
> * entrance animations
> * normal scroll animations
>
> can be applied to **multiple elements on the same page**.
>
> This allows you to reuse the same animation style across many text elements.

#### Sticky Animation Classes

> Sticky animation classes work differently.
>
> On each page:
>
> * the **sticky class** can only be used once
>
> * the **sticky-trigger class** can only be used once
>
> If you want multiple sticky text animations on the same page, you must:
>
> * create multiple sticky animations
> * use different class pairs (e.g. `sticky-001`, `sticky-002`, etc.)

{% hint style="info" %}
You can reuse the same sticky class again on a **different page**, just not multiple times on the same page.
{% endhint %}

***

### Browser & Device Restrictions

#### Effects Disabled on Some Devices

> Some effects may be automatically disabled on:
>
> * Safari
>
> * mobile devices
>
> * low-performance devices
>
> This is done intentionally to prevent:
>
> * stuttering
> * excessive battery usage
> * poor scrolling performance

{% hint style="info" %}
Our goal is to always prioritize usability and smooth experience over visual effects.
{% endhint %}

***

### If Something Looks Wrong

If effects are missing or not behaving as expected:

1. Open the Aura Suite panel to force sync
2. Click **Save** again to regenerate scripts
3. Republish your site and test on live
4. Check background transparency for WebGL cursors

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

* your site link
* device and browser info
* which effect is not working