Motion Studio 1.0 Windows Client Is Now Available

Create, preview, and integrate parameter-based multi-axis motion for games, Mods, video, audio, and other interactive software.

Following the release of Motion Studio 1.0 on MiraPlay Web, the MiraBot Motion Studio Windows Client is now available, together with the official Developer Guide.

Motion Studio is designed for TCode-based multi-axis devices. In addition to MiraBot, it can also be used with compatible third-party devices such as OSR2+ and SR6.

Create Multi-Axis Motion with Parameters

Motion Studio provides a parameter-based workflow for creating multi-axis motion.

Instead of defining an entire movement as a long sequence of individual position points, users can create a Motion by adjusting parameters such as:

  • Motion range
  • Speed and BPM
  • Trajectory type
  • Phase
  • Eccentricity
  • Participating axes

Multiple Motions can also be arranged into a Session for longer sequences, staged content, or video and audio timelines.

The Windows Client includes the complete Motion and Session creation workflow, motion curves, 3D device preview, Project management, and Motion Hub access.

Built for Games, Mods, and Third-Party Applications

The main addition in the Windows Client is its local motion runtime and HTTP API.

Each Motion and Session has a unique Code. A game, Mod, or other third-party application can call that Code when an event occurs, while the Windows Client handles:

  • Loading the selected Motion or Session
  • Interpreting the multi-axis parameters
  • Managing the current run state
  • Connecting to the device
  • Sending the resulting motion output

This allows developers to keep motion content separate from the application code. The application only needs to decide when an action should occur and which Motion or Session should be called.

A Simple Development Workflow

The basic integration process is straightforward:

  1. Create a Motion or Session in the Windows Client.
  2. Preview and adjust the result using the built-in 3D device model.
  3. Copy the resource Code.
  4. Map the Code to an event in the game, Mod, or application.
  5. Call the resource through the local API.

Motion creation, preview, device testing, and integration debugging can all be handled within the same client.

Supporting Motion and Session resources can also be published as a Project through Motion Hub, allowing users to obtain the resources separately from the application itself.

What Can It Be Used For?

Games and Mods

Trigger Motion or Session resources from game events, character states, animations, scene changes, rhythm events, or user actions.

Video and Audio

Use video timelines, playback positions, music sections, BPM changes, or other media events to trigger motion content.

Other Interactive Software

Integrate Motion Studio with remote-control tools, live-interaction applications, automation utilities, prototypes, and other software that requires multi-axis device motion.

Download and Documentation

Motion Studio Windows Client & Developer Guide : Download

The Developer Guide covers the available local API endpoints, request and response formats, Motion and Session calls, runtime controls, integration workflow, debugging guidance, and development examples.

We welcome game, Mod, and third-party application developers to try the Motion Studio Windows Client.

Development and integration questions are also welcome in our community discussion thread.

Shopping Cart