Bluetooth Passthrough = "ScheduleEvent from wrong thread (non-CPU)"

[dezraj]

(10-15-2017, 12:27 AM)JosJuice Wrote: 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

Thanks a lot for the tip! Would you have a working link for the platform update? It seems as though Microsoft removed the file from their servers. Curiously all their links are dead.

[JosJuice]

I was able to download it by following the links there. The page at https://www.microsoft.com/en-us/download/details.aspx?id=36805 looked a bit odd, but once I found that the download link was below the "Select Language" dropdown, I could click on that and then on "Click here" in order to get a download.

[dezraj]

(10-15-2017, 04:45 PM)JosJuice Wrote: I was able to download it by following the links there. The page at https://www.microsoft.com/en-us/download/details.aspx?id=36805 looked a bit odd, but once I found that the download link was below the "Select Language" dropdown, I could click on that and then on "Click here" in order to get a download.

Thank you for your super fast reply. Actually the file is online. I just found out that the problem was with Firefox always showing a "secure connection failed" to this very file and most of the related Microsoft articles. Anyway, thanks again!

[dephined]

I have the same proble (message showing 80% of the time that I start a game), I also noticed that if I reset Wii mote bindings in the Dolphin controller configuration, the "error" message doesn't show up anymore, until I bind again the Wiimote and restart Dolphin or a game...

[dephined]

So at the moment the solution may be to always reset pairings bafore you close/stop playing a game (an hotkey here would be appreciated) and then manually re-bind the Wiimote when you start a new game...

[dephined]

I 've also noticed that enabling in the controller configuration the option "input in background" almost get rid of the error message (came out only 1 time after 20 tries), but I don't know what that option is supposed to do...

[dephined]

bah, I think "input in background" story was only a period of good luck, now the messages stil come out as before :-(

[deadkat37]

(12-13-2017, 04:51 AM)dephined Wrote: bah, I think "input in background" story was only a period of good luck, now the messages stil come out as before :-(

sorry to hear you have been getting this issue as well.

I have not had this problem interrupt emulation for many months now and I think that it is successfully suppressed by turning off Panic Handlers which allows the dolphin to continue without any adverse effects (that I can see).

BTW - in some of my earlier posts I said I thought it had been fixed by turning off Virtualisation in the BIOS, but now think this was a red-herring.