[Bug] Rumble stop working after a couple of minutes

[nalf3in]

On my machine (Windows 10 x64 20H2) the rumble works great at the start, but end up stopping working (no rumble at all) after a couple of minutes. The bug can be reproduced easily when playing Halo MCC or many of the Call of duty. Unfortunately, I do not see any error message in the console that opens with the app.

[71]

Hey there. How intense is normally the rumble? Is it constant for a couple of minutes and then stops, or rather works intermittently for a couple of minutes and then stops?

[nalf3in]

Wow that's a quick answer :) Anyway, the intensity must be roughly the same (or at least, I can't tell just by playing) the whole time it works. The way I noticed the bug is by firing up a game, noticing the rumble works when firing with a weapon and then noticing the controller doesn't rumble anymore when pulling the trigger ~ 5 mins in the match. I will try to do more interesting tests (such as leaving it rumbling at full speed for a couple of minutes).

TLDR for the wall of text : here
On a bit of an unrelated note (but hopefully that can maybe be of use to you), I was planning to do a similar program but I don't have any experience with HID devices and the usb protocol in general so that and my finals of the semester were slowing me down quite a bit. Anyway, I noticed that while the controller is detected as a directinput device in most applications, Chromium based browsers such as Edge (and not Firefox) were able to use the analog triggers and the rumble using the Gamepad Api (you can see what I'm talking about here). This make me thinks that the code for communicating with the controller (when wired) must be located in this directory which I found thanks to this github (which is a patch to make stadia works on unsupported AOSP devices)

I won't have the time mess around the project much for the next week (thanks to my finals) but I'm now able to run and debug the project in vscode so I will try to debug this more proactively if it's still there once they are over :)

[71]

Yeah, I also noticed that Chromium was able to interpret the keys better than regular Windows apps, but didn't manage to find where it was implemented, thanks for the pointer!

As for the issue, I just tried reproducing it with the following code in main.go:

go func() {
	for {
		controller.Vibrate(5, 5)
		time.Sleep(1 * time.Second)
		controller.Vibrate(0, 0)
		time.Sleep(5 * time.Second)
	}
}()

which has been running for 20 minutes now, and the rumbling still hasn't stopped.

I think the first step is to find out if the vibration event is sent to the Stadia controller by eg setting a breakpoint or printing something here (it may also be interesting to see the values of smallMotor and largeMotor).

[nalf3in]

Just a quick update to let you know what I found so far

I just tried a quick and dirty test with a rubber band on the trigger and I was indeed, not able to reproduce the bug even after one hour. However, I'm now able to reproduce it with merely about 20 secs of "normal" playing. That is pretty strange considering that the rumble level in the quick test has 3 "phases" with different rumble level depending of if the guy is shooting or reloading.

Anyway, jumped in the vscode debugger and logged the 2 bytes and the variable iterationCount (corresponding to the number of times the function (modified code here) (Debug console output here) and what actually happens when the bug occurs is the function Vibrate() stop getting called (and no logs are generated). Clearly, the rest of the code is still running (breakpoints in other parts of the code are still working).. With that being said, I think the issue leans toward the "listener of vigem events" or my installation of vigem itself.

I will try to understand the mechanism vigem sends "events" in vigem.go and let you know if I find something of interest. Let me know if you have an idea :)

[ethanporcaro]

Just letting you know I'm having the same issue. I have been working in Unreal Engine for a few hours and now it stopped. Lemme know if you find a fix!

[Gabi10017]

After a few hours lost on searching, I finally found the one that works. No rumble stop bug, and also it has support for analog triggers.

Prerequisites:
ViGEmBus
.NET Desktop Runtime 3.1 - https://dotnet.microsoft.com/en-us/download/dotnet/3.1
.NetFramework 4.5
Requirement: Run the program using Run as Administrator for the best performance.

Optional: Use HidHide in order to avoid double commands.

https://github.com/MWisBest/StadiEm - here is the original project if you want to build your own from it.
https://drive.google.com/file/d/10lHU0kbI3hkNHlYEqfN-4I3rhRMAdSyF/view?usp=sharing - debug build compiled by me using Visual Studio - OLD BUILD - use only if newer builds have bugs!

https://drive.google.com/file/d/1_HXN-1yywvOYilD1EYVY8ByU4-SdJxn_/view?usp=sharing - release build compiled by me using Visual Studio - NEW BUILD - no bugs found yet, leave a comment if you experience one.

[moba86]

Hello,

I opened and closed the issue, I didn't see there was already this issue...

I used v1.3.1 on pc game Gears 4 but after 10 minutes of gaming, the vibration on Stadia controller gone, I have to stop and start manually the .exe (Stadiacontroller 1.3.1) to have the vibration again. I have the same issue on Battlefield V, the vibration stopped after few minutes (about 10 minutes) of gaming.

Thanks in advance for your work and your help :)

[Gabi10017]

Use the file I sent. Stadiacontroller had and still has this issue, and seems like it will not be fixed too soon. Instead, StadiEm works flawlessly.

[moba86]

Thanks a lot Gabi10017 for your prompt answer, I tried your file and it works ;)

[Gabi10017]

Glad I could help 😄

[kastle1]

another thank you to Gabi10017 for providing the build of StadiEm, it works almost perfectly - only issue is that the unmapped buttons (the two below the select and start) sometimes cause the app to crash, but probably an issue with the original project, and I've just learned to stay away from those buttons.

[Gabi10017]

Oh, I didn’t know that. I pressed that 2 buttons only once or twice while using StadiEm only to see if they work or not :D Luckily the app didn’t crash then. Anyway, after that I literally forgot about their existence until you mentioned them 😅. The thing is, even if you would want to, they can’t be really mapped to something since the Xbox Controller doesn’t have that 2 buttons. I’m glad that sharing this build helps others too 😌 Enjoy!

LE: Seems like the StadiEm owner made some modifications to its project a few days ago, I’ll try later tonight to build another .exe from it. I’ll post the link to the new version next to the first, and if it works without issues, I’ll then remove the old build, From what I see he added ‘combo buttons’, whatever that means. I’ll keep you updated ;)
EDIT: New build is UP!

[Gabi10017]

another thank you to Gabi10017 for providing the build of StadiEm, it works almost perfectly - only issue is that the unmapped buttons (the two below the select and start) sometimes cause the app to crash, but probably an issue with the original project, and I've just learned to stay away from those buttons.

Hi! Just released the new build, you could try that one, as far as I saw it has a bit better controls and a bit nicer rumble IMO. Also, I tried crashing the app by spamming those 2 buttons and it didn't crash on my PC (I tried with the new build), please tell me if you still get crashes while pressing the 2 buttons. Thanks!

[kastle1]

Thank you again Gabi10017 for the new build, I really appreciate you compiling and making the builds available, as I don't have any of the necessary tools to compile myself. I tried out the new release, and it seems to be working well enough. I can't really tell the difference between the old one and the new one, other than that the rumble might be a little shorter than it used to be, which I think is a good thing.

As for the app crashing with the extra buttons, it is nearly impossible to reproduce, as it didn't crash before just pressing the buttons after starting up stadiem. I only noticed it twice, both times the stadiem instance had been running for at least a week, and I would accidentally press the lower button instead of the start button while playing something, and windows would make the sound that a device disconnected and my controller would stop working. Both times, inspecting the task bar showed that stadiem was no longer running at that time. I've since just learned to stay away from those buttons, so it'll be hard to tell if the new build is more stable from that standpoint, but will definitely post back here if I notice it again.

Thanks again for your help