Dolphin, the GameCube and Wii emulator - Forums

why, of course! cuz everybody buys the game for two consoles...

Okami PS2 version is much cheaper, and you can just run it on PCSX2 at max frames for half the CPU

The only way to play the game is using DX9 plugin and enable both "EFB copy to RAM" and "Safe Texture Cache". This way you can see graphics and text.
With OpenGL it's all ok but when you enable "Safe Texture Cache" graphics get overburned by black artifacts and you almost cannot see anything.

However, DX9 "EFB copy to RAM" option is also making some less noticing ghosting artifacts, expecially at higher resolutions such as 1080p.



Nothing you cannot enjoy the game but if you switch to "EFB copy to Texture" by pressing "5" on the keyboard you will get this.
Call me "graphic whore" but this is the only reason i play Okami with Dolphin, 1080p + widescreen.



The problem is that you must boot the game with "EFB copy to RAM" and then manually switch to "EFB copy to Texture".
And what's more when you switch to texture you must not have any dark graphics nor black outline in your screen or it will be overlapped to the image constantly.
To do this correctly move camera and find a correct place, such the sky or a light color big rock standing close to it, remember no black outlines inside the screenshoot.
I know this would be a little tricky because it's hard to find a very blank camera spot ;-).
Anyway when you have found the correct spot press "1" on the wiimote to get the map (this is for attenuate more the background, so you won't have any artifact).
While pressing "1" on the wiimote press "5" on the keyboard and you are done.

Hmm, and doing this, the game stops crashing? I noticed some problems with a black blur overlapping the image when I change something in the graphics during the game (probably changing from EFB to RAM, for Texture, as you said, when there are dark spots on the screen), but my real problem realy is the crashing... After I posted that on the previous page, I went back to playing the game and it crashed again after I've painted a sword and faced some mobs... I tried using SaveState to prevent case the game crashed again, so I could just load from my past SaveState and would not have to play all the way again, but the SaveState almost never works ... When I try to use it, the game crashes = (

(12-23-2010, 08:16 AM)Wartogh Wrote: [ -> ]Hmm, and doing this, the game stops crashing? I noticed some problems with a black blur overlapping the image when I change something in the graphics during the game (probably changing from EFB to RAM, for Texture, as you said, when there are dark spots on the screen), but my real problem realy is the crashing... After I posted that on the previous page, I went back to playing the game and it crashed again after I've painted a sword and faced some mobs... I tried using SaveState to prevent case the game crashed again, so I could just load from my past SaveState and would not have to play all the way again, but the SaveState almost never works ... When I try to use it, the game crashes = (

As for me the game crashes too sometimes, but very sporadically so it's not such a problem ;-), when i get that i simply load the last savegame, i don't use savestates.
The fix i explained is intended to remove the ghosting effect you get with "EFB to RAM", maybe it also has a side effect that makes Dolphin to crash less more, who knows ;-).
Or maybe you use some settings this game doesn't like, i also think savestates is very useful but also makes games less stable.

Try using JITIL experimental recompiler.
Disable "Lock threads to cores"

(12-23-2010, 08:48 AM)pilone71 Wrote: [ -> ]

(12-23-2010, 08:16 AM)Wartogh Wrote: [ -> ]Hmm, and doing this, the game stops crashing? I noticed some problems with a black blur overlapping the image when I change something in the graphics during the game (probably changing from EFB to RAM, for Texture, as you said, when there are dark spots on the screen), but my real problem realy is the crashing... After I posted that on the previous page, I went back to playing the game and it crashed again after I've painted a sword and faced some mobs... I tried using SaveState to prevent case the game crashed again, so I could just load from my past SaveState and would not have to play all the way again, but the SaveState almost never works ... When I try to use it, the game crashes = (

As for me the game crashes too sometimes, but very sporadically so it's not such a problem ;-), when i get that i simply load the last savegame, i don't use savestates.
The fix i explained is intended to remove the ghosting effect you get with "EFB to RAM", maybe it also has a side effect that makes Dolphin to crash less more, who knows ;-).
Or maybe you use some settings this game doesn't like, i also think savestates is very useful but also makes games less stable.

Try using JITIL experimental recompiler.
Disable "Lock threads to cores"

Yeah, I also prefer to play without using SaveState, I just used it to avoid having to load the last savegame and having to do it all over again case the game crashes again ...

Well, I'll try your suggestion! Thanks! Let's just hope that with time the developers of Dolphin fix that as they fixed the problems with Sonic Colors ... They already made a gorgeous work with the emu, those games are working pratically perfect already =)

I'm sorry for digging up an old thread, this also might be totally unrelated to the game itself (Because it seems I have this issue with all Wii games).

When I start Okami I can press the + key to start the game, but straight after that (when I have to choose new game/resume game) it says I must connect a wii mote.

(It seems with Mario Galaxy it also asks this whenever I start up the game).

I'm using R6535 from extreme2damax.

Select the nunchuck extension in wiimote config

(12-26-2010, 09:31 AM)KHRZ Wrote: [ -> ]Select the nunchuck extension in wiimote config

Thx a lot :p that was the problem indeed.

@ pilone71

can you tell me how did you manage to run the game like that ? with no graphical errors?