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
How do I connect my own software to the platform?
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.
Questions
What people ask about integration.
Do I need FlyPT Mover, and is it made by ARK?
It is not ours. FlyPT Mover 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. Nor do you have to use it: a telemetry bridge is the shortest route for existing games, and if you are writing the thing that generates motion you can supply the pose yourself instead.
Which games are supported?
We do not publish a supported-title list. The titles a telemetry bridge can read are maintained by that project rather than by us, and they change; a list that is out of date costs a developer a day before they discover it is wrong. FlyPT Mover maintains its own list of supported titles, and that is the one that is current.
Is there an SDK or API documentation?
Not yet, and that is a decision rather than an omission. There is no API version table here because we do not have one in a form we have verified, and an interface document that is out of date is worse than none. The pose interface itself is real and in use; if your work needs to sit below it, that is a conversation rather than a download.
Keep reading
Motion cueing
What happens to your telemetry between arriving and being executed.
Community guides
Setup material written by people running the hardware, once Kinemaniacs opens. It is in development.
Contact
For integration questions not covered here.
Every build starts with this platform. The PDK + ARK Ecosystem finishes it — racing chassis, wheelbase, wheel, load-cell pedals and button box, $8,499.99.
Order the PDK + ARK EcosystemAll four builds ›
Made to order · Batch One: ready to ship an estimated 3–6 months from order confirmation