GameInput stops working on Host machine when connected to with RDP until rebooted

microsoft / GDK

Microsoft Public GDK

http://aka.ms/gamedevdocs

Other

1.48k stars 99 forks source link

GameInput stops working on Host machine when connected to with RDP until rebooted #28

Open TriumphRick opened 1 year ago

TriumphRick commented 1 year ago

GameInput appears to stop working on the target machine when any user remote desktops to it, even after the remote session is disconnected, until the affected machine is rebooted. This can be reproduced as follows:

Run the Gamepad sample from the Xbox-GDK-Samples repo in Gaming.Desktop.x64
Verify GameInput is working properly
Have a user on any other computer remote desktop to the machine you just verified GameInput to be working
Disconnect the remote session
Run the Gamepad sample from the Xbox-GDK-Samples repo again
Verify GameInput is no longer receiving any input: It will detect controllers, but it will seemingly never pass any input to applications, neither through GetCurrentReading nor GetNextReading

FLY1NGSQU1RR3L commented 1 year ago

@TriumphRick - just read through your report and will be pinging a few folks to see if this is a new issue. I might tie this over on the issues for the sample itself as the folks who work on GameInput aren't paying as close attention to feedback on the GDK installer point.

FLY1NGSQU1RR3L commented 1 year ago

@TriumphRick - are you in our developer program? If so, can you raise this on the Xbox developer forums (https://forums.xboxlive.com) so we can pair you with an expert?

TriumphRick commented 1 year ago

Yes we are. Figured this was the more appropriate forum considering it was publically released, but I've cross-posted this issue on the XBox Developer Forum now for visibility. Thanks. :)

Squall-Leonhart commented 1 year ago

This sounds similar to something i'm experiencing too, except theres no RDP involved, WGI based apps stop receiving input on Account X when you sign into and then log out of Account Y on the switch user screen.

Signing out and back into account X resolves it.

Applications like Xbox Accessories, and apps using recent versions of SDL2 input are affected too as they use WGI. (The former can still vibrate the controller tho)

It would be reasonable to assume the simple creation of a second user session on the machine causes the faulty behavior.

@TriumphRick rather than restarting, does simply logging your user off and back on restore the control behavior?