Project

General

Profile

Actions

Emulator Issues #7642

closed

Switching between Real & Hybrid Wii Remotes while running causes a crash

Added by JasenHibberd over 10 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Current
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

Game Name?
Legend Of Zelda: Skyward Sword

Game ID?
SOUE01 (USA)

What's the problem? Describe what went wrong in few words.
Using a hybrid Wii Remote will not allow you to calibrate on the intro screen (it fails to detect the nunchuk or motion plus accessory), attempting to switch to a "Real" Wii remote to calibrate fails and causes Dolphin to crash.

What did you expect to happen instead?
For the Hybrid Wii Remote to detect the Nunchuk or Motion Plus and allow me to calibrate

What steps will reproduce the problem?
[Don't assume we have ever played the game and know any level names. Be as
specific as possible.]

  1. Connect in real wii remote with motion plus built in, and the nunchuk connected
  2. Connect it to Dolphin and set Dolphin to hybrid Wii Remote
  3. Launch game
  4. Game will get stuck waiting for you to connect the motion plus and/or the nunchuk accessory. Switching to real wii remote crashes Dolphin, and was the only known way around this problem

Dolphin 3.5 and 3.5-367 are old versions of Dolphin that have
known issues and bugs, so don't report issues about them and test the
latest Dolphin version first.
Which versions of Dolphin did you test on?
Dolphin 4.0-3106

Does using an older version of Dolphin solve your issue? If yes, which
versions of Dolphin used to work?

I do not know

What are your PC specifications? (including, but not limited to: Operating
System, CPU and GPU)
Summary
Operating System
Windows 8.1 Pro 64-bit
CPU
Intel Core i7 2630QM @ 2.00GHz 164 °F
Sandy Bridge 32nm Technology
RAM
8.00GB Dual-Channel DDR3 @ 656MHz (9-9-9-24)
Motherboard
Dell Inc. 0NJT03 (CPU) 168 °F
Graphics
Generic PnP Monitor (1920x1080@60Hz)
Intel (Dell)
2047MB NVIDIA GeForce GT 540M (Dell) 135 °F
Storage
596GB TOSHIBA MK6461GSYN (SATA) 123 °F
Optical Drives
HL-DT-ST DVDRWBD CT30N
ELBY CLONEDRIVE SCSI CdRom Device
Audio
Realtek High Definition Audio
Operating System
Windows 8.1 Pro 64-bit
Computer type: Virtual
Installation Date: 8/31/2013 12:35:02 AM

Is there any other relevant information? (e.g. logs, screenshots,
configuration files)
[Upload big files to a hosting service and post links here!]
Using Toshiba Bluetooth Stack
Screenshot of screen you get stuck at
http://i.imgur.com/PN5xAiY.png

[Do not attach files to this issue. Upload them to another site and
link here. Use imgur.com for images and pastie.org for logs. Monitor the
email address that was used to create this issue.]


Related issues 1 (0 open1 closed)

Has duplicate Emulator - Emulator Issues #8046: Switching wiimote from hybrid to real crash when a remote is connectedDuplicate

Actions
Actions #1

Updated by JMC4789 over 10 years ago

  • Status changed from New to Accepted
Actions #2

Updated by JMC4789 over 10 years ago

  • Milestone set to Current
Actions #3

Updated by JMC4789 about 10 years ago

Coredump. http://pastie.org/pastes/9670860/text

shuffle2: basically the issue is that it's trying to assign a new thread to m_wiimote_thread, when m_wiimote_thread is already running

If someone could fix this, that'd be nice.

Actions #4

Updated by JMC4789 almost 10 years ago

Issue 8046 has been merged into this issue.

Actions #5

Updated by Shalashalska over 9 years ago

I have the same problem, and found a way around it. Switch from Hybrid to Emulated to Real, then when you get to the point the remote at the center of the screen, save a state, then switch to hybrid, then load the state again.

Actions #7

Updated by AdmiralCurtiss over 9 years ago

This is actually much uglier than just the described issue. You can also trigger the same crash by setting two Wiimotes options to Real, connecting one Wiimote, then switching the first Wiimote to None. It's an issue with how Dolphin tries to re-assign a Wiimote that has been changed in the UI to a different internal "slot": Start at ControllerConfigDiag::SelectSource() and follow the function calls down, you'll see what it's trying to do eventually. I'll try to look at this more tomorrow.

Actions #8

Updated by JosJuice over 9 years ago

  • Status changed from Accepted to Fix pending
Actions

Also available in: Atom PDF