ATLAS VISIONCOMPUTER VISION
Checking account
Browse docsControllers and output
On this page
Using Atlas

Controllers and output devices

Atlas reads your controller, lets your script adjust it, and sends the result to your console. The Output device decides how that input reaches the console.

Pre-release documentation: this page describes Atlas for Windows as built from source in September 2026, before public release. Labels and behavior can change before release.

Choose an output device

Pick the output in the Connections card, under Output device.

Output deviceVideo source it works withHow input reaches the console
PlayStation Remote Play or Xbox Remote PlayA capture card, or the matching Remote Play sourceOver your network, inside a Remote Play session. See Remote Play.
Cronus ZenA capture cardThrough a Cronus Zen connected to this PC and to the console.
  • A Remote Play video source always uses Remote Play output. To use a Cronus Zen, choose a capture card as the video source.
  • An output appears only when your plan includes it and it is ready: a saved, complete setup for Remote Play, or a connected Zen for Cronus Zen.
  • When you select Stop, Atlas returns the output to neutral: no buttons held and sticks centered.
Titan Two: Titan Two output is not available in this version of Atlas for Windows, and it does not appear in the list yet.

Choose your controller

Connect your controller to the PC, then pick it under Controller input, or leave Auto-select controller to use the first one Atlas finds. You can switch controllers while a session is running.

ControllerShown asWhat Atlas can pass through
PlayStation 5 DualSenseDualSenseButtons, sticks and triggers; rumble with Remote Play (PlayStation or Xbox); the touchpad, motion and adaptive triggers with PlayStation Remote Play
PlayStation 4 DualShock 4DualShock 4Buttons, sticks and triggers; rumble with Remote Play (PlayStation or Xbox); the touchpad and motion with PlayStation Remote Play
Xbox and other XInput controllersXInputButtons, sticks and triggers; rumble with Remote Play (PlayStation or Xbox)
Other controllersHIDNot supported in this version: Atlas can list them but cannot read them

What reaches the console also depends on the output. Xbox Remote Play has no touchpad or motion. A Cronus Zen receives buttons, sticks, triggers and the touchpad click, and no controller rumbles with Cronus Zen output.

With Remote Play output, your controller is forwarded as usual and your script only changes what it sets. With Cronus Zen output, Atlas reads the controller connected to the PC and sends each change to the Zen straight away; if no controller is connected, the console receives a neutral controller.

Set up a Cronus Zen

  1. Connect the Cronus Zen to your console, and connect it to this PC with USB.
  2. Make sure the Zen runs firmware 2.2.0 to 2.2.14, or 2.3.0 or newer.
  3. In Atlas, choose your capture card as the video source. Cronus Zen then appears under Output device.
  4. Select Start. Below it, Atlas shows Session active.

Atlas reads the console mode from the Zen; you don't choose it in Atlas, and Atlas does not display it. Scripts can check it with cronuszen.protocol.

What you seeWhat to do
No Cronus Zen was found.Reconnect the Zen's USB cable to the PC, check that the Zen is connected to the console, then start again.
Cronus Zen firmware X is not supported.Update the Zen to firmware 2.3.0 or newer, or use 2.2.0 to 2.2.14.
Your input stops reaching the console during a sessionThe Zen may have been unplugged; Atlas does not show a message for this. Select Stop, reconnect the Zen, then Start.

Rumble, lightbar and triggers

Scripts can control rumble, the lightbar, player lights and adaptive triggers only with Remote Play output. With a Cronus Zen these script commands have no effect, and Atlas logs Script feedback failed. See rumble and lightbar.

If your controller is not detected

  • No controller detected: connect a supported controller to the PC with a USB cable, or pair a PlayStation controller with Windows over Bluetooth. Check that Windows shows it under Settings › Bluetooth & devices.
  • While no session is running, the list updates by itself when Windows detects a controller. During a session, select Stop first.
  • Close other apps that take exclusive control of controllers, such as controller remapping tools.
  • If the wrong controller is used, pick it by name instead of Auto-select controller.

More fixes are in Troubleshooting.