Last reviewed 31 Jul 2026
Applies to
Banter VR Unity SDK Samples Spaces Physics Multiplayer
Difficulty Beginner

Import and Explore the Banter Unity SDK Samples

The Banter SDK package publishes two importable sample groups: Basics and FlexaWorld. The current package manifest describes Basics as a collection of introductory worlds covering Banter components, gadgets, gravity, networking, and AI-assisted world building. FlexaWorld is described as a physics playground for the SDK's FlexaBody system.

Import the Official Samples

Import one sample group from the Banter package, open its main scene, and inspect the included objects before moving anything into your own space.

  1. Open Unity Package Manager and select the installed Banter SDK package.
  2. Find the Samples section and import Basics or FlexaWorld.
  3. Open an imported scene from the project's Assets folder and inspect its Banter components.

Import a Banter Sample

Unity packages can declare samples in their package.json manifest. When a package exposes samples, Unity displays an Import control for each sample in the package details. Importing copies the sample's folder structure into the project's Assets folder.

For Banter:

  1. Confirm that the Banter SDK package has finished installing without Console errors.
  2. Open Package Manager.
  3. Select the installed Banter SDK package.
  4. Find the package's sample list.
  5. Select Import beside Basics or FlexaWorld.
  6. Locate the imported Banter sample folder under Assets.

Import only the sample group needed for the task. Both groups contain scenes and supporting assets.

Basics Sample Scenes

The current Banter SDK source contains these main scenes under Samples~/GettingStarted:

Source folder Scene file Package purpose
Basics BasicScene.unity Basic Banter space construction
Gadgets GadgetsExample.unity Example gadgets
GravityMazeExampleGame RealmsOfGravity.unity A space that manipulates gravity
Networking Networking.unity Banter networking components
World_Builder World_Builder.unity World-building workflow
World_Builder World_Renderer.unity Companion world-rendering scene

The package manifest names the broader sample group Basics even though it contains several separate folders and scenes.

BasicScene

Open BasicScene.unity first when you need the smallest entry point. Use the Hierarchy and Inspector to identify which Banter components are attached to the included GameObjects and how those objects are arranged in the scene.

GadgetsExample

Open GadgetsExample.unity when the task involves reusable interactive objects. Inspect one gadget at a time, including its components, supporting scripts or graphs, references, and child objects.

RealmsOfGravity

Open RealmsOfGravity.unity for the SDK's gravity-focused example. Compare the scene-level settings and physics objects with the standard settings used by the basic scene.

Networking

Open Networking.unity when working with shared or synchronized behaviour. Identify the networking components and any event or state connections before copying an object to another scene.

World Builder and World Renderer

The World_Builder folder contains both World_Builder.unity and World_Renderer.unity. Treat them as related sample scenes and inspect their references before moving individual assets into a different project structure.

FlexaWorld

The package manifest describes FlexaWorld as a physics-focused playground demonstrating the SDK's FlexaBody system. Its main Banter scene is:

Samples~/FlexaWorld/Banter_FlexaWorld.unity

Import this sample when evaluating FlexaBody behaviour or studying a larger physics scene. Because FlexaWorld includes supporting asset packs and many dependencies, open the main Banter_FlexaWorld.unity scene rather than assuming every .unity file in its asset folders is a Banter entry scene.

Inspect a Sample Safely

Before editing an imported sample:

  1. Open the sample scene and allow Unity to finish importing and compiling.
  2. Check the Console for missing scripts, shader errors, or unresolved references.
  3. Save a copy of the scene under a project-owned folder if you plan to modify it.
  4. Inspect the complete GameObject hierarchy before extracting a prefab or component.
  5. Copy required supporting assets and references together.
  6. Test the copied object in a clean scene before including it in a Banter build.

Imported package samples are copied into Assets, so modifications affect the project copy rather than the package's original Samples~ source folder.

Match a Sample to the Task

Creator task Sample to inspect
Learn the basic scene structure BasicScene
Study reusable interactive objects GadgetsExample
Work with non-default gravity RealmsOfGravity
Examine networked behaviour Networking
Study world-building and rendering scenes World Builder and World Renderer
Explore FlexaBody physics FlexaWorld

Troubleshooting

The Banter package does not show any samples.

Confirm that the installed Banter package is the current SDK package and that Unity recognizes it in Package Manager. Resolve package or compilation errors, then reopen the package details and look for its Samples section.

I imported a sample but cannot find its scenes.

Search the Project window for the exact scene filename listed in this guide. Unity copies imported package samples into the project's Assets folder rather than running them from the package's Samples~ folder.

An imported scene opens with missing scripts or errors.

Wait for package import and script compilation to finish, then resolve the first Console error before addressing later errors. Confirm that the Banter SDK and its declared dependencies installed successfully.

A copied sample object no longer works in my scene.

Return to the sample and inspect the object's parent hierarchy, component references, scripts, graphs, materials, and shared assets. Copy the required dependencies with the object and reconnect scene-specific references.

Official References

Related Navigation