Emulator Issues #12342
openCannot trigger variable strength motions
0%
Description
Game Name?
Any Wii game that requires specific motion to trigger an action. Ex: Boom Blox with its variable strength throws.
Game ID? (right click the game in the game list, Properties, Info tab)
RBKE69
MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)
63d749ffdde0ab32dc69d535ef8f373e
What's the problem? Describe what went wrong.
Try to trigger a motion that requires a different "strength" of motion. Ex flicking the Wiimote harder or softer.
What steps will reproduce the problem?
Load up one of the tutorial levels in BoomBlox where you throw a ball.
Try to do both a hard and soft throw.
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
Yes. 5.0-13207
Is the issue present in the latest stable version?
Yes
If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)
--
If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer
--
What are your PC specifications? (CPU, GPU, Operating System, more)
6700k Intel
AMD rx480 GPU
Windows 10
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
This was "fixed" before a number of Wiimote rewrites were performed where it was removed for a future enhanced implementation. This bug is to track that implementation. The original issue was 7813