> For the complete documentation index, see [llms.txt](https://sdk-doc.tyrads.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sdk-doc.tyrads.com/unity/sdk-integration/1.-scene-setup.md). # 1. Scene setup Add the **TyrSDKPlugin** prefab to your scene (ideally once to your initial or bootstrap scene) from: ``` Packages/com.tyrads.unity-sdk/Runtime/Prefabs/TyrSDKPlugin.prefab ``` This enables API access via `TyrSDKPlugin.Instance` in code. ### Event System Requirement The SDK UI is built using Unity’s standard Event System (UGUI). All interactive elements (buttons, toggles, input fields, etc.) rely on an active EventSystem in the scene to function correctly. Unity UI input is processed through the EventSystem and an associated input module (e.g. StandaloneInputModule or InputSystemUIInputModule). If no EventSystem is present, UI elements will not receive input events, which may appear as if the UI is frozen or unresponsive. #### When you need to take action If your project: * Uses a custom input system, or * Does not include a default EventSystem in the scene, you must ensure that an EventSystem is available when the SDK UI is active. #### How to fix Add an EventSystem GameObject to the scene where the SDK prefab is used. Steps: 1. Create a new GameObject 2. Add component: EventSystem 3. Add one of the input modules: * StandaloneInputModule (old input system) * InputSystemUIInputModule (new input system) #### Important Notes * Unity supports only one active EventSystem per scene * Multiple EventSystem instances may cause undefined behavior or input issues * The SDK does not automatically include an EventSystem to avoid conflicts with existing project setups --- # 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://sdk-doc.tyrads.com/unity/sdk-integration/1.-scene-setup.md?ask=&goal= ``` `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.