Bliss-box Controller causing Dolphin crash

01-07-2018, 04:46 AM #1

Hey everyone,

For several years now I've used a controller peripheral called the Bliss-box (http://skunx7.wixsite.com/bliss-box), which in a nutshell is a peripheral that allows you to hook in original controllers via HDMI cables. It's worked great with Dolphin for years with GC controllers. I've updated the firmware on my blissbox, and now Dolphin crashes upon opening the program every time the controller is plugged in. I was wondering if there is some way to get a detailed crash log for why this is happening, so perhaps someone could give me a hand troubleshooting the problem. The very basic log I'm getting currently is this:

44:45:336 ControllerInterface\ControllerInterface.cpp:194 N[SI]: Added device: DInput/0/Keyboard Mouse
44:45:358 ControllerInterface\ControllerInterface.cpp:194 N[SI]: Added device: DInput/0/FGT Rumble 3-in-1
44:45:401 HW\WiimoteReal\WiimoteReal.cpp:747 N[Wiimote]: WiimoteReal::Shutdown

Could anyone point me in the right direction to troubleshoot this? I've tried several versions of Dolphin and am currently using the latest experimental builds.

**AnyOldName3** · 01-07-2018, 05:25 AM #2

You can contact the person who actually designed the blissbox directly by sending ulao a personal message, as that's his username on these forums. It's possible that it'd Dolphin's fault, not his, but he'll know more about it than anyone else.

01-07-2018, 06:58 AM #3

(01-07-2018, 05:25 AM)AnyOldName3 Wrote: You can contact the person who actually designed the blissbox directly by sending ulao a personal message, as that's his username on these forums. It's possible that it'd Dolphin's fault, not his, but he'll know more about it than anyone else.

Thanks; I actually was talking with him on the blissbox boards, and he isn't having the same issue I am. It's strange because the controller is recognized and functions well with all my other emulators; just for whatever reason, Dolphin doesn't like it and it crashes immediately. Just not sure I can figure out why yet.

**ulao** · (This post was last modified: 02-01-2018, 02:45 AM by ulao.)

Hey team, so the problem is simple. Here is a poor mans flow of what is going on.

[run dolphin]
[ask device for FFB capabilities]
|
[reply]-[no reply] -> crash
|
continue

So dolphin is expecting all device to reply to a FFB query. Or at-least Dx is.. The problem being is sometimes the usb feature get report is skipped. In this case the usb driver will timeout and someone does not like that. Most all usb devices will give a reply but the Bliss-Box was created using a firmware-only usb driver(v-usb) not hardware. This gives us a lot of advantages but this case is one of the set backs. I have found a way to patch this in the code, I just tell the Bliss-Box not to talk to controller when being asked for FFB capabilities. This works in all cases but Joes here. All it does is frees up resources for the USB talk. Yes it can still happen because this is not hardware usb and Joe is proof that it does. Why his system is so picky I do not know. I suspect a USB sniffer, accelerator or like is on there.

The best solution is to figure out why Dolphin is demanding a reply where pj64 and many others do not. But I'm not here to tell anyone how to code. Just my suggestion, error handing is a good thing Wink

02-04-2018, 11:02 PM #5

(02-01-2018, 02:41 AM)ulao Wrote: Hey team, so the problem is simple. Here is a poor mans flow of what is going on.

[run dolphin]
[ask device for FFB capabilities]
|
[reply]-[no reply] -> crash
|
continue

So dolphin is expecting all device to reply to a FFB query. Or at-least Dx is.. The problem being is sometimes the usb feature get report is skipped. In this case the usb driver will timeout and someone does not like that. Most all usb devices will give a reply but the Bliss-Box was created using a firmware-only usb driver(v-usb) not hardware. This gives us a lot of advantages but this case is one of the set backs. I have found a way to patch this in the code, I just tell the Bliss-Box not to talk to controller when being asked for FFB capabilities. This works in all cases but Joes here. All it does is frees up resources for the USB talk. Yes it can still happen because this is not hardware usb and Joe is proof that it does. Why his system is so picky I do not know. I suspect a USB sniffer, accelerator or like is on there.

The best solution is to figure out why Dolphin is demanding a reply where pj64 and many others do not. But I'm not here to tell anyone how to code. Just my suggestion, error handing is a good thing

I just purchased a Bliss-Box 4-Play recently and was experiencing the same problem as described by joec3109 above. Consequently, yesterday I flashed my firmware back to version 1.56.1 to prevent dolphin from crashing at startup. I'm really hoping, a solution will be found so that I can flash my 4-Play back to 2.0. The above was tested on a brand new installation of Windows 10 (installed from scratch yesterday as well).