[GH-ISSUE #748] Phantasy Star Online 2 eats all input from barrier with no response #584

New issue

Closed

opened 2026-05-05 06:43:22 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 06:43:22 -06:00

Owner

Originally created by @Flat on GitHub (Jun 12, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/748

Operating Systems

Server: Arch Linux

Client: Windows 10

Barrier Version

2.3.2

Steps to reproduce bug

Launch Phantasy Star Online 2
Try to use the keyboard to type anything or control your character
The game does not register any inputs. You cannot use hotkeys to leave the game's input loop and you are stuck in the game.

Originally created by @Flat on GitHub (Jun 12, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/748 ### Operating Systems ### Server: Arch Linux Client: Windows 10 ### Barrier Version ### 2.3.2 ### Steps to reproduce bug ### 1. Launch Phantasy Star Online 2 2. Try to use the keyboard to type anything or control your character 3. The game does not register any inputs. You cannot use hotkeys to leave the game's input loop and you are stuck in the game.

gitea-mirror closed this issue

2026-05-05 06:43:23 -06:00

gitea-mirror commented

2026-05-05 06:43:25 -06:00

Author

Owner

@Flat commented on GitHub (Jun 18, 2020):

Any ideas at how I may start debugging this issue? I've tried looking through the code base but couldn't find exactly how keys are sent. On windows I assume it may be through some keySend win32 API, but haven't confirmed that.

Has any thought been put into writing a HID driver so that barrier may act more like a native keyboard?

@Flat commented on GitHub (Jun 18, 2020): Any ideas at how I may start debugging this issue? I've tried looking through the code base but couldn't find exactly how keys are sent. On windows I assume it may be through some keySend win32 API, but haven't confirmed that. Has any thought been put into writing a HID driver so that barrier may act more like a native keyboard?

gitea-mirror commented

2026-05-05 06:43:28 -06:00

Author

Owner

@Flat commented on GitHub (Jun 22, 2020):

From additional research it appears the anti-cheat used (nProtect GameGuard) blocks calls to winuser.h SendInput which is the function barrier uses to send key events. The windows on-screen keyboard from accessability does seem to work, I believe as windows sees it as a "hardware" keyboard with it's own driver.

@Flat commented on GitHub (Jun 22, 2020): From additional research it appears the anti-cheat used (nProtect GameGuard) blocks calls to winuser.h SendInput which is the function barrier uses to send key events. The windows on-screen keyboard from accessability does seem to work, I believe as windows sees it as a "hardware" keyboard with it's own driver.

gitea-mirror commented

2026-05-05 06:43:31 -06:00

Author

Owner

@Flat commented on GitHub (Jun 22, 2020):

Aaand.. now it works out of no where.

@Flat commented on GitHub (Jun 22, 2020): Aaand.. now it works out of no where.