Ratchet & Clank: Difference between revisions

Jump to navigation Jump to search
mNo edit summary
(4 intermediate revisions by 2 users not shown)
Line 320: Line 320:
|Comments=BIOS: USA 2.00. Played at full speed. Opaque background to menus, but it's worth it to stay in hardware mode. OpenGL and Direct3D 11 had similar performance, with OpenGL performing slightly better. Anisotropic Filtering is optional. For the Riglar bolt-trick, use turbo mode, lock input, and lower GSdx settings.
|Comments=BIOS: USA 2.00. Played at full speed. Opaque background to menus, but it's worth it to stay in hardware mode. OpenGL and Direct3D 11 had similar performance, with OpenGL performing slightly better. Anisotropic Filtering is optional. For the Riglar bolt-trick, use turbo mode, lock input, and lower GSdx settings.
|Tester=Otamajakushi
|Tester=Otamajakushi
}}
{{TestingEntry
|Status=2
|Region=NTSC-U
|OS=Windows 10 Pro x64
|CPU=Intel Core i7-4790K @ 4.00 GHz
|GPU=NVIDIA GeForce RTX 2080
|Revision=1.7.0-dev-191-g5118aba45
<spoiler show="Settings" hide="Hide">
* EE Cyclerate: 0/-1
* EE Cycle Skipping: 0
* mVU Flag Hack: Yes
* MTVU: Yes
* Preset: 2
</spoiler>
|Graphics=GSdx 1.2.0
<spoiler show="Settings" hide="Hide">
* Renderer: OpenGL (Hardware)
* Internal Resolution: 3x
* 8-bit Textures: Yes
* Large Framebuffer: Yes
</spoiler>
|Sound=
* SPU2-X 2.0.0
* Synchronizing Mode: Async Mix
* Lilypad 0.12.1
|Comments=Game is very demanding. Occasionally slows down with EE Cyclerate 0, but setting to -1 activates the game's internal frameskipping and makes it run a little smoother in most sections. Solid background menus are fine, since other than that and some minor lighting glitches, the game looks great.
|Tester=Darkshadows
}}
}}
{{TestingFooter}}
{{TestingFooter}}
Line 372: Line 400:
|Workaround=Use software mode, or ignore it (gameplay is not affected).
|Workaround=Use software mode, or ignore it (gameplay is not affected).
}}
}}
{{Issue
|IssueName=Crash on MTVU + Disabled Framelimiter
|IsFixed=0
|IssueLevel=0
|Description=The game may crash when loading into a new planet if MTVU is enabled and the framelimiter is disabled. Seems to scale with the power of the host CPU; the stronger the CPU, the faster the game will run, and the faster the game will run, the more likely it is to encounter the hang condition.
|Workaround=Do not disable the framelimiter while loading a new planet. Or, simply reboot the game after the crash (the game auto saves when changing planets, before the crash condition is reached, so no progress will actually be lost).
}}
==Fixed Issues==
==Fixed Issues==


ninja
54

edits

Navigation menu