-
Notifications
You must be signed in to change notification settings - Fork 170
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
Vibration? #191
Comments
None of the Moonlight clients support vibration yet. It was only added to GameStream a few weeks ago. |
OK thanks, and i thought it's a bug. |
Any update on this? |
It's not supported by Chrome. |
And no possible workarounds? |
Chrome needs to implement support for it. There's currently no W3C standard for it. There's no way to break out of the Chrome sandbox and directly access the device to vibrate it, if that's what you're asking. w3c/gamepad#19 |
What about the java version? Just tried it and it there doesn't seem to be vibration on it either. :( |
Right, there are 2 issues blocking vibration support on Chrome.
|
Hello, how about the Android client? Could it use the vibration from the smartphone? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Hi, any progress concerning this feature request? |
@Rutjan666 We're working on a new version which may support it. |
wow, that's some good news, as some games rely heavily on vibration!! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Is there anywhere we can keep an eye on this progress instead of just adding to this thread? I don't want to seem like I'm nagging, I'd just want to keep tabs on any developments on this feature as it would be pretty awesome! |
Would be great, like an RSS feed or something. |
@Andy4Shurr @Rutjan666 The team is now working on a new version, which you can find here. The main developer hasn't yet figured out if vibration is indeed possible with the Gamestream protocol, but if this gets ever implemented, it'll be probably in this new version. The Chrome version is now deprecated, in favor of that new version and the Android version for Chromebooks. |
Vibration is supported by GameStream on the Shield Android TV, but not in Moonlight yet. However, it won't be coming to this ChromeOS client because NaCl lacks an API for haptics. |
Thanks for confirmation. I don't use the ChromeOS versions anyway so that's fine, I tend to use I currently use virtualhere with steam link for controller vibration but I find steam in home streaming lacking in certain areas, if it's possible in moonlight that would be the better solution imho. |
Have you tried VirtualHere with Moonlight? |
I have, it works ok locally but doesn't work as well remotely, where I use moonlight more tbh. The in built controller driver in moonlight is more stable and responsive, I'm not sure why. If I VPN into my home network with the steam link app it's fine, although with the VPN it increases latency and It also can't process as much bandwidth so not ideal for gaming otherwise I'd just use that, although like I mentioned steam still isn't ideal and doesn't always play nice with non steam games where as moonlight and Nvidia gamestream are better in that respect. I think the Nvidia streaming API is faster too and supports higher resolution. Using virtualhere with moonlight also loses the ability to control the moonlight app unlike steam link. Not a huge issue but would be good if it had integration. Especially for my Shield TV. I'm not a fan of the shield controller, the sticks are really sensitive so precision aiming is so much more difficult than using a DS4 or XB1 S controller. When using virtual here with moonlight is also a separate licence to steam so I had to buy it again in case anyone wonders. |
Will be implemented vibration (Logitech F710) in Android client? |
I have a Xbox360 controller connected to my PC.
Everything works except vibration.
In Steam InHome Streaming this works.
The text was updated successfully, but these errors were encountered: