something odd between R4959 and r4985

[Brule]

hello there, i am not as new on the forum, but i post very little, so many of here dont know me ^^

anyway, there is somethingh odd between those 2 versions, i am talking about Zelda: the wind maker

i am playing normally since R4959, and i could take photos with the picture box, the game freeze for a few seconds, but the picture is taken, nothing worng here, than some time later, i downloaded the a new rev 4985 and for a while i didnt had take any picture, till now, and i discovered that i cant, the game freeze when i try take a picture, the same thing happened on really older versions (4-5 months ago) and, the error returned, i dont know why

tryed with the new rev 5003 (btw, great job on that, the games i am playing are a lot bright, and with better sound than before) but the error persist, is just me take a picture and the game freeze.

what could be wrong betwen those 2 versions?

[RupeeClock]

I just started a game of Wind Waker and found I couldn't take pictures either, but I assumed that it was always like that.

[Brule]

(02-04-2010, 04:40 AM)RupeeClock Wrote: I just started a game of Wind Waker and found I couldn't take pictures either, but I assumed that it was always like that.

in older versions was, that is why i stopped playing (i hate leaving sidequest uncomplete)

than after a while on the latest "bi-weklly" version, pictures work, so i started to play wind maker again. than on newer versions stoped again T_T

well, you could use the rev 4959 to take pictures, and the new version to play, is what i am doing now.

But still, i really wanna know what caused the bug back.

[boogerlad]

efb to ram?

[Brule]

changed efb to ram, now i can take photos, but with a freeze of 15-20 seconds, strange that takes so long, on rev 4959 only take 3-5 seconds

[Pringles]

I recommend you use Fraps for screenshots. It's better and shouldn't lag you.
Works with EFB to Texture as well.

[Jack Frost]

He's talking about pictograph photos, not screenshots.
The hangs might be due to (slow) EFB access there - this most likely also means that you use the DX9 plugin