Blissbox GCN-USB crashes Dolphin

[Leafia_Barrett]

Not only when I go to play, but when it has to register that Blissbox exists at ALL (i.e. setting controls). Now, I'm thinking this might be the Blissbox unit itself, as it's been giving me grief lately (probably dying, the thing is a couple years old now and I take it with me everywhere), but I wanted to be sure.

When it reads Blissbox, it hangs for a couple seconds, then produces the "Dolphin has stopped responding" not once, but twice. Looking in the exceptioninfo.txt reveals why: it's throwing two exceptions one after the other.

Unhandled Exception
Code: 0xC0000005
Call stack info:
0x0A072A7C : ?

Unhandled Exception
Code: 0xC0000005
Call stack info:
0x05AC1410 : ?
Dolphin!0x0058E137 : ?

I was hoping this would be a more straightforward explanation than some pointers... Help?

[pauldacheez]

I'd bet that this is yet another SDL-related issue, seeing as we've had plenty of those recently, but I'd defer to ulao for advice before jumping to that conclusion.

[ulao]

Quote:I'd bet that this is yet another SDL-related issue, seeing as we've had plenty of those recently, but I'd defer to ulao for advice before jumping to that conclusion.

Thx for helping out pauldacheez as always FYI: Bliss-Box is a DX only device. If anyone tries SDL it should not show up or work right.

Leafia_Barrett,
It's a beta thing, if you purchased it properly from me you should be aware buying 2.0 is "BETA" 1.0 ( very limited but stable does not have these issue ). If you like the features of 2.0 and want to continue being a beta user FOLLOW THE RULES .

1) Don't ever post on a board that Bliss-box has problems before firstly updating to the latest version. TIP: this issues was resolved a few days ago
2) Be involved, BETA users are intended to help production, this implies you get active on the board and report bugs.
3) Always update! You should always check for newer update as things change on a daily basis.

If you dont want to be part of the BETA project and have 2.0 that is fine but dont do thing like this? Just try to remember the first thing. Its not fair to have the Dolphin group chase down BETA issues that are not of their own making. Also there are times Dolphin makes a change that causes an issue, but Bliss-Box gets on the issue right away.


If you can see this link
http://blissbox.freeforums.org/beta-tester-forum-f44.html
You are singed up for beta, if not request it via PM or email S_K_U_N_X [aT] yahoo [DOT] com


This topic can be closed sorry for inconvenience.

[Leafia_Barrett]

(04-28-2014, 07:33 AM)ulao Wrote:

Quote:I'd bet that this is yet another SDL-related issue, seeing as we've had plenty of those recently, but I'd defer to ulao for advice before jumping to that conclusion.

Thx for helping out pauldacheez as always FYI: Bliss-Box is a DX only device. If anyone tries SDL it should not show up or work right.

Leafia_Barrett,
It's a beta thing, if you purchased it properly from me you should be aware buying 2.0 is "BETA" 1.0 ( very limited but stable does not have these issue ). If you like the features of 2.0 and want to continue being a beta user FOLLOW THE RULES .

1) Don't ever post on a board that Bliss-box has problems before firstly updating to the latest version. TIP: this issues was resolved a few days ago
2) Be involved, BETA users are intended to help production, this implies you get active on the board and report bugs.
3) Always update! You should always check for newer update as things change on a daily basis.

If you dont want to be part of the BETA project and have 2.0 that is fine but dont do thing like this? Just try to remember the first thing. Its not fair to have the Dolphin group chase down BETA issues that are not of their own making. Also there are times Dolphin makes a change that causes an issue, but Bliss-Box gets on the right away.


If you can see this link
http://blissbox.freeforums.org/beta-tester-forum-f44.html
You are singed up for beta, if not request it via PM or email S_K_U_N_X [aT] yahoo [DOT] com


This topic can be closed sorry for inconvenience.

To my knowledge, I do not have Beta unless the Beta testing started over a year ago, when I purchased the item. (I also can't access that forum you linked to, even after signing up, so...)
The other reason that I'm not buying that explanation is that the device worked perfectly fine for a long time, so to have it suddenly stop working seems off to me.

[ulao]

Quote: To my knowledge, I do not have Beta unless the Beta testing started over a year ago, when I purchased the item.

Beta has been going on long before that.

Quote: (I also can't access that forum you linked to, even after signing up, so...)

That just means you never request to be a beta tester as to my point, I dont think it was understood at the time of purchase.

Quote:The other reason that I'm not buying that explanation is that the device worked perfectly fine for a long time, so to have it suddenly stop working seems off to me.

I have explained that in the email.

Prior to the crash, If rumble works or shows up in dolphin you have 2.0, and somehow you have misunderstood the beta program.

The latest 2.0 works with dolphin, as does the stable 1.0. Dolphin has gone thru some changes and caused crashes like this to occur but its not a Dolphin bug. It just caused the Bliss-box to fail alerting a bug in the firmware that has been around for more then a year. Dolphin just ran happy with it until recent. This is how the nature of Beta firmware works. This change that Dolphin made goes back a little ways and was reported by many users. If you want further proof of the bug try to get dolphin to show a crash report. Then go to details and look for PID.dll.

Whether you BUY it or not you should always start from device and work to software. In this cause your device is out of date. Updating it is very easy, so its the best thing to try. I personally think you need to flash 1.0 because you clearly do not know how beta works.