(10-11-2017, 09:39 AM)deadkat37 Wrote: [ -> ]...
If DaMoo confirms that he has the same Virtualisation BIOS setting and turning it off fixes it (nothing to with a bug that was introduced between r2500s and r5260 - just coincidence that he had changed this BIOS setting between the earlier version and the current version) I think we have a smoking gun - especially as he has a different model BT adaptor.
Either way, I am psyched that the problem seems to be resolved on my setup!!
I can try disabling Virtualization for the sake of testing, but that isn't a viable long-term solution for me since I actually do run VMs. I'm glad that workaround somehow managed to work for you, but hopefully the devs can narrow down a proper solution to this annoying bug.
Looks like the "transfer to adapter complete" event is being triggered from the CPU thread. This is an issue, because it's supposed to be triggered by libusb, on a different transfer thread. Dolphin is showing this alert because something is definitely wrong.
I've taken a look at the code again -- we submit transfers on the CPU thread; transfers are *always* processed and completed on the transfer thread, so I don't see how the events could be scheduled from the CPU thread...
Unless it's a bug in libusb or the Windows USB backend, which wouldn't be that surprising...
(10-13-2017, 01:34 AM)leolam Wrote: [ -> ]Looks like the "transfer to adapter complete" event is being triggered from the CPU thread. This is an issue, because it's supposed to be triggered by libusb, on a different transfer thread. Dolphin is showing this alert because something is definitely wrong.
I've taken a look at the code again -- we submit transfers on the CPU thread; transfers are *always* processed and completed on the transfer thread, so I don't see how the events could be scheduled from the CPU thread...
Unless it's a bug in libusb or the Windows USB backend, which wouldn't be that surprising...
Would you recommend testing a change in the USB driver? IIRC, I didn't use libusbK when I was on r2500~. Are the other USB drivers provided by Zadig supported by Dolphin (libusb, WinUSB)?
Yeah. They are all "libusb compatible".
Hi,
thanks for the attention everyone is giving this issue - I have never seen an emulation development community so helpful and responsive.
do you think the cause & effect I thought I saw around the Virtualisation BIOS setting is a complete red herring then?
I wouldn't rule that out completely, considering how finicky libusb is on Windows.
(10-03-2017, 05:02 AM)deadkat37 Wrote: [ -> ]Hi,
I have tried the following builds:
* 5.0.4869 (2 months ago)
* 5.0.4003 (4 months ago)
* 5.0.3202 (6 months ago)
but all versions are reporting the same error.
I have also tried it with default config settings using the portable.txt (thanks for that tip!) but it made no difference.
Do you think there is any point in going back further?
Hey there! I just registered to report that I too was having this issue. It's showing in version 5.0-5400 for me. So I went and tried version 5.0-5395 and the problem doesn't show there until now.
I came across an interesting situation though. I opened version 5.0-5395 and let it running with the emulation paused and then tried version 5.0-5400 at the same time and curiously the problem didn't show there! So it only shows if the build is running solely. Maybe that can be somehow useful to find the problem?
That's weird. The change between 5.0-5395 and 5.0-5400 should only affect the video backends, not anything related to Bluetooth...
(10-14-2017, 04:39 PM)JosJuice Wrote: [ -> ]That's weird. The change between 5.0-5395 and 5.0-5400 should only affect the video backends, not anything related to Bluetooth...
By the way, the issue shows with both OpenGL and Direct3D backends in build 5.0-5400. I went and tried version 5.0-5400 because with the most recent dev build the Direct3D backend is broken. Dolphin freezes and crashes when I try to load a game. Since I'm using Win 7, I supposed that has to do with the logic ops changes implemented after version 5.0-5400, which are unsupported in Win 7.
(10-15-2017, 12:24 AM)dezraj Wrote: [ -> ]By the way, the issue shows with both OpenGL and Direct3D backends in build 5.0-5400. I went and tried version 5.0-5400 because with the most recent dev build the Direct3D backend is broken. Dolphin freezes and crashes when I try to load a game. Since I'm using Win 7, I supposed that has to do with the logic ops changes implemented after version 5.0-5400, which are unsupported in Win 7.
I don't think the logic ops changes would cause something like that, but there have been some other changes that could cause those kinds of problems if you haven't installed the updates that are linked here:
https://bugs.dolphin-emu.org/issues/10482#note-4