-
-
Notifications
You must be signed in to change notification settings - Fork 141
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
[Controller Request]: Stadia Controller #836
Comments
Stadia controller uses BLE, still in the works #568 |
One of the replies said it was in the works while the direct reply says it
is not in the works.
I appreciate the replies in general and the response to the request. I
couldn't imagine I was the only one who had asked about the Stadia
controller.
Name: Jacob Vaughan
Alt Email: ***@***.***
Alt Email 2: ***@***.***
…On Thu, Jul 4, 2024, 6:17 AM ndeadly ***@***.***> wrote:
Closed #836 <#836> as not
planned.
—
Reply to this email directly, view it on GitHub
<#836 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGEQEL4GFIZIYADLNVQKSH3ZKUOKVAVCNFSM6AAAAABKGSGCK2VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJTGM4TENZTGAYTAOA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Nowhere was it said (by me) that support is not in the works. The controller is working, in private, and has been for some time. |
I just went through the thread and apologies for the confusion on my end.
When you emailed or rather when a reply was sent via email the first email
says, "in the works" while the ticket was closed as, "not planned."
I attached an image just so I don't look entirely crazy. However, I think
the confusion is context on my end of GitHub's responses to and from the
threads or tickets. I also appreciate the references. Never wanted to know
indicate you said anything.
The work on the controller is appreciated. It is awesome it is working in
private. Super excited for that controller. Is there a way to support your
work or efforts? I also don't believe I have the discord server interacting
with the community and keeping up with the controller efforts for the
stadia controller would be awesome. Again thank you for your response.
Name: Jacob Vaughan
Alt Email: ***@***.***
Alt Email 2: ***@***.***
…On Thu, Jul 4, 2024, 7:28 AM ndeadly ***@***.***> wrote:
Nowhere was it said (by me) that support is not in the works. The
controller is working, in private, and has been for some time.
—
Reply to this email directly, view it on GitHub
<#836 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGEQEL75STCLPZXZ2PCF7LLZKUWV3AVCNFSM6AAAAABKGSGCK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBYG4ZTONBTGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Today I learned I am old and was replying via email and didn't realize I could reply directly on GitHub. Apologies. Thanks for the replies. |
@Amagora please use the search funcion even on closed issues before post a duplicated one. please close this. |
Understood, and I apologize. |
Controller Name
Google Stadia Controller | Model: H2B
Current Controller Behaviour
Controller is not successful in pairing with the console
Controller vendor and product ID
A4RH2B
Supported Features
Input Report Format
No response
Additional Details
No response
The text was updated successfully, but these errors were encountered: