Pixel 2 - GC Works, Wii Crashes (was fine until it wasn't?)

[badrockjones]

I just swapped from IOS to a Pixel 2 last week and installed Dolphin's latest dev build at the time, which booted Wii and GC roms without issue. I've tried multiple versions to see about performance and haven't had any major issues until yesterday -- now, GC games launch but Wii games will crash the emulator. I have deleted cache/uninstalled app/removed all folders as I saw in other posts when I searched for this issue, but it persists even with the known-good build I started with (5.0-6335).

Again, GC games are fine, Wii games are crashing on launch. Just wondering if there's some magic folder I'm missing or something, or how better to wipe all traces of the emu from the phone so I can start fresh?

Thanks!

[badrockjones]

I note that if I disable all Wiimotes, Wii games will boot. Strange! Not a fix but hopefully helpful.

EDIT: Reinstalled 5.0-6335 (again) and Wii games boot again. Also (weirdly) it still had old library values for my collection (the original location I specified when this version was first installed) even though I completely nuked the folder/rebooted phone between installs.

[T_K_25]

(02-21-2018, 03:04 AM)badrockjones Wrote: I note that if I disable all Wiimotes, Wii games will boot.  Strange!  Not a fix but hopefully helpful.

EDIT:  Reinstalled 5.0-6335 (again) and Wii games boot again.  Also (weirdly) it still had old library values for my collection (the original location I specified when this version was first installed) even though I completely nuked the folder/rebooted phone between installs.

6339 appears to have introduced a bug that crashes Dolphin when emulated Wiimotes are used. Crashing also occurs on Windows.

[badrockjones]

(02-21-2018, 03:20 AM)T_K_25 Wrote: 6339 appears to have introduced a bug that crashes Dolphin when emulated Wiimotes are used. Crashing also occurs on Windows.

Thanks for the heads up -- I saw that elsewhere which is what gave me the idea to disable the emulated wiimotes.  Just surprised that it seemed to "stick" to other versions.  I have no idea why this install of 6335 fixed it when my previous reinstall didn't (same process followed exactly each time).  Ah well, mystery somewhat solved!

[JosJuice]

This is now fixed in 5.0-6356.

[badrockjones]

(02-21-2018, 06:42 AM)JosJuice Wrote: This is now fixed in 5.0-6356.

Thanks for the heads up.  Keep up the great work!