Emulator

Please respond if this issue is still valid, or it will be closed.

the game still does not work. i have the newest version (r7369)i have windows 7 32bit professional. i still get the same error

Can anyone try running this game using the interpreter instead of JIT/JITIL, as to confirm whether this problem is JIT-related?

Also, just in case, what about using GameConfig options such as "Enable MMU", "Enable BAT" and "MMU Speed Hack"?

Issue 4301 has been merged into this issue.

With the interpreter after a (long) while of black screen (vps 3 - 5% speed) comes out the message: "Program tried to read an opcode from [00000000]. It has crashed."
Trying with "Enable MMU", "Enable BAT" and "MMU Speed Hack" (alone and all toghether) doesn't help (still error "trying to compile at 0.LR=80004bc4")

what have you not tried that you think might work

I think I tried everything that could make a game work but with no avail...

Still an issue. JIT crashes instantly but JITIL seems to at least get to the title screen, but the game just hangs there forever.

will this issue be fixed?

still broken on Dolphin 3.0-158

Please test this game on 3.0-161 (r18d9a275e70c).

still broken on 3.0-161

Still broken. Someone please fix this!

No Longer an Issue

Show a screen of the game working.

I took it from friend only to made a test, i no longer have a copy

You must be talking about some other game, this one doesn't work.

JIT64, HLE, OpenGL:
Shows blank screen for ~10 seconds (not a black screen, just the off-white window color that you see on wxWidgets windows on OS X), then shows game's "Loading" screen and promptly errors:
ERROR: Compiling at 0. LR=80004bc4 CTR=00000001
Dolphin hangs, and crashes when attempting to pause emulation (or do anything else, likely).

JITIL64, HLE, OpenGL:
Shows black screen for ~10 seconds, then shows game's "Loading" screen and promptly errors:
ERROR : Trying to compile at 0. LR=80004bc4
Dolphin hangs, giving me a busy cursor (OS X's "spinning beachball of death") and requiring me to force-quit it myself.

Interpreter64, HLE, OpenGL:
~5 minutes of black screen, then game's "Loading" screen appears and promptly errors:
Program tried to read an opcode from [00000000]. It has crashed.
Dolphin doesn't hang, allowing me to freely pause, resume, and stop emulation. Can't do anything else, of course.

Interpreter64, LLE Interpreter, OpenGL, dual core/idle skipping/MMU speed hack/speed up disc transfer rate all disabled for maximum compatibility:
~10 minutes of black screen (good God, this takes forever), then game's "Loading" screen appears and promptly errors:
Program tried to read an opcode from [00000000]. It has crashed.

Yep, still broken.

(Dolphin 3.0-592, Mac OS X 10.7.3.)

I'm getting slightly different results on 3.0-616, likely from the newly-merged JIT-Exceptions branch:

JIT64, HLE/LLE, OpenGL:
Now just crashes Dolphin without any error. (It would show the standard "Dolphin has quit unexpectedly" dialog box, but I have that dialog disabled.)
Here's a CrashReporter log, if that's any help: http://pastebin.com/3HgFRjsP

I'd normally recommend this be tested under another GPU (as mine, an Intel HD Graphics 3000, breaks at least one game that works on other GPUs), but I doubt that's necessary as it's not crashing on the GPU thread. (I don't actually know what the thread it's crashing on is for, though.)

I've noticed that nobody provided any log output. This is with Interpreter64, LLE and OpenGL: http://pastebin.com/YxwtJ9Zg

I should note that that log output is pretty damn informative. SOMEONE READ IT

Had my own run in with this game today. It's using some sort of custom virtual memory (SR4 and SR8 get initialized to 0x39 and 0x28, SDR1 set to 0x00FA0001) and the "tried to read opcode from [00000000]" error occurs some time during the VM setup; the game copies a function that modifies the IBAT registers (more fun later) to 0x400 and then causes an ISI by jumping to 0x1 (li r12,1;mtctr r12;bctrl) to execute that function. So the PC in the error message is correct, but the game hasn't crashed; it just expects an ISI exception to occur.
Why they did it this way, I have no idea. Triggering an exception is not the preferred method of switching to real mode, especially if you have to wipe out your ISI handler on the way.

Still Here with Bacpatch issue

This game is starting to work with interpreter with the mmu-test branch for those who care -> https://dolphin-emu.org/download/list/mmu-test/

hey, random person here, but I was just trying to get the game to work, and you should note the newest stabile revision(4.0) has broken this game again.

Winchester, this game has never worked in the master branch. It does work in interpreter mode using a build from the mmu-test branch though.

Still hangs on initial loading screen.

Loads up with mmu-test branch (https://dolphin-emu.org/download/list/mmu-test/), but crashes when attempt to load up a game (Campaign or Multiplayer).

This game works fine in mmu-test with MMU on and JIT.

Interpreter is not necessary.

Issue 8302 has been merged into this issue.

Dynamic BAT was merged in #4146 (https://github.com/dolphin-emu/dolphin/pull/4146). Is this fixed now?