Emulator Issues #6110
closed
Big Buck Hunter Pro wiimote disconnect after a time
0%
Description
Do not attach files to this issue. Upload them to another site and
link here. Use imgur.com for images.
Game Name? Big Buck Hunter Pro
Game ID? SBQE4Z
What went wrong? Wiimote disconnect after a time, only in this game.
What did you expect to happen? After levels the game tell wiimote disconnected. But the wiimote is ok.
What steps will reproduce the problem? Play one or two level, it disconnects.
What version of Dolphin were you using? Dolphin 3.5-1026
64 or 32 bit Dolphin? 64
What version of Dolphin used to work? Older ones with the alternate wiimote timing setting worked properly.
What Operating System were you using and what are your hardware
specifications? win 7 x64
64 or 32 bit Operating system? 64
Any other relevant information or links to logs:
This game were playable with alternate wiimote timings at the past.
Tested on two win 7, and the result is the same: disconnect after a time.
Thanks!
Updated by JMC4789 almost 12 years ago
Go into wiimote configuration and try turning off the Wiimote speaker if you haven't. That fixes Wiimote disconnects in a few other games.
Updated by ervin.hegedus almost 12 years ago
Thanks. Help to keep connected but introduce other error: during shooting scene, reload with "A" button freeze the real wii cursor/crosshair and make it improper.
Updated by ervin.hegedus almost 12 years ago
I red there is a disconnect bug here... wrong, actually.
Updated by Billiard26 over 11 years ago
- Status changed from New to Questionable
"I red there is a disconnect bug here... wrong, actually."
What?
Updated by ervin.hegedus over 11 years ago
Something wrong with the speaker data handling after alternate wiimote timing option disabled.
Updated by Billiard26 over 11 years ago
- Category set to controls
- Issue type set to Bug
I have zero control issues when reloading in this game.
Perhaps your bluetooth setup cannot handle the increased number of packets that are sent when a wiimote sound would be played.
If we tracked the rumble state we could eliminate many of these packets but this shouldn't be needed.
Updated by Billiard26 over 11 years ago
- Status changed from Questionable to Fixed
Is the issue resolved in r018282c2b9f2c0f128b0ae6ce9157ae01de5c4d5 (3.5-1204) when Disabling speaker data?
I bet it will be.
Updated by ervin.hegedus over 11 years ago
Thanks. Looks resolved with disabled speaker data in TEV fixes - r1222. I will check my bluetooth setup, too.