Through a telemetry tool
For existing games, a telemetry bridge reads the title's own output and produces motion. This is where FlyPT Mover sits, and for most sim racing and flight titles it is the shortest route to moving.
Engineering · Interfaces
What talks to
the platform.
The PDK takes a pose and executes it. Getting a pose out of a game, a simulator, a research rig or your own code is the integration question — and the answer involves naming software that other people wrote and maintain.
FlyPT Mover ›Talking to it directly ›What is documented today ›
Credit where it belongs
FlyPT Mover is not
our software.
Much of what makes a motion rig usable with existing games is the work of the FlyPT Mover project, which reads telemetry from a wide range of titles and turns it into motion output. It was written and is maintained by FlyPT Mover, not by ARK Dynamics. We support it, we test against it, and some of our early development happened with its author alpha-testing our hardware — but it is theirs, and this site will not imply otherwise.
Talking to it directly
Three ways in, depending on what you are building.
The platform is a development kit, so the interface is meant to be used rather than merely supported.
Pose commands, directly
If you are writing the thing that generates motion — a research protocol, an experiment, your own engine — you can supply the pose yourself and let the platform handle the six legs. Commands run at 1 kHz — an internal command cadence, not a telemetry guarantee.
Deeper than that
The kit is a development kit. If your work needs to sit below the pose interface, that is a conversation rather than a download — tell us what you are building.
Where the documentation is
What we will not publish yet.
There is no supported-title list on this page, and no API version table. Both would be easy to write and neither exists here in a form we have verified, and an integration list that is out of date costs a developer a day before they discover it is wrong.
What will exist is the community. Kinemaniacs — where owners will publish setup guides, the configurations people are actually running, and the questions that come up when someone gets their kit on a bench for the first time — is in development. That material is written by people using the hardware, which for this kind of documentation is worth more than anything we could write in advance.
Full interface documentation ships with the kit and is expanded as the platform's software settles. If you are evaluating the PDK for a specific integration and need to know whether it will work before you order, ask us directly rather than inferring it from a page — we would rather answer the specific question than publish a general claim that turns out not to cover your case.
Keep reading
Motion cueing
What happens to your telemetry between arriving and being executed.
Community guides
Setup material written by people running the hardware.
Contact
For integration questions not covered here.