DualSense not connecting to PC: separate pairing, browser input, and game compatibility

Why connection and compatibility need separate tests

The phrase controller not working can describe several different failures. The computer may not detect any device. Bluetooth may remember a pairing that is not currently connected. A browser may wait for deliberate input before exposing the controller. A game may require a different mapping or input path. Haptic effects may be absent even while every ordinary button works. Treating these as one problem leads to unnecessary resets and conflicting software installations.

This guide follows the connection from the controller to the computer, then to the browser, and finally to the game you want to play. At each stage, record what is actually visible before moving on. A passing browser check is a useful intermediate result, not the finish line for game compatibility. Conversely, a browser that does not expose the controller cannot alone establish that the controller is broken, especially when a supported game already receives input.

Prepare the controller and preserve existing settings

1. Identify the exact controller model and note whether it is a standard DualSense, a different PlayStation controller, or a third-party lookalike. Find the matching official support instructions. Record the computer's operating system and the game's name and version. A guide for one model or firmware revision should not be assumed to describe another model's pairing slots, buttons, or supported features.
2. Charge the controller using a supported method and inspect the USB connector and cable for obvious damage. Stop if the battery enclosure is swollen, unusually hot, or damaged. Choose a cable known to carry data, not merely one that lights the charging indicator. Keep a second compatible cable available if possible, but do not force a loose or resistant connector.
3. Save the game and leave online matches before changing connections. Note any controller remapper, launcher profile, accessibility mapping, or virtual controller utility already in use. Do not install another translation tool for the baseline. Have a keyboard or mouse available so losing controller input does not leave you unable to navigate the computer safely.

Establish a wired baseline

1. Connect the controller to a supported computer port with the data cable and allow the operating system to finish recognizing it. Prefer a direct connection for this baseline when practical. A light or battery icon proves power activity, not necessarily successful data communication. Note whether the system's device interface shows the controller and whether that status remains stable without touching the cable.
2. If the device does not appear, disconnect once and compare a second known compatible data cable or another supported port. Change only one item per run. Wait for recognition before opening the game. If neither cable works and another supported computer is available, that becomes a useful next control; otherwise mark cross-computer testing as unavailable rather than implying it passed.
3. If recognition repeatedly disappears, stop moving the connector to provoke it. Record whether the whole device disconnects or only the game loses input. The former points to a different investigation than a stable device that one application ignores. Keep the most stable supported connection for further tests so intermittent detection does not confuse every later result.

Pair through Bluetooth using the documented sequence

Sony's basic first-pairing instructions call for disconnecting USB, turning the controller off, then holding Create while pressing and holding the PS button until the light bar blinks. Enable Bluetooth on the supported computer and select the controller from its discovered devices. Follow the current model-specific page for any pairing-slot or firmware-dependent behavior; do not combine several remembered internet shortcuts into one improvised sequence.

After pairing, check the computer's current connection status rather than relying on a remembered device entry. If the controller connects to another previously used device, intentionally select the desired connection using the supported controls. Do not remove unrelated Bluetooth devices from the computer to clear the list. If you choose to forget this controller and pair again, record that action and expect to restore that pairing; it is not a harmless read-only check.

On Windows 11, start in Settings, Bluetooth and devices, then use Add device and Bluetooth for a discoverable controller. On current macOS, open System Settings, Bluetooth and choose Connect beside the discovered device. Older versions can use different names and layouts. If no Bluetooth controls are available, confirm the computer's supported adapter and drivers with its manufacturer rather than assuming the controller's pairing sequence is at fault.

Make the controller visible to the browser

1. Open MeterSee Gamepad Test in a current supported browser on the secure site. Keep the page visible, click it if needed, and press an ordinary controller button. Browsers may withhold gamepad exposure until deliberate interaction. A waiting message before that gesture is therefore not enough to diagnose a failed connection. Give the interface a moment to display the detected device after the press.
2. If multiple controllers appear, select the one you intend to test and compare its displayed identity with the devices you connected. A virtual controller created by existing software can appear alongside the physical controller. Record both entries if present; do not assume the first item is always the physical DualSense or that two entries mean you accidentally paired the hardware twice.
3. If the operating system shows a stable controller but this page remains empty after interaction, compare another supported browser without changing the connection. If one browser works and another does not, retain the browser-specific result. Avoid weakening privacy protections or installing unknown browser extensions merely to force exposure. The browser API is one observation path, not the operating system's complete device inventory.

Exercise buttons, triggers, and sticks deliberately

Press and release one face button at a time, then each directional control and shoulder control. Watch for a corresponding browser-visible change. Move each stick through a comfortable range and return it to rest. Squeeze and release triggers slowly. The page displays numeric button and axis values supplied by the browser; labels and mappings can differ across connection modes or software layers, so note the observed control rather than insisting every index must have one universal name.

The coverage result concerns controls exposed by that browser. An observed button count does not prove that every physical feature, touch surface, microphone, speaker, motion sensor, or advanced effect is accessible. If a control appears missing, test its intended action in a compatible application and consult the model's documentation. Keep ordinary input coverage separate from the optional vibration command, which can be unavailable even when the input connection is functioning normally.

Interpret neutral-stick observations without calling them a repair

Place the controller on a stable surface, release both sticks, and run the neutral-stick measurement if drifting is part of the complaint. MeterSee observes a short sample and uses a disclosed practical warning threshold. It does not write factory calibration, replace a worn sensor, or measure the manufacturer's electrical tolerances. Touching the stick during the sample invalidates the intended neutral comparison, so repeat after hands are fully clear.

If a character moves without your touch, compare the browser's resting values with the game's behavior and dead-zone settings. A game can apply a different dead zone or mapping, and a small displayed offset does not automatically explain a large in-game movement. Record both observations. Do not enlarge dead zones until an unplayable controller merely looks acceptable in a menu; verify that deliberate small movements remain usable and restore settings that harm control.

Check the target game's input path

Once basic input arrives, open a safe menu or practice scene in the affected game. Confirm whether the game acknowledges the controller, whether controls are mapped correctly, and whether the failure affects every action or only one feature. A game that expects an Xbox-style input path may behave differently from a title with native DualSense support. Browser recognition is not certification of XInput compatibility or any particular game's controller integration.

Read the game's current controller-support notes and the launcher's supported configuration for that title. If a launcher provides per-game controller handling, record the original setting before a single comparison. Some configurations use translation, while others rely on native support; do not apply a blanket instruction to enable or disable every controller layer. The useful outcome is the actual game's behavior under a documented configuration, not a generic claim that one setting is always correct.

Avoid duplicate translation layers

Existing remappers and launchers can intentionally create virtual controllers or transform input. If one physical press moves a menu twice, note which known tools are active and whether both physical and virtual devices are visible. Where the tool offers a documented pause or profile switch, compare that state after saving the configuration. Do not terminate unfamiliar processes or uninstall drivers blindly; a name you do not recognize may belong to an accessibility device or managed system component.

If the problem disappears when one optional translation layer is paused, repeat the game action to confirm the contrast and preserve the working configuration. That supports investigating overlapping input handling, not condemning every remapper. If you need such software for accessibility or an unsupported title, follow its documentation and the game's rules. Avoid unknown driver bundles, security bypasses, or tools that promise universal compatibility without explaining what they install.

Treat haptics and audio as separate features

Sony's current support guidance makes advanced feature availability dependent on the device and game, and describes USB requirements for PC haptic feedback. Check that page and the particular game's documentation before expecting console-equivalent effects. A successful browser vibration request is not proof of adaptive-trigger integration or every DualSense haptic feature. An unavailable browser vibration command is likewise not proof that the controller's actuators have failed.

If connecting the controller changes where computer audio plays, inspect the application's selected output before concluding that sound disappeared. Keep the test volume low and choose the intended speakers or headset. The controller's microphone, speaker, and headset connection have their own support conditions; none are validated by the button display. Test an audio feature only when the platform documentation says it is supported, and treat that outcome as separate from gamepad input.

Use official updates only after collecting a baseline

If the official support workflow recommends an update for your situation, use the manufacturer's current supported utility and instructions. Sony provides PlayStation Accessories for supported PC controller maintenance. Confirm model compatibility, keep the connection stable, and avoid interrupting an update. Do not obtain firmware from a forum attachment or assume a successful download means the controller has finished installing it.

Afterward, repeat the same connection and input checks that failed before. Record the software version when visible and keep the before-and-after results. If the update does not change the symptom, stop attributing improvement to it. A reset is also a separate state-changing step, not something the browser test performs. Follow the exact official reset procedure only when appropriate and understand that connection setup may need to be restored afterward.

Worked case: charging without usable data

Hypothetical example: a controller lights up when connected to a PC, but neither the system nor MeterSee shows a usable controller. The user replaces the cable with one already known to transfer data. The system then recognizes the device, a deliberate button press exposes it to the browser, and the button and stick checks respond. The original observation established charging activity only; it never established a working data path.

The user keeps the compatible cable and verifies the actual game before declaring the task complete. They do not claim that every charging cable is defective or that the original cable failed an electrical test. If the game still ignored the controller, that would become the next separate input-compatibility question. The staged workflow preserves this distinction instead of treating one newly illuminated indicator as proof that every layer now works.

Worked case: browser input works, one game does not

A second hypothetical user sees stable buttons and axes in MeterSee over both supported connections, yet one game shows no controller input. Another compatible game works. The user records the affected title's controller settings and discovers that its documented launcher configuration differs from the active profile. Changing only that per-game setting restores menu navigation and practice controls. The browser test helped establish basic delivered input but did not certify the game's original configuration.

The user then checks advanced effects separately and finds that a desired effect is unavailable in the tested game and connection combination. They record that as a feature-support boundary, not a renewed connection failure. This prevents repeated pairing and unnecessary controller resets after ordinary input is already reliable. A useful completion note distinguishes working controls, untested features, and features documented as unsupported under the chosen setup.

FAQs and safe escalation

Does a connected Bluetooth entry prove a game should work? No. It is one stage of the path. Check delivered controls and then the game's support. Does MeterSee's calibration repair drift? No. It samples browser values without changing firmware. Does missing vibration prove broken hardware? No. Browser and game feature support must be checked first.

When should I contact support? Escalate when detection or a specific control repeatedly fails across supported cables, connections, or computers, or when a documented feature remains inconsistent in a compatible game. Include the exact model, firmware if known, operating system, connection, game, active translation tools, and reproduction. Say which comparisons were unavailable. Do not open the controller, manipulate the battery, or disable security protections to continue; a focused warranty or compatibility report is a legitimate endpoint.