(08-08-2013, 11:37 PM)haddockd Wrote: [ -> ] (08-08-2013, 12:17 PM)Starscream Wrote: [ -> ]You don't need to overclock that high to run this game with HLE audio. Just right click on the game in the game list and select properties, then make sure there is a check in the "DSP HLE Emulation" box.
I think he was referring to running it with LLE due to the crashes that seem to happen sometimes with HLE.
I understand, but he never mentioned any crashes and we're not absolutely sure if HLE actually does cause these crashes (I've never had any). Until he runs into an issue, he should probably use the faster HLE option.
I have run into it once (the first time I ever played through) when I went to the Forsaken Fortress for the first time. Ever since then I used LLE and never looked back.
How bad are the tradeoffs for HLE? I've looked around a bit, and I see mostly sound crashes which prevent treasure chests from completing. Would this be a situation where you could savestate, in game save to be sure, and just go for it? If sound crashes before, try a savestate to fix before running at it again? Basically, are the crashes only in sound, how frequent, and are treasure chests the only game breakers? On the OC, it was something I'd been meaning to do anyways, I've got a medium-high end aftermarket cooler and just had never gotten around to it so i'm not worried about that.
(08-09-2013, 02:55 AM)haddockd Wrote: [ -> ]I have run into it once (the first time I ever played through) when I went to the Forsaken Fortress for the first time. Ever since then I used LLE and never looked back.
Yeah, that's exactly where it crashed for me
Save states actually tend to exacerbate the problem, from what I hear. Some folk who ran into the hangs somehow ended up with corrupt savefiles and had to use save states for the rest of the game, then when they hit one of the hangs they couldn't do anything about it, since you can't just switch it to LLE when your save state was made under HLE.
So, yeah, I'd personally stick with LLE until someone rewrites the Zelda µcode HLE. I can't trust the current HLE. v_v
It really just comes down to risk. If you are risk and crash averse, use LLE at the cost of speed. If you value speed then use HLE but know it can cause freezes/crashes. I always recommending using native saves vs save states, but that's just me.
After some tweaking, I've set it to 1.5 native, 4x SSAA and running LLE. Does that sound about right for a 3.8GHz i7 950, GTX 460 card or should I be able to run higher than that? I can bump it up a good amount (3x native) without seeing any slowdowns in normal game, but locking onto anything for some reason gives me sound and fps drops by about 10 fps, making combat a bit difficult. Is slowdown on lockdown something other people have experienced?
1.5IR + 4x SSAA = 3xIR
3xIR + 4x SSAA = 6xIR
You should use 4xIR , no AA , 16x Anisotropic Filtering
With my 6970, I am only able to get 3x at 4x AA anything higher in the AA department bring my GPU to about half FPS. Remember that bumping up AA will mean a larger performance hit that upping the IR (assuming equal intervals( 1x IR vs 4x AA)
I'm also having this issue with Wind Waker; whenever I get in combat the FPS drops to around 25-27 or so and the audio gets choppy.
If I change my setting to frame limit 60 the Frame rate drops to 35-40 in combat. It's really weird.
I'm using HLE too, so LLE isn't causing it for me. :/
EDIT: Actually scratch that; I didn't notice the WW ROM was overriding my DSP settings into LLE. So now it's actually on HLE I'm not getting any slowdowns at all. Hopefully I won't run into the crashes.