Force Unleashed Bugs

[JMC47]

The game commonly disconnects Wiimotes on boot and sometimes between levels. It should never disconnect the wiimote during gameplay through. That sounds like Dolphin's log message is wrong.

[darkness93]

Thanks, no disconnects happen though since I updated my Bluetooth driver plus got a new dongle (not sure if that helped but my old one was very old). Only problem now is sometimes in multiplayer this error comes up, as I showed before. Any thoughts on this "Unknown Opcode" statement? When I click ok it resumes as normal.. seems to happen whenever I try to initiate a force lock. The subsequent force locks seem fine

   

[darkness93]

Any explanations for this? Would love to play multiplayer on this without the error popping up

[darkness93]

*BUMP* Still happening on Dolphin 5.0-574 (Released 6 hours ago) :'(

[Craftyawesome]

Still dual core I think

[darkness93]

(09-10-2016, 09:57 PM)Craftyawesome Wrote: Still dual core I think

I think I tried that again too, plus I hope it isn't because it significantly reduces the speed. JMC47 here said it disconnects the wiimotes on the console too, however I'd have thought their connection between Dolphin would be more reliable. I think it must be just the game, all my other ones don't have them disconnect like this, and it seems it's only during the "force lock" scenes which is the most fun part of the battle  I'll keep you updated..

[mstreurman]

What @CraftyAwesome means is that the Unknown opcode has nothing really to do with the Wiimotes because that is an issue with Dolphin itself. Remember that the Dualcore mode of Dolphin is a Hack and something is de-syncing the cores. The issue should not be happening in singlecore mode since it is cannot de-sync 2 different cores because you are not using them. IF, and only IF the issue is happening on singlecore as well it might actually be that you stumbled upon a bug in Dolphin. So from that moment on it might be smart to start trying different settings (preferably at 1x IR and no enhancements or hacks to rule issues with those out) and different backends for graphics and sound and CPU emulator engine.

[darkness93]

Thanks that's very helpful about explaining the Unknown opcode message. I've tried so many different configuration options already including of course running on single core but no luck, however last I tested this was last month on Dolphin 5.0-574, so will try again today with latest dev build when I get around to it.

[darkness93]

Hey guys, on latest Dev Dolphin the game's both really smooth and no wiimote disconnects. However, the opcode thing still shows when a force lock happens, but I only need to dismiss those two messages to continue, then it doesn't happen after that. The duel mode is actually very playable past that point Haven't managed to fix that opcode thing yet even after trying on minimal settings (no dual core etc)

[JMC47]

There are still unknown opcodes happening, we just only warn the user about the first one.

If the unknown opcodes happen without dualcore, can you please copy/screenshot the data?