Using a DualSense controller as Titan Two input

Verify the controller over USB

ConsoleTuner’s Titan Two release history records USB and Bluetooth drivers for the DualSense. Start with a known USB-A to USB-C data cable from one of the front input ports to the controller. Confirm the controller appears in Gtuner IV and watch face buttons, both sticks and triggers individually before selecting an alternate host or a wireless connection.

Sony documents the DualSense USB-C connection and recommends a charging-and-data cable when a controller cannot establish the link. If necessary, verify the same cable with the controller attached directly to a supported computer or PS5 before involving the adapter.

Decide whether wireless input is useful

For Titan Two Bluetooth input, check that the optional Bluetooth module and the required setup files are present. Pair the controller with the Titan Two rather than with the destination if the adapter should receive its inputs. When testing, turn off other pairings as needed so the controller does not reconnect to a different host.

Test USB and Bluetooth in isolation. A report that the controller works over one connection gives you a baseline, while a failure only over wireless narrows the cause to the pairing, module or controller radio path.

Check features at the destination

The destination protocol and the application determine whether specialty features are usable. Verify motion, touchpad behavior, haptics, adaptive triggers and audio individually if you rely on them. Face buttons working in Device Monitor confirms an input path but does not confirm that these additional features are passed through.