Dokapon Kingdom 5.0-129 Netplay Help

07-08-2016, 06:59 AM #1

I am trying to run Dokapon Kingdom on Dolphin 5.0-129 using Netplay. When running the game normally (non-netplay) it works fine. When try to use Netplay (even just hosting as myself with no other participants) the game is stuck at a blackscreen with the following log message:

Code:

49:910 HW\WiimoteReal\WiimoteReal.cpp:657 N[Wiimote]: WiimoteReal::Initialize

58:944 ConfigManager.cpp:71 N[BOOT]: Saving settings to C:/Users/JLATHAM/Documents/Dolphin Emulator/Config/Dolphin.ini

59:121 Main.cpp:524 N[Wiimote]: Not connected

00:363 Boot\Boot.cpp:247 N[BOOT]: Booting C:\Dolphin-x64\iso\Dokapon Kingdom [R2DEEB]/R2DEEB.wbfs

00:368 HLE\HLE_OS.cpp:46 N[OSREPORT]: 812003d8->81300000| 

Apploader Initialized.

00:368 HLE\HLE_OS.cpp:46 N[OSREPORT]: 812003f4->81300000| This Apploader built Oct  3 2007 10:21:59 for RVL

00:782 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: << RVL_SDK - EXI     release build: Aug  8 2007 01:59:22 (0x4199_60831) >>

00:782 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: << RVL_SDK - SI     release build: Aug  8 2007 02:07:10 (0x4199_60831) >>

00:785 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: 

00:785 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: Revolution OS

00:785 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: Kernel built : Jan 30 2008 01:38:43

00:785 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: Console Type : NDEV 2.1

00:785 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: Firmware     : 33.4.16 (6/25/2007)

00:785 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: Memory 88 MB

00:785 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: MEM1 Arena : 0x808fdb40 - 0x817f9b80

00:785 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: MEM2 Arena : 0x90000800 - 0x93ae0000

00:785 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: << RVL_SDK - OS     release build: Jan 30 2008 01:38:43 (0x4199_60831) >>

00:809 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: << RVL_SDK - SC     release build: Aug  8 2007 02:09:03 (0x4199_60831) >>

00:810 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: << RVL_SDK - NAND     release build: Dec 11 2007 01:35:48 (0x4199_60831) >>

00:816 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: << RVL_SDK - DVD     release build: Aug  8 2007 01:59:13 (0x4199_60831) >>

01:011 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: << RVL_SDK - VI     release build: Aug  8 2007 02:07:17 (0x4199_60831) >>

01:020 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: << RVL_SDK - GX     release build: Dec 11 2007 01:34:15 (0x4199_60831) >>

01:177 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: << RVL_SDK - AI     release build: Aug  8 2007 01:58:12 (0x4199_60831) >>

01:177 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: << RVL_SDK - AX     release build: Aug  8 2007 01:58:18 (0x4199_60831) >>

01:178 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: << RVL_SDK - DSP     release build: Aug  8 2007 01:59:06 (0x4199_60831) >>

02:501 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: ...waiting for gpu breakpoint...forever?

03:501 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: ...waiting for gpu breakpoint...forever?

04:503 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: ...waiting for gpu breakpoint...forever?

05:504 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: ...waiting for gpu breakpoint...forever?

06:504 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: ...waiting for gpu breakpoint...forever?

07:505 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: ...waiting for gpu breakpoint...forever?

08:508 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: ...waiting for gpu breakpoint...forever?

09:508 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: ...waiting for gpu breakpoint...forever?

10:509 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: ...waiting for gpu breakpoint...forever?

11:511 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: ...waiting for gpu breakpoint...forever?

12:511 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: ...waiting for gpu breakpoint...forever?

13:512 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: ...waiting for gpu breakpoint...forever?

14:513 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: ...waiting for gpu breakpoint...forever?

15:514 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: ...waiting for gpu breakpoint...forever?

16:517 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: ...waiting for gpu breakpoint...forever?

17:518 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: ...waiting for gpu breakpoint...forever?

18:518 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: ...waiting for gpu breakpoint...forever?

19:520 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: ...waiting for gpu breakpoint...forever?

20:521 HW\EXI_DeviceIPL.cpp:339 N[OSREPORT]: ...waiting for gpu breakpoint...forever?

It does this regardless of renderer (tried DX12, DX11, OpenGL, Software), and regardless of any settings I try. The game also does this on the most recent nightly version 4 build. It does get past this on version 3.5 stable, but that version has issues with controllers in netplay (says wiimote 1 is disconnected). Any ideas? Thanks!

mimimi · 07-08-2016, 07:04 AM #2

Does the game allow using gamecube controller as input devices? If no, it wouldn't work, even if you got it it to boot, because wiimote netplay is disabled on the latest builds for now.

07-08-2016, 07:06 AM #3

Yes it allows gamecube controllers. Playing the game outside of netplay, it starts just fine with only gamecube controllers being emulated as connected and wiimotes set to none.

EDIT: Actually I just tried again, and it seems like a wiimote must be connected for it to get past the initial controller nag. I may be out of luck regardless.

mimimi · 07-08-2016, 07:44 AM #4

Maybe some wiimote netplay stuff is going to be merged this weekend. It might be playable with that, but it's annoying to setup, and it might have really annoying issues.

07-08-2016, 07:46 AM #5

Well unless something changes on the netplay side (as far as the black screen from the "...waiting for gpu breakpoint...forever?" bug) then wiimote support won't matter anyway.

07-08-2016, 09:46 AM #6

So this game does require a Wiimote port to be active upon startup, but you can begin using a gamecube controller right away as long as the wiimote port is on. Once you setup your game settings for a mode, you can mark it to be using the gamecube controller for each individual character and it no longer gives the message the wiimote was disconnected.

However, can we do something about the wiimote being allowed for the sake of netplay with this game?

07-08-2016, 10:27 AM #7

(07-08-2016, 09:46 AM)c.alexnelson@gmail.com Wrote: So this game does require a Wiimote port to be active upon startup, but you can begin using a gamecube controller right away as long as the wiimote port is on. Once you setup your game settings for a mode, you can mark it to be using the gamecube controller for each individual character and it no longer gives the message the wiimote was disconnected.

However, can we do something about the wiimote being allowed for the sake of netplay with this game?

That sounds like it would work for the controller aspect, but again, would do nothing for the black screen issue. The primary issue for this game inparticular is the black screen, as the wiimote missing issue is shared among many titles at the moment.

12-18-2016, 03:07 PM #8

Try to uncheck Dual core in confiq. it's work for me

**JMC47** · 12-18-2016, 03:11 PM #9

Dualcore Netplay is not guaranteed to work for games that use the GPU in certain ways. Single core is recommended for general use in Netplay, with dualcore only being recommended for titles known to be compatible on netplay, or if you absolutely need to use it.