-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GameInput stops working on Host machine when connected to with RDP until rebooted #28
Comments
@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. |
@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? |
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. :) |
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? |
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:
The text was updated successfully, but these errors were encountered: