Xenoblade Chronicles: Difference between revisions

Jump to navigation Jump to search
No edit summary
Line 55: Line 55:
{{testing/entry|revision=3.0-201|OS=Windows 7 x64|CPU=Intel Core i7 920 @ 3.80 GHz|GPU=ATI Radeon HD 5850 1GB|result=PAL version tested; Had some issues with the sound at first using English dialogue, but for some reason this did not occur when setting it to Japanese in the Game Options. It did not always occur however. Other than that the game runs flawless so far.|tester=xRyudo}}
{{testing/entry|revision=3.0-201|OS=Windows 7 x64|CPU=Intel Core i7 920 @ 3.80 GHz|GPU=ATI Radeon HD 5850 1GB|result=PAL version tested; Had some issues with the sound at first using English dialogue, but for some reason this did not occur when setting it to Japanese in the Game Options. It did not always occur however. Other than that the game runs flawless so far.|tester=xRyudo}}
{{testing/entry|revision=3.0-72 HLE Hack|OS=Windows 7 x64|CPU=Intel Core i7-875k @ 2.93GHz|GPU=ATI Radeon HD 5850 1GB|result=PAL patched to 30 FPS; 40+ hours in the game. Only one very minor issue : the screenshot next to your savegames doesn't appear correctly. Otherwise, as far as I can tell, graphics and audio are perfect. No crackling sound at all, which was the purpose of this HLE Hack build. FPS Limit off, JIT recompiler, lock threads to core, HLE, Enable audio throttle, DSound, Direct3D9.|tester=Tech}}
{{testing/entry|revision=3.0-72 HLE Hack|OS=Windows 7 x64|CPU=Intel Core i7-875k @ 2.93GHz|GPU=ATI Radeon HD 5850 1GB|result=PAL patched to 30 FPS; 40+ hours in the game. Only one very minor issue : the screenshot next to your savegames doesn't appear correctly. Otherwise, as far as I can tell, graphics and audio are perfect. No crackling sound at all, which was the purpose of this HLE Hack build. FPS Limit off, JIT recompiler, lock threads to core, HLE, Enable audio throttle, DSound, Direct3D9.|tester=Tech}}
{{testing/entry|revision=3.0-204-dirty |OS=Windows 7 x64|CPU=Intel Core e6600 @ 3.15GHz(tested from 2.4 over 3.0 to 3.15)|GPU=ATI Radeon HD 5850 2GB OC|result=PAL patched to 30 FPS both tried fully; 9+ hours in the game. So, with 3ghz I generally had no overhead and every big situation could lead to crackling despite HLE Hack or LLE DSP, LLE DSP fared generally a lot more well, when I overclocked to 3.15 ghz I had an overhead of about 20% which is nice, this could also because I had far lower memory timings 700mhz @3.15 with 5/5/5/13 (could lower even more, but tends to be more unstable, T2, could imagine T1 gives another speedup but is often very unstable with picky programs) with 3ghz I had 888mhz at 6/6/7/20 and with 2.4ghz I either use 800 or 1066 mhz at respective settings. IdleSkipping ON, accurate Vbeam emulation ON (this one helped a lot) also OpenGL gives the best results for me with the least fuckups and most accurate results, LLE is locked to core, also I assume that with a dual core clocked less than 3ghz you should disable Sound alltogether if your rig doesn't give you good results, this will also result in a big speedup, for me e6600@3ghz wasn't playable with stable best looking settings and memory management but I still have to try out very low memory timings on less FSB, it could be viable because an increase of 150 mhz from 3000 to 3150 shouldn't let me jump from 76/84/96-98% to an even 98-100% (114/126/140 without framelit/throtte) in big locations or with dozens of monsters. Also patching the PAL version to 30fps doesn't seem to have a negative FPS impact whatsoever. Also don't cache display lists as it's sometimes needed, EFB copies are needed for caves and other locations (you can disable it safely and only have minor glitches, like no head but hair etcpp)|tester=SunnySalvadore}}
{{testing/entry|revision=3.0-204|OS=Windows 7 x64|CPU=Intel Core e6600 @ 3.15GHz|GPU=ATI Radeon HD 5850|result=PAL patched to 30 FPS both tried fully; 9+ hours in the game. So, with 3GHz I generally had no overhead and every big situation could lead to crackling despite HLE Hack or LLE DSP, LLE DSP fared generally a lot more well, when I overclocked to 3.15GHz I had an overhead of about 20% which is nice, this could also because I had far lower memory timings 700MHz @3.15 with 5/5/5/13 (could lower even more, but tends to be more unstable, T2, could imagine T1 gives another speedup but is often very unstable with picky programs) with 3GHz I had 888MHz at 6/6/7/20 and with 2.4GHz I either use 800 or 1066MHz at respective settings. IdleSkipping ON, accurate Vbeam emulation ON (this one helped a lot) also OpenGL gives the best results for me with the least fuck ups and most accurate results, LLE is locked to core, also I assume that with a dual core clocked less than 3GHz you should disable Sound all together if your rig doesn't give you good results, this will also result in a big speedup, for me e6600 @ 3GHz wasn't playable with stable best looking settings and memory management but I still have to try out very low memory timings on less FSB, it could be viable because an increase of 150MHz from 3000 to 3150 shouldn't let me jump from 76/84/96-98% to an even 98-100% (114/126/140 without framelimit/throttle) in big locations or with dozens of monsters. Also patching the PAL version to 30FPS doesn't seem to have a negative FPS impact whatsoever. Also don't cache display lists as it's sometimes needed, EFB copies are needed for caves and other locations (you can disable it safely and only have minor glitches, like no head but hair etcpp)|tester=SunnySalvadore}}
{{testing/end}}
{{testing/end}}


== Gameplay Videos ==
== Gameplay Videos ==

Navigation menu