You can't push this into master yourself if you don't have commit access, of course. But a dev who knows somethin' about Wii Remotes might come by, look at the change and consider merging it in (crediting you, of course).
The change certainly looks like it'll help, but it may not be that 2 ms was too long an interval - my crackpot theory is that misbehaving remotes expect audio data every 5 ms (since that's the interval at which the DSP receives audio data from the CPU), and if the thread only wakes up every 2 ms, it was waking up at 4 and 6 ms but not at 5 ms, which third-party remotes don't enjoy. Feel free to test this out, of course, since I'm likely incorrect.
The change certainly looks like it'll help, but it may not be that 2 ms was too long an interval - my crackpot theory is that misbehaving remotes expect audio data every 5 ms (since that's the interval at which the DSP receives audio data from the CPU), and if the thread only wakes up every 2 ms, it was waking up at 4 and 6 ms but not at 5 ms, which third-party remotes don't enjoy. Feel free to test this out, of course, since I'm likely incorrect.
<@skid_au> fishing resort is still broken: http://i.imgur.com/dvPiQKg.png
<@neobrain> dafuq
<+JMC47> no dude, you're just holding the postcard upside down
----------------------------------------
<@Lioncash> pauldachz in charge of shitposting :^)
<@neobrain> dafuq
<+JMC47> no dude, you're just holding the postcard upside down
----------------------------------------
<@Lioncash> pauldachz in charge of shitposting :^)