Bring Multi-Axis Motion into Your Games and Mods — MiraBot Motion Studio (MMS) Windows Client

A few days ago, we released MiraBot Motion Studio 1.0 and introduced its parameter-based multi-axis motion workflow in this post:

As mentioned there, the Motion Studio Windows Client is now available, together with the Developer Guide.

Motion Studio is built around the TCode protocol and is not limited to MiraBot hardware. It is also available for compatible third-party devices such as OSR2+ and SR6.

We hope this open workflow can help more developers create interactive content for the wider TCode and OSR community.

What Does the Windows Client Do?

The Windows Client combines:

  • Motion and Session creation
  • Multi-axis parameter editing
  • 3D motion preview
  • Device testing
  • A local HTTP API for games, Mods, and third-party software

A Motion is a reusable parameter-based action. A Session combines multiple Motions into a longer sequence.

Each Motion and Session has a unique Code. Your application calls that Code when an event occurs, while the Windows Client handles the motion runtime, device connection, and output.

How the Client Works

The basic development flow is:

  1. Create a Motion or Session.
  2. Preview and adjust it using the built-in 3D model.
  3. Copy its Code.
  4. Map that Code to an event in your game, Mod, or application.
  5. Call it through the local API.

That is the main integration workflow. The application decides when to trigger an action; the Windows Client handles how the device moves.

What Changes for Developers?

No Traditional Script-Making Experience Required

Developers can create multi-axis motion by adjusting parameters such as range, speed, BPM, trajectory, and phase. Separate script-editing software is not required.

Well Suited to Short Scenes and Repeating Actions

Many games and Mods use short scenes, loops, continuous states, and event-triggered actions rather than one fixed motion timeline.

Motion lets developers create these actions directly from a small set of parameters, without first preparing a complete script and then extracting or configuring individual sections.

Develop, Preview, and Debug in One Client

Motion creation, parameter adjustment, preview, and integration testing can all be handled in the Windows Client.

The built-in 3D model makes it possible to check multi-axis motion without connecting a physical device after every change, improving development efficiency and reducing unnecessary hardware testing.

Separate Application and Motion Distribution

The game or Mod only needs to retain the resource Codes and calling logic.

Supporting Motion and Session resources can be distributed separately as a Project through Motion Hub, rather than bundling script and configuration files with the application or asking users to import them manually.

Update and Reuse Motion Content

As long as the Code remains unchanged, a Motion or Session can be adjusted without changing the game or Mod integration.

The same Motion can also be reused across different events, scenes, Sessions, or projects.

:brain:What Can You Build with It?

  • Games and Mods: Trigger motion from game events, states, animations, scene changes, rhythm events, or user actions.
  • Video and Audio Experiences: Trigger Motion or Session resources from playback positions, video scenes, music sections, BPM changes, or other media events.
  • Other Interactive Software: Use it with remote-control tools, live-interaction applications, automation utilities, prototypes, and other software that needs multi-axis device control.

Downloads and Documentation

Windows Client & Developer Guide: Download :down_arrow:

The Developer Guide includes the 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.

Questions about development and integration are welcome in this thread. Please share what you are building, any problems you encounter, and the features or examples you would like to see next.:slightly_smiling_face:

:link: Links

banner723

4 Likes

Hi, this caught my attention.

I’ve been wanting to make a Mod for one of my favorite games with motion support for a while. I’ve looked at a few game-integration tools on the forum, but I don’t have much experience creating scripts, so I’ve always been a little hesitant to get started.

Motion Studio looks like it might be easier for me to approach, so I’d like to give it a try.

Before I get started, what do I need to install? If I want to create motions for my Mod, do I still need OFS or another script editor?

If I run into Motion Studio-related questions along the way, would it be okay to ask for some guidance here?

Thanks.

Thanks for your interest in MiraBot Motion Studio! :grin:
Motion Studio lets you create device motions through adjustable parameters, and you can create, preview, and test them directly in the client. You don’t need OFS or any other script-editing software just to make Motion Studio motions.
And of course, feel free to ask any Motion Studio related questions here. I’ll do my best to answer and help you integrate MMS into your Mod or application.Really looking forward to seeing what you build with it!

Thanks for the clarification. I will start by try it out with a chapter of the game and see how it goes. I may have a few questions as I get further into development.

1 Like

Does this tool have support for the handy at all? From the looks of it i couldn’t connect it up.

Thomas made their mod but i cant seem to figure out connecting my handy to the program, so im not sure if your app has support for it..

1 Like

Sorry, not at the moment.
MiraBot Motion Studio is currently designed for MiraBot and other OSR / T-Code compatible devices. The Handy uses a different control system, so it isn’t supported right now. We may look into broader device support in the future, but for now the focus is on MiraBot and OSR-type multi-axis devices.

1 Like

When connecting with Intiface Central it throws these errors, seems like something missing on MiraBot’s side to function with Intiface.

34.880 “L04439”
34.880 Got invalid messages from remote Buttplug connection - Message: Text(“L04439”) - Error: MessageSpecVersionNotReceived

It’d be good to have a global range control on the app, but a functioning Intiface connection could perhaps act as a workaround.
Would also let Handy users connect to the app.

Thanks for testing and sharing the log.
Motion Studio currently works through the MiraBot / OSR / T-Code style workflow, and Intiface / Buttplug isn’t supported yet. That error looks like a protocol mismatch rather than a simple missing setting.
I agree Intiface support could be useful in the future, especially for broader device compatibility, so we’ll keep it in mind.
For the range issue, we’ll prioritize adding a native global range control in Motion Studio / MiraPlay first.