The game knows that it has to do that much work and have that much stuff loaded at a time because what's onscreen also includes a bit of what's offscreen. As in, his head reflection is itself a "display", but it's not projecting through to your monitor, it's projecting onto his head, and then you see his head along with everything else on your screen. So if you think of it in terms of "what the viewer sees", the game would render everything that's on my display monitor, then it would check and go, Oh also Clank's head is on screen and I'm seeing this much of it, so also render everything that would reflect at that specific angle across that visible curvature. I imagine the answer is simply that, if a raytraced surface is on screen, then the surfaces and sources the rays would be expected to trace would also needed to be loaded. With these settings, I can play the game with mostly 60 fps, sometimes it drops for a short amount of time, but I think it should be playable.I'm curious about how that would work as well? Also activate "Enable INTC Spin detection", "Enable Wait Loop detection", "mVU flag hack" and "mVU block hack". You should set "Emotion Engine (EE) Cyclerate" to 3 and "VU Cycle Stealing" to 2. Then, go to your emulator settings and switch to "Speed Hacks". So if your processor has 4 threads, this should be set to 3. Under "Software Mode Settings" > "Extra Rendering Threads", give the emulator all the extra threads you have left. Notice that this will slow down your emulation a lot. I could not get rid of the weird shadow silhouette thing graphics glitch.įirst of all, in your Gsdx settings, set "Renderer" to Direct3d9 or Direct3D11 in Software mode. I got rid of the black eyes & texture corruptions glitch in Jak II with the following settings (will most probably also work for Jak III and Jak & Daxter). I know, this thread is a little bit older, but I wanted to share my config for Jak II / Jak III with you, since I feel it might help with some of these problems.
0 kommentar(er)
