(05-16-2017, 01:11 PM)Dafahawk Wrote: [ -> ]Ok I was lazy in the last post/test and just copied the portable.txt into the new file name. I just removed the ".txt" so it would work properly. It removed my game directory BUT corrected the CPU#0 issue. What's the magic here my friend?
Adding a portable.txt file makes Dolphin change where its settings and saves are stored, so it's essentially as if you've reset all your Dolphin settings (but the old settings are still on your hard drive in case you want them back later).
What this means is that there's probably a broken configuration file in the Dolphin setting stored in "C:\Users\<YourNameHere>\Documents\Dolphin Emulator"
I recommend you copy only the save files out of there, aka the GC and Wii folders
Update: I spent time configuring the now corrected and working Dolphin tonight. After finishing I left it running while going onto other task. I started to notice Core#0 getting close to the 100% mark roughly 40 minutes. Closed Dolphin and #0 was all good. Here we go again. After trying several combinations of settings being tested from fresh portable installs I found this issue. I can now replicate the issue 100% of the time.
Freshly installed default Dolphin, open controllers, select Continuous Scanning and Real Wii Remote.
Somehow that's it. I gotta get to bed, but I hope one of you brilliant fellows have some input. Thanks for helping me get this far. More testing tomorrow afternoon.