Emulator

Enable CPU access to EFB? I dunno, this is an interesting one, PJ64 doesn't even do as well as that. If you can bear incredible slowness for a while, can you see if it works in interpreter mode? Starred.

I'm sure Jabo and Zilmar have their reasons, but things like this just go to show the obvious benefits of an open source emulator.

This sounds like the same type of issue as in ZWW with accepting the pictograph photo's. Try enabling Copy EFB to Ram if you haven't tried that yet.

copy EFB to ram was already on and my system can't handle interpreter mode even though I have a 6mb core 2 duo processor. I only have an intel gma4500HD video card and 4 gigs of ram on my laptop. it's hard to believe that i'm having a harder time playing an n64 game than I do ps2 and dreamcast games.

One, Interpreter is never meant to be fast, it's just for testing to see if it works in interpreter or not, if it DOES work in interpreter, that can narrow it down for the developers. If you REALLY REALLY want to play a Nintendo 64 game, you should probably play it in a Nintendo 64 emulator. Not a Gamecube emulator emulating a Nintendo 64.

Same here with SSBB custom stage previews, but ONLY if the stage was created in Dolphin. The stages that come with the game and stages created on a real Wii both work fine.

After waiting 4 hours to reach the end of the first level, this problem still exists when ran with the interpreter.

This game was never fixed in any n64 emulators so it'd be nice to see it working with dolphin. The n64 emulators had the same problem in not being able to select pictures, but they got around it with a cheat code you could enter that would fix it. The n64 versions had other problems that dolphin doesn't seem to have though.

emulating an emulator

lulz

I played this game in the emulator with EFB to ram on, and I've noticed that it's actually different than in the N64 emulators. The problem isn't in the pictures being taken, or even in viewing them.

In EFB to texture, it does not detect what you're seeing and softlocks because there is a scripted sequence at the beginning of stage one. This is because it's meant to see three pokemon and force you to use the controls.

EFB to Ram detects the pokemon, and detects that you're shooting them and the stage plays as normal. But somewhere along the lines, that data gets lost or isn't saved, because the problem is that when you see the pictures in Oak's lab, it doesn't know that there's a pokemon in the picture, effectively giving you 0 pokemon to choose from. This cannot happen in stage 1 on the Wii, because you automatically have 3 images from the first 3 pidgeys.

For people who absolutely want to play it on emulator, project 64 and Mupen 64 with Glide64 Napalm will run the game fine under certain settings. Otherwise, just stick to the Wii for now

Is it possible to fix this issue ?
We can't finish Pokemon Snap on any N64 emulators, because there are a problem with the red dot of the camera...

Even a cheat code or any hack, but please, you can find a solution, for we, Pokemon fans ?

Thanks in advance guys...

@link_971: Stop spamming the issue tracker, this isn't a support forum to get all your issues fixed. If you have nothing to say which directly helps solving the issue, keep it to yourself. Thanks.

For some reason, D3D in this fork actually works. https://forums.dolphin-emu.org/Thread-custom-d3d-version-with-massive-performance-boost-and-a-lot-of-rendering-fixes

I tried software renderer last night and it was back to "stuck in tutorial mode".

I was thinking on the way to work that it might be a gpu sync problem. I had software renderer running in dual core mode, I wonder if single core mode with efb copies. would fix ogl/dx backends?

PhireN: What happens is that the game has a built-in frameskip, and if you run it so slow, you'll miss the pokemon that trigger the tutorial.

No, i've only ever tested this with single core.

https://github.com/galop1n/dolphin/commit/8128018a422e4da2ae1054844a2dcd7ade1310a0

This is the real commit that fixes it now. I had to check the WIP branch to find it. I tried merging it into master to pull it apart but holy crap that's not working out.

Pinging more people to dig through it and find what fixes Pokemon Snap.

I did get this commit compiling after fixing a build error in visual studio, and I did confirm with bisecting this one fixes it.

@jmc: this commit is worthless, it's his all-in-one commit.