# Creation Tips - Scene Creation

## <mark style="color:blue;">1.Overall Recommendations</mark>

It is recommended to split scenes reasonably: Avoid adding too many scenes, and avoid adding excessive assets or effects within the same scene. This can prevent performance issues such as slow loading and lag during ad playback.

Specific Production Recommendations:

* It is advised to compress asset sizes as much as possible in the first main scene. Avoid using excessively large video assets, as it can affect the completion rate of asset loading and the interaction initiation rate.
* Avoid using large videos and a large number of frame sequences, as this can impact the loading rate of assets.
* Do not exceed four videos within the same scene.

## <mark style="color:blue;">2.Global Scene</mark>

It is recommended to place persistent information in the "Global Scene" to avoid the hassle of duplicating it and facilitate centralized management.&#x20;

Persistent information typically includes product information, download buttons, and disclaimers. Depending on the specific situation, you can also place content that appears in every scene in the global scene.  [Global Settings](/playable-tools-content-editor/content-editor-user-guide/editing-page-module-intro/scene-area/global-settings.md)

<figure><img src="/files/jE4RdLKV3wAwP7kwbUb5" alt=""><figcaption></figcaption></figure>

In the settings of regular scenes, you can flexibly adjust based on the actual production needs. You can choose whether to enable Global scene in the current scene and specify whether to put it on the top or bottom layer of the current scene.

<figure><img src="/files/azcf3jmQ0Zu3iZxcdtcV" alt=""><figcaption></figcaption></figure>

For example, if you want to create a masking effect on the end page, you can choose to "put the global scene on the bottom" for a more aesthetic appearance.

<div align="left"><figure><img src="/files/f9kjNrIR8jv65BF3mEIW" alt="" width="198"><figcaption></figcaption></figure></div>

## <mark style="color:blue;">3.Scene</mark>

The core idea of scene splitting is to minimize the number of animations and events within a single scene, keep the layer structure simple (making it easier to inspect animation and event settings), and avoid adding too many scenes that can cause lag during gameplay.&#x20;

Therefore, it is generally recommended to separate <mark style="color:orange;">the core gameplay</mark> from <mark style="color:orange;">the result feedback</mark> when creating scenes.

**Now let's explain in detail using a case example:**

#### 1) Scene1: Core Gameplay

This scene showcases the core gameplay elements and provides instructions on how to interact. It clearly defines the interaction goals and guides players through the gameplay.

<figure><img src="/files/MyGFZ6r41C9d5u2h5QJr" alt=""><figcaption></figcaption></figure>

#### 2) Scene2/3/4: Corresponding Results A/B/C&#x20;

In Scene1, there are three options to choose from, each leading to a different result. Therefore, we place each result in a separate scene.

<figure><img src="/files/Uqp6lyvOR9jS6oUUOqux" alt=""><figcaption></figcaption></figure>

#### 3) Scene5: End Page

It is generally recommended to display the following content on the end page: product information, settlement details, reward information, promotional offers, and other relevant information. Additionally, it is advisable to include a button for redirection.

<figure><img src="/files/yIEHRiMYdEgDcBORGY6R" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://doc.playturbo.com/playable-tools-content-editor/content-editor-creation-tips-center/common-creation-tips/creation-tips-scene-creation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.