How simachines/motorbuster works
MotorBuster is a haptic-effect composition and hardware-testing toolkit. The documented workflow is to connect a controller, compose and edit effects on a timeline, then play the sequence through a haptic device; projects can also be saved and loaded. The graph includes the documented editor capabilities and the sampled WebSocket-to-engine command path. The main UI and native application source were not sampled, so links from the UI to the server are shown as unverified rather than asserted.
Main entry points: App.jsx Haptic Editor · main.py Command Dispatch · ffb_engine.py FFB Engine · inspector_panel.py Clip Inspector
Components 12
Composition and Editing
- Haptic Editor
client/src/App.jsx - Clip Timeline
client/src/App.jsx - Effect Library
client/src/App.jsx - Clip Inspector
inspector_panel.py - Native Application
native_app.py
Playback Runtime
- WebSocket Server
server/main.py - Command Dispatch
server/main.py - FFB Engine
server/ffb_engine.py
Device Support
- Haptic Controller
Project Files
- Project Files
client/src/App.jsx
Other components
- Composer
- Browser UI
Connections 11
- Composer → Haptic Editor: composes
- Haptic Editor → Clip Timeline: arranges clips
- Haptic Editor → Effect Library: selects effects
- Composer → Clip Inspector: edits parameters
- Haptic Editor → Project Files: saves and loads
- Browser UI → WebSocket Server: opens app
server/main.py - Browser UI → Command Dispatch: sends commands
- WebSocket Server → Command Dispatch: routes commands
server/main.py - Command Dispatch → FFB Engine: calls playback
server/main.py - FFB Engine → Haptic Controller: drives effects
- Composer → Native Application: launches