Five quick steps lead from the project to a matched Motion Systems model - with a shareable spec sheet at the end.
Five quick steps lead to a matched model and a shareable spec sheet. Pick the project type that best matches the simulator; every following step is tailored to it.
Building a full simulator, not just the platform? Note it here - the team can point the project toward a vetted integration partner.
Each degrees-of-freedom level delivers different motion cues. 2DOF for basic feel, 3DOF for the industry standard, 6DOF for full fidelity.
Pitch / roll = tilt · heave = vertical lift · surge / sway = slide · yaw = rotation.
Pick a use case in step 1 first - then context-specific DOF guidance appears here.
Set the payload - a 15% engineering margin is added automatically - and flag site constraints early.
Cockpit weight is the structure bolted to the platform - frame and seat. Screens and controls count as peripherals. Weigh it where possible - a bathroom scale and thirty minutes beat a guess.
Building on a factory Qubic cockpit instead of a self-built rig (QS-V20, or QS-S25 / QS-S35 with the cockpit set)? Enter only the seat weight as the cockpit weight - the motion frame comes with the machine, and the seat and controls the integrator mounts count toward its max payload.
The QS-H13 seat mover is the exception: it is rated by occupant weight, not full-rig payload - the configurator applies that comparison automatically.
Sizing covers one platform - the people riding it at the same time. For several single-seat stations, size a single station here and mention the station count in the message.
Every platform ships with a perpetual ForceSeatPM license - no subscriptions. Custom builds add the ForceSeat SDK. The three cards below show which path fits the project.
A note -Not sure? The team maps the right path from the project description. See the full games list →
Based on the answers above, the wizard matches the configuration to the model that fits the project.
Pick a use case (step 1) and a DOF configuration (step 2) above - the recommendation appears here automatically.
Addressing the most frequent engineering questions and deployment scenarios.
Less than most teams expect. With ForceSeatPM, supported titles run plug-and-play - load a game and motion starts. Custom simulators integrate through the ForceSeat SDK with native Unity and Unreal Engine 5 plugins and documented APIs in C, C++, C# and Python. The M10 hardware imitator lets the software team start integration while the platform is still in production.
No - a half-filled configuration is a normal starting point. The use case, a measured cockpit weight and a rough timeline are enough; "not sure yet" is a valid answer for the motion configuration. The team resolves the open points in the first conversation and responds within 1 business day.
ForceSeatPM supports VR HeadWay / Motion Compensation to subtract platform motion from the headset tracking, ensuring the virtual cockpit stays stationary relative to the user while the world moves. This is crucial for reducing simulator sickness.
As an OEM manufacturer, Motion Systems can modify the upper frame to match specific cockpit mounting points for custom projects. On the PS-6TL series the integrator can also remove the factory top frame and bolt the cockpit floor directly to the mounting points - the full gross moving load from the model name then becomes available; the team validates the setup during scoping.
Everything that rides on the moving frame counts: the cockpit structure, the occupants and any screens or controls mounted on it. No platform ships with a seat, cockpit or sim controls - the integrator supplies and mounts those. Two Qubic units read differently: the QS-V20 comes with the 4DOF cockpit frame included, so its 150 kg max payload covers the occupant plus the seat and controls mounted on it, and the QS-H13 seat mover carries only the seat, so its 130 kg rating is occupant weight rather than a full rig. The configurator applies the right comparison automatically.
Motion Systems engineers the motion platform and its control software, not the finished simulator. For a complete build - cockpit, visuals, controls and final assembly - the team works with a network of vetted integrators and can point a project toward a suitable partner. Sharing the use case, cockpit and timeline early is enough for the team to steer it the right way.
The configurator reserves a 15% engineering margin on top of the entered payload because a platform's real limit depends on more than total weight - how far the mass sits from the pivot (its center of gravity) and how it is distributed both raise the load the actuators handle. The exception: the QS-H13 seat mover is rated by max user weight - a manufacturer limit with the margin already built in - so the occupant weight is compared directly, with no extra 15% on top.
Lead time depends on the model. The compact Qubic System line is often in stock and typically ships within 1-3 weeks; Professional Series platforms are built to order, typically in 6-10 weeks. The recommendation card shows the figure for the matched model, and the team confirms the exact date once the configuration is validated.
