Motion simulation software What talks to
the platform.

The Portal Development Kit (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

FlyPT Mover ›Talking to it directly ›What is documented today ›

The signal path from a game's telemetry output through the cueing stage to the platform's six legs.

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. Some of our early development happened with its author alpha-testing our hardware, but it is theirs: ARK does not maintain or support it, 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.

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; which titles it reads is FlyPT Mover's to decide.

Kinemaniacs, in development ›

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. Your poses run at the platform's 1 kHz game-to-motion rate — a command rate, not a telemetry rate.

Deeper than that

The kit is a development kit. Work below the pose interface is not part of what the Kit supplies.

Contact ›

Where the documentation is

What we do not publish.

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.

Kinemaniacs, a community where people using the hardware may share setup guides and configurations, 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.

Interface documentation is supplied with the Kit in the state it is in at dispatch. Whether the PDK works with a specific integration is for you to test; ARK makes no compatibility promise for any title, tool or setup.

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 — some of our early development happened with its author alpha-testing our hardware, but it is theirs, and ARK does not maintain or support it. 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?

The supported-title list is FlyPT Mover's; an undated copy, which may be out of date, is on the support page. 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?

No, 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; work below it is not part of what the Kit supplies.

Keep reading

Motion cueing

What happens to your telemetry between arriving and being executed.

Motion cueing ›

Community guides

Setup material written by people running the hardware. Kinemaniacs is in development.

Kinemaniacs ›

Contact

For integration questions not covered here.