One Controller, Two Input Paths.

Start With A Repeatable Observation

A remapping setup can expose a physical controller and a virtual output at the same time. A game that responds to both can appear to react twice to one press. Two entries in a browser are a clue about the setup; they are not by themselves proof that a particular game is processing both.

Identify The Entries First

1. Open the tester with your usual remapper profile active.
2. Press one face button and select each responding device in turn.
3. Record the reported name, mapping and button count. Name snapshots “physical path” and “virtual profile” where you can identify them.
4. Repeat the same action in the affected game. Note whether the issue occurs there, only here, or both.

Check Hiding Rules If You Use HidHide

HidHide can limit which applications see a selected physical device while allowing the remapper access. Check the intended physical device and the allowed application path against its official setup guide. A moved executable can leave an old allowed path behind. After a visibility change, reconnect as directed and retest the target application.

Keep the physical controller available to the remapper. Do not hide a virtual output merely because its Xbox name looks unfamiliar. If input disappears, review the last changed rule before adding more drivers.

Save A Useful Before-And-After

Change one visibility or profile setting, then save a second snapshot with the setting named. Compare device identity as well as button behavior. If the browser sees only the virtual output afterwards, that does not mean the physical controller stopped working.

Test the input path → · If the controller disappears →

Sources And Further Help

• HidHide setup guide
• DS4Windows