Summer launch MouseMux V3 just launched. We'll be polishing it all summer with free updates, so early adopters get 25% off with code SUMMER26. See pricing
MouseMux for Aerospace & Simulation

Built for simulators.

Simulator builders were among our first enterprise users, and they still push the engine hardest. Instructor and trainee share one running scenario, each driving their own side of it, on one PC. And the hardware these rigs live on, the yokes, throttle quadrants and control panels, feeds into the same session, so the rig behaves like the real thing, not a workstation with a dozen controllers all competing for one cursor.

Running a single training rig? The Ultra licence covers commercial use for a one-time fee. For a fleet of simulators, exotic hardware and an SLA, we build the whole thing with you.

Flight & ATC trainersInstructor + traineeYokes & throttle quadrantsMulti-crew cockpitsNaval & vehicle simsRuns alongside your simCustom hardware routing
See it on the rig

Instructor and trainee, one running scenario

A normal Windows PC has one cursor, so the instructor and the trainee take turns at exactly the moment a lesson gets interesting. MouseMux gives every seat - instructor, trainee, each crew position - its own mouse, keyboard and cursor on the same running simulation, on one PC. No swapping seats, no second machine to keep in sync.

The rig's real controls feed straight into the same session: yokes, throttle quadrants, rudder pedals, HOTAS and bespoke panels, each routed to its seat, so the rig responds like the aircraft or vehicle it models. And the instructor stays in charge: pin each seat where it belongs and set who can touch what, so they can inject failures, freeze or reposition the scenario while the trainee flies it - controls a trainee should never reach.

Below: the trainee flies the approach on their own controls while the instructor, on their own cursor, fails an engine at exactly the wrong moment. Both act on the same simulation at the same instant. One PC, two seats.

FLIGHT TRAINER — Approach RWY 27 SIM RUN
SPD
142
kt
ALT
2400
ft
ENG 1 FAIL
Trainee
Instructor
One simulator workstation
Trainee flies the approach Instructor fails an engine one running scenario
Where it fits

If it teaches someone to operate a machine, we can make it multi-user

The same engine covers a two-seat desktop trainer and a full-motion rig with a crew and an instructor station. A few of the setups people run with it:

Flight trainers

Instructor and student pilot share one running flight sim, each with their own cursor and their own controls. The instructor sets weather, fails an engine or repositions the aircraft while the student keeps flying, without ever reaching for the same mouse.

Multi-crew cockpits

Pilot, co-pilot and instructor each work their own panels on one machine at the same time. Overhead, pedestal and glareshield controls stay with the crew member who owns them instead of queueing for a single pointer.

ATC tower trainers

Several trainee controllers and an instructor work one traffic picture together, each driving their own strips and displays, so a whole tower exercise runs on shared screens instead of isolated stations.

Exotic hardware rigs

Yokes, throttle quadrants, collectives, rudder pedals, HOTAS and custom-built panels route into one session, so a rig built from specialist hardware behaves like the real cockpit, not a scatter of controllers each doing its own thing.

Naval & vehicle sims

Bridge, engine-room, tank and heavy-equipment trainers put a whole crew on one running scenario, each station with its own cursor and controls, from submarine sims to driver training.

Instructor & assessment

The instructor watches, annotates and scores from their own cursor while the exercise runs, injecting the malfunctions that make a lesson, so the session stays a controlled assessment instead of a scramble for the mouse.

Built for the rig

Made for cockpits full of specialist hardware

MouseMux works at the Windows input layer, which is exactly where simulators get hard: exotic controllers, many devices at once, and a scenario that must keep running through everything a lesson throws at it.

Every yoke, quadrant, pedal set and panel becomes its own routed input in one session, pinned where it belongs, so the rig behaves like the machine it trains people to operate.

Route exotic controllers

Yokes, throttle quadrants, rudder pedals, HOTAS and bespoke panels feed into one session as routed inputs, so the rig responds like the real controls.

Pin each seat to its panels

Lock every crew position to the displays and panels it owns, so control never drifts to the wrong seat mid-scenario.

Instructor-only controls

Decide per seat who can inject a failure, freeze or reposition. The instructor station keeps the controls a trainee should never reach.

Runs alongside your sim

MouseMux is the input layer underneath, not a simulator. It sits beneath your existing sim software and makes it multi-crew, whatever engine you run.

For sim builders & training centres

We build it into the rig, then keep it flying

A single trainer you can set up yourself with the Ultra licence. For a simulator product or a training centre, we build the whole thing: seats, controls and instructor rights shaped around your sim and your hardware, integrated and hardened for daily training use.

And we stand behind it with what matters when a course depends on the rig: a support agreement, fast remote help, and a rollout that is identical across every simulator you ship or operate.

Tailored hardware routing

We map your yokes, quadrants, pedals and custom panels into the session so the rig drives like the real cockpit, not a generic overlay.

SLA & priority support

A support agreement scoped to your training operation, so a problem on the rig has a guaranteed response instead of a queue.

Easy remote support

Support staff connect and get their own cursor on the rig, fixing an instructor or crew station remotely without taking the simulator out of service.

Identical across the fleet

One seat, control and rights configuration, tested once and rolled out the same way to every simulator you build or operate.

Simulator questions

Can an instructor and trainee use one simulator at the same time?

Yes. MouseMux gives each seat its own mouse, keyboard and cursor on the same running scenario, so the instructor can inject failures, freeze or reposition while the trainee keeps flying, both acting at the same instant on one PC.

Can it route yokes, throttles and custom panels?

Yes, that is a big part of why simulator builders use it. Yokes, throttle quadrants, rudder pedals, HOTAS and bespoke panels feed into one session as routed inputs, so the rig behaves like the real controls, not a set of peripherals each acting on its own.

Can I keep certain controls to the instructor only?

Yes. Rights are set per seat: who can inject a malfunction, freeze the sim or reposition the aircraft, and who can only fly it. The instructor station keeps the controls a trainee should never reach.

Does it work for multi-crew cockpits?

Yes. Pilot, co-pilot and instructor each drive their own panels on one machine at once, each pinned to the displays and controls they own, so an overhead, pedestal or glareshield stays with the right crew member.

Is MouseMux a flight simulator?

No. MouseMux is the input layer underneath: it runs alongside your existing simulator software and makes it multi-crew, giving each seat its own cursor, controls and rights on one PC, whatever sim engine you run.

Can you build and support a simulator or a whole fleet?

Yes. We build a tailored multi-seat setup around your sim, hardware and instructor roles, with an SLA, remote support and an identical rollout across every rig. Talk to us.

Put the instructor and the trainee on one rig

Run a single training rig yourself with the Ultra licence, or let us build and support a multi-seat simulator around your sim software and your hardware.