You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm hoping to use a Chatpad keyboard connected to a wired Microsoft Xbox controller. This is an original Xbox Chatpad, not one of the aftermarket knock-offs. It uses the same connection as the Xbox controller, not a separate USB receiver. It does show up in Windows as a HID device.
The quickstart script sees the keyboard and does detect the CHN sample keystrokes. But the same CHN keys still get sent through to whatever the active text entry screen is at the moment.
I can press c here in this box, calc.exe is started, but the letter c is still also entered here into this text box.
Is there a way to suppress that follow-on keystroke?
I have tried this with another 'regular' USB keyboard and that one DOES NOT have the pass-through problem.
I think I have figured out part of the problem. If I have the Steam game client running I get the problem. If I quit the Steam client the problem goes away. This is not a solution, however, as the whole point of my attempt here is to use the macros during gameplay and that requires the Steam client.
I'm "guessing" the steam client is using some of the same tricks as luamacros to capture and manage the inputs through the controller and chatpad?
The text was updated successfully, but these errors were encountered:
I can confirm that another Xbox chatpad alternative that uses it's own USB wireless receiver does not have the same double-entry issue as the factory original Microsoft Chatpad. Which makes sense, as it's not really connecting 'through' the Xbox controller's USB connection (and thus not through it's driver subsystem). So the Steam game client doesn't pay any different attention to it, as it thinks it's just another keyboard.
I'm hoping to use a Chatpad keyboard connected to a wired Microsoft Xbox controller. This is an original Xbox Chatpad, not one of the aftermarket knock-offs. It uses the same connection as the Xbox controller, not a separate USB receiver. It does show up in Windows as a HID device.
The quickstart script sees the keyboard and does detect the CHN sample keystrokes. But the same CHN keys still get sent through to whatever the active text entry screen is at the moment.
I can press c here in this box, calc.exe is started, but the letter c is still also entered here into this text box.
Is there a way to suppress that follow-on keystroke?
I have tried this with another 'regular' USB keyboard and that one DOES NOT have the pass-through problem.
I think I have figured out part of the problem. If I have the Steam game client running I get the problem. If I quit the Steam client the problem goes away. This is not a solution, however, as the whole point of my attempt here is to use the macros during gameplay and that requires the Steam client.
I'm "guessing" the steam client is using some of the same tricks as luamacros to capture and manage the inputs through the controller and chatpad?
The text was updated successfully, but these errors were encountered: