Monster Hunter Tri: Difference between revisions

Line 72: Line 72:
{{Test Entry|revision=7335|OS=Windows 7 x64|CPU=AMD Phenom II 720 BE @ 3.2GHz|GPU=ATI Radeon HD 4850|result=Working good at 30fps. Some slowdowns with many monsters and in the village|tester=ultramann}}
{{Test Entry|revision=7335|OS=Windows 7 x64|CPU=AMD Phenom II 720 BE @ 3.2GHz|GPU=ATI Radeon HD 4850|result=Working good at 30fps. Some slowdowns with many monsters and in the village|tester=ultramann}}
{{Test Entry|revision=7409|OS=Windows 7 x64|CPU=Intel Core 2 Quad Q9550 @ 3.8GHz|GPU=nVidia GeForce 9600 GT|result=Perfect playable: EFB->RAM with Cache enabled and disable CPU-EFB-Access to solve the texture problem. Use HLE to gain +10% FPS|tester=GothicIII}}
{{Test Entry|revision=7409|OS=Windows 7 x64|CPU=Intel Core 2 Quad Q9550 @ 3.8GHz|GPU=nVidia GeForce 9600 GT|result=Perfect playable: EFB->RAM with Cache enabled and disable CPU-EFB-Access to solve the texture problem. Use HLE to gain +10% FPS|tester=GothicIII}}
{{Test Entry|revision=7551|OS=Ubuntu 10.10 x64|CPU=AMD Phenom II X4 @ 3.2GHz|GPU=ATI Radeon HD 4770 512MB|result=Perfect playable: texture problem sometimes. Slow with many monsters and in the village.|tester=Aldo Nogueira}}
{{Test Entry|revision=7551|OS=Linux x86_64 (Ubuntu 10.10)|CPU=AMD Phenom II X4 @ 3.2GHz|GPU=ATI Radeon HD 4770 512MB|result=Perfect playable: texture problem sometimes. Slow with many monsters and in the village.|tester=Aldo Nogueira}}
{{Test Entry|revision=7676|OS=Windows 7 x64|CPU=Intel Core 2 Duo E7500 @ 2.93GHz|GPU=nVidia GeForce 430 GT|result=Perfectly playable at full speed 30 fps even in village. Slows down with many huge monsters at 23-26 fps, in caves with monsters about 23fps, overclocking should resolve this.|tester=Spardadvlking3 (YouTube account)}}
{{Test Entry|revision=7676|OS=Windows 7 x64|CPU=Intel Core 2 Duo E7500 @ 2.93GHz|GPU=nVidia GeForce 430 GT|result=Perfectly playable at full speed 30 fps even in village. Slows down with many huge monsters at 23-26 fps, in caves with monsters about 23fps, overclocking should resolve this.|tester=Spardadvlking3 (YouTube account)}}
|}
|}