dolphin crashing dev question.

[ulao]

Hello, I have an issue here that is quite the mystery. I have a device that supports just about any controller available for a console to usb. If you need to know more about it see my sig. My latest adoption is the wii accessory port. The wii uses a i2c protocol that is pretty straight forward. From that I send to usb in the normal way I do all other controller. See the steps below to understand my puzzlement.

Turn on my device in wii accessory mode. -> run dolphin -> run GCpad { crash }
Turn on my device in wii accessory mode. -> removed the controller so that the wii mode is essentially off -> run dolphin -> run GCpad -> plug controller back in -> all controller work -> exit GCpad -> go back in {crash }

all my device does during wii mode is talk to the wii accessory and report to the usb HID. Just like all other controllers.

So it would seem that running GCpad does something to the usb HID that causes my device to go nutty and then making dolphin angry and crashing. Now my only guess is FFB because the only communication that I know of is to inquiry the effects. So I turned off the FFB HID aka (PID) and nothing changed. So I guess what I need to know is what all is done at that point. What ever it is also happens when a game is run.

I know this is not really a dolphin problem but I'm hopping someone can help shed the light here.

[skid]

Is Dolphin at the default input configuration at the time it crashes?

[ulao]

Is Dolphin at the default input configuration at the time it crashes?

nope, does not get that far. Once I click the GCpad it seems to pause for 1-2 seconds then crash before anything else is drawn to the screen..

[skid]

Sorry, I mean does this crash occur with a new, fresh, full install of Dolphin where no setting changes have been made, except for plugging in the adapter and going to the GCPad dialog?

[ulao]

Oh good question, I just downloaded 3.5 stable and installed to a new dir and yes it crashes in the very same way.

[ulao]

Is there a crash log that would give me a clue? Or maybe a log I can turn on before I attempt the crash. All I need to know is what takes place during this point.

For argument sake its works find in other emulators. ( just tested pj64 )

also for kicks I turned off all the controller data, so it sends just 0,0,0.... for each state. Still crashes. Has to be the weirdest thing I have ever seen.
------------------------------------------------------------------
Wait a sec, maybe I was right???

Code:

Problem Event Name:    APPCRASH
  Application Name:    Dolphin.exe
  Application Version:    0.0.0.0
  Application Timestamp:    51e45abc
  Fault Module Name:    pid.dll  <------------------------------------------
  Fault Module Version:    6.1.7600.16385
  Fault Module Timestamp:    4a5be03a
  Exception Code:    c0000005
  Exception Offset:    0000000000002d52
  OS Version:    6.1.7601.2.1.0.256.1
  Locale ID:    1033
  Additional Information 1:    d98f
  Additional Information 2:    d98fb813b238145984d42ddf84ad2d7c
  Additional Information 3:    f3d6
  Additional Information 4:    f3d65cd073ce0ce05ccf9a81394a33f1

pid? is that what I think it is? Maybe the FFB is doing something weird here.

---

Yes, that is the clue I needed. Sorry to waste any devs time it was on my end. All I needed was a clue were to look. Never though I'd get helpful info from the windows crash, huh cool.