Test Tab

*Ce contenu sera bientôt disponible dans la langue que vous avez sélectionnée.

The Test tab contains tools for testing and debugging an experience, simulating multiple clients, and emulating different devices or users with regional content policies.

Test tab indicated in Studio toolbar.

Playtest Options

There are three common options for playtesting an experience. Clicking the small arrow below the main button lets you choose from each option, and sets that option as the default.

Rapid playtest options in Test tab of Studio.
ActionShortcutDescription
PlayF5Starts simulating the experience, inserting your avatar at either a SpawnLocation or coordinates of around (0, 100, 0).
Play HereStarts simulating the experience, inserting your avatar in front of the camera's current position.
RunF8Starts simulating the experience but does not insert your avatar. The simulation begins at the current camera position and you can navigate around using the Studio camera controls.

Once a playtest is running, the following options become available:

Additional options available during playtesting in Studio.
ActionShortcutDescription
Client / ServerDuring playtesting in a "play solo" mode (Play or Play Here), toggles between Client mode and Server mode. See Client/Server Toggle for details.
Pause Physics / Resume PhysicsLets you pause and resume physics without disabling rendering.
StopShiftF5Stops simulation of the experience and resets all objects and instances to how they were before Play, Play Here, or Run was clicked.

Pausing & Resuming Physics

While playtesting, the Pause Physics and Resume Physics buttons are useful for debugging ephemeral scenes and mechanisms, without disabling rendering.

Pause Physics and Resume Physics buttons available during playtesting in Studio.

By default, pausing and resuming physics acts upon both the client and server as indicated by the All notation. If you wish to pause or resume only the client or server physics, click the small arrow on either button and select Current. Then, depending on your chosen view through the Client/Server toggle, pausing or resuming will act only upon that side of the simulation.

Selection arrows for Pause Physics and Resume Physics to toggle between All or Current pause/resume action between client and server physics.

When physics is paused, you can step forward 1/60th of a second (60 Hz) by clicking the Step Forward Physics button. Like the neighboring buttons to its left, clicking the small arrow lets you toggle client and/or server steps between All or Current.

Step Forward Physics button available during playtesting in Studio, only active while physics is paused.

Note the following technical details in relation to physics pause/resume:

Clients and Servers

Using the Clients and Servers options, you can launch multiple sessions of Studio, one acting as the server and each other acting as a client. See Multi-Client Simulation for details.

Clients and Servers options indicated in Test tab

Device Emulation

The Device emulator lets you emulate various devices directly in Studio, providing insight on how controls operate on a mobile device or how on-screen UI displays on different screens and aspect ratios.

Device button indicated in Test tab

In emulation mode, you can select devices from the device selector dropdown menu above the 3D viewport to emulate less powerful devices and test streaming-enabled experiences where 3D content dynamically loads/unloads based on available memory. You can also adjust the view size and change the orientation between landscape and portrait modes.

Emulation options above the 3D viewport

Controller Emulation

The Controller Emulator lets you accurately emulate gamepad input directly in Studio. The default controller is a generic gamepad but you can select alternatives for Playstation, Xbox, and Quest devices from the upper‑left picker menu.

Emulate Device Controllers button indicated in Test tab View of the generic controller in the Controller Emulator.

While playtesting, you can control the experience with the virtual controller using your mouse.

You can also click Edit mappings in the upper‑right corner to view and edit key mappings for the virtual controller, for example E to ButtonL2 or 9 to ButtonA. These mappings are saved like other Studio settings (per controller, per user, per computer) and are translated to gamepad events in both the emulator window and the 3D viewport.

Player Emulator

The Player emulator lets you test various localization and content policies. See Player Emulation for details.

Player emulator button indicated in Test tab

Audio Mute

The Mute button allows you to mute in-experience sounds and music.

Mute button indicated in Test tab