Emulator

Game Name?

Dokapon Kingdom

Game ID? (right click the game in the game list, properties, info tab)

R2DEEB

MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)

81e6ee0381ca33b0cb7f5a4fc5e0fc9f

What's the problem? Describe what went wrong.

I started up in netplay, but when it gets to the first screen where it shows supported controllers it displays "Lost Connection with Wii Remote 1" and I can't get past this screen.

What steps will reproduce the problem?

1. Starting up the game in netplay.
2. Let game go until supported controller screen.

Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.

5.0-6081

Is the issue present in the latest stable version?

Yes 5.0

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.)

N/A

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

Not a graphics issue.

What are your PC specifications? (CPU, GPU, Operating System, more)

CPU: Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz, 2601 Mhz, 2 Core(s), 4 Logical Processor(s)

GPU: Intel(R) HD Graphics 520

OS: Windows 10 64-bit

Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)

It looks like people have had this problem before (Emulator Issue #6797), but it seems that using the latest development version fixed it for them.