Great, report back when you have more info.
You can use the portable.txt file inside dolphin folder to test a clean build without using your real dolphin folder settings.
(10-03-2017, 12:53 AM)trihy Wrote: [ -> ]Great, report back when you have more info.
You can use the portable.txt file inside dolphin folder to test a clean build without using your real dolphin folder settings.
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?
Probably not. Wait for leolam to see if that error message is useful.
Yes, better wait for leo. Probably something related to your adapter.
Did you installed zadig and libusbk or usbdk standalone package?
Hi, I found this thread after following the pull request that linked it. I'm also having the same issue, however I have found a reliable workaround that will (hopefully) help debug the issue. I get the error every time I start up a game, however if I go into the Controller settings and toggle between "Passthrough a Bluetooth Adapter" and "Emulate the Wii's Bluetooth Adapter", then go back to Bluetooth Passthrough and hit Close, the error will not happen on next game boot.
I downloaded Zadig 2.3 and used the libusbk driver as per the wiki's instructions for Bluetooth Passthrough.
(10-03-2017, 11:06 PM)DaMoo Wrote: [ -> ]Hi, I found this thread after following the pull request that linked it. I'm also having the same issue, however I have found a reliable workaround that will (hopefully) help debug the issue. I get the error every time I start up a game, however if I go into the Controller settings and toggle between "Passthrough a Bluetooth Adapter" and "Emulate the Wii's Bluetooth Adapter", then go back to Bluetooth Passthrough and hit Close, the error will not happen on next game boot.
I downloaded Zadig 2.3 and used the libusbk driver as per the wiki's instructions for Bluetooth Passthrough.
Hi,
I'm a bit relieved to know that I am not the only person getting this issue!
Thanks for the workaround advice, I will give it a go. I also used Zadig 2.3 + libusbk driver installed as per the wiki.
What is the make and model of the Bluetooth adapter you are using?
(10-04-2017, 02:47 AM)deadkat37 Wrote: [ -> ]Hi,
I'm a bit relieved to know that I am not the only person getting this issue!
Thanks for the workaround advice, I will give it a go. I also used Zadig 2.3 + libusbk driver installed as per the wiki.
What is the make and model of the Bluetooth adapter you are using?
It's a
Hawking Tech. HBTC1 adapter. It's extremely old, but it has worked with earlier development versions of Dolphin 5.0. Last dev version I used before downloading r5260 was around the r2500's. Never saw this error back then.
(10-04-2017, 02:54 AM)DaMoo Wrote: [ -> ]It's a Hawking Tech. HBTC1 adapter. It's extremely old, but it has worked with earlier development versions of Dolphin 5.0. Last dev version I used before downloading r5260 was around the r2500's. Never saw this error back then.
Hi DaMoo,
I think I might have found what is causing the problem - I was in my BIOS settings and found that I had left "Virtualisation" enabled after playing around with VMWare (it was off by default).
I have switched Virtualisation off and not seen the "ScheduleEvent from wrong thread (non-CPU)" error all evening... I don't want to get giddy too quickly, but could you check this on your system and see if it resolves the problem for you?
Cheers.
that doesn't sound right at all.
Disabling a virtualization extension that dolphin doesn't even touch shouldn't change anything unless you have a motherboard that is entirely broken
(10-11-2017, 08:38 AM)Helios Wrote: [ -> ]that doesn't sound right at all.
Disabling a virtualization extension that dolphin doesn't even touch shouldn't change anything unless you have a motherboard that is entirely broken
I cannot begin to explain it!
I am using one of the recommended BT dongles on Windows 10 and have followed the Wiki installation instructions to the letter. I googled the error expecting to find dozens of similar fault reports from other users with answers explaining whatever Dolphin config setting was causing the issue - but no luck!
I have tried old versions, default config, different PC, etc. but am getting the same issue every time. I am running Windows 10 Home x64 with automatic updates so I find it hard to believe that my config is that unique across the many Dolphin users around the world.
I was in the BIOS because I have just upgraded my memory from 8Gb > 16Gb and a second SSD (in the BIOS double checking exactly what the boot priority was - I hadn't applied any Windows 10 hardware settings for the new SSD format) and spotted that the Virtualisation setting was not default and might be the oddity that makes my setup different enough to cause the problem.
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!!