[GC] The Legend of Zelda: The Wind Waker

[RicYin]

thanx for the help guys,

the image must have been corrupted, it did work with a new one.

[kilirm]

How do I run it in dx9 mode without the pixelyzed blurring on the background??

[Yobiwan29]

(05-18-2010, 11:41 AM)kilirm Wrote: How do I run it in dx9 mode without the pixelyzed blurring on the background??

Disable CPU->EFB Access. I'm trying to run WW in 60 Hz mode, but no way! VPS still stays at 50, and the animation jerks. I've tried to push B button at the beginning, but doesn't work. Nevertheless it worked well in a last revision, I don't remember which one exactly. Same problem in SMS, I had to import the GC SRAM.raw file from my last revision to see it working again, but still not with Wind Waker...

[kilirm]

(05-19-2010, 01:39 AM)Yobiwan29 Wrote:

(05-18-2010, 11:41 AM)kilirm Wrote: How do I run it in dx9 mode without the pixelyzed blurring on the background??

Disable CPU->EFB Access. I'm trying to run WW in 60 Hz mode, but no way! VPS still stays at 50, and the animation jerks. I've tried to push B button at the beginning, but doesn't work. Nevertheless it worked well in a last revision, I don't remember which one exactly. Same problem in SMS, I had to import the GC SRAM.raw file from my last revision to see it working again, but still not with Wind Waker...

tyvm, its solved, but how do I start windwaker in 50hz mode?

[Yobiwan29]

I guessed you could help for this issue... Basically you have to press B button, but I don't know why, it doesn't work anymore... I'm locked in 50 Hz, wich provides jolts.

[Whistler]

So, the dragoon rost glitch cant be fixed yet?

There is no way to fix it?

[NaturalViolence]

At the moment, no.

Edit: Well now that I think about it that's not completely true. It's just that in order to fix it you have to be running on an older build with copy efb to ram and using the native resolution. Since almost no one runs at the native resolution you might as well say that it can't be fixed.

[Xtreme2damax]

I'm going to take a guess and say this issue probably can't be fixed unless developers figure a way to properly scale EFB to resolutions other than just the native resolution. Since Copy EFB -> Ram is also required and is slow, I'm sure the developers would either need to find a way to speed up Copy EFB -> Ram or at least fix the issues with Copy EFB -> Texture so it produces effects accurately like with Copy EFB -> Ram.

[Whistler]

What about the fire bug?

Cant it be solved?

[Mashuga]

I know it's lazy but I didn't really want to sift through 70 pages of thread just to speed-read for the word 'sound'.

Someone want to sound-off 'yay'/'nay' for sound support?

EDIT: Scratch that, sound works. It's a little choppy but whatever. Only noticeable when music's playing.