I would like to report a reproducible issue with the multi-controller feature (using 2 phones as 2 Xbox 360 controllers on the same PC).
Environment:
- Windows PC, Monect PC Remote (latest version)
- 2 Android phones connected simultaneously via WiFi
- Layout: Xbox 360 Controller (default)
- Goal: Use each phone as a separate player (Player 1 and Player 2) for a split-screen co-op game.
Steps to reproduce:
- Connect Phone 1 and Phone 2 to the PC.
- Under Layout > Settings > Controllers, ensure only 1 controller (Xbox 360) is added.
- Result: Both phones correctly control that single controller in
joy.cpl (verified in Device Properties).
- Add a second Xbox 360 controller via the settings menu (this automatically appears/reflects on both phones and in
joy.cpl, as the controller list is session-wide).
- Manually assign Player ID 1 to Phone 1 and Player ID 2 to Phone 2 ("force to be player 1/2").
Expected behavior:
Phone 1 controls Controller 1 and Phone 2 controls Controller 2, each independently within joy.cpl.
Actual behavior:
Phone 1 continues to control Controller 1 correctly. However, Phone 2 stops controlling both Controller 1 and Controller 2—it sends no input to either controller in joy.cpl, even with the Player ID forced to 2.
Additional observation:
I suspect that the button layout (Xbox 360 Controller) defaults to a fixed association with "Play as player 1," regardless of the "force to be player X" option configured in the controller list. In other words, even if the controller (the virtual device) is forced to Player 2, the layout generating the touch inputs on the second phone might still be internally mapped to Player 1; consequently, no signal reaches the Player 2 slot. If that is the case, it would be necessary to explicitly create or select a "Play as Player 2" layout for the second phone, rather than simply forcing the controller's Player ID.
Specific question:
Could you confirm whether there is currently a way to assign the Xbox 360 layout of a specific phone to Player 2 (rather than just the virtual controller itself)? If not, could you consider addressing this or adding it as a feature, given that it appears to be a recurring issue reported by several users in the community?