Ratchet & Clank: Difference between revisions
Jump to navigation
Jump to search
no edit summary
mNo edit summary |
No edit summary |
||
| Line 348: | Line 348: | ||
|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. | |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 | |Tester=Darkshadows | ||
}} | |||
{{TestingEntry | |||
|Status = 2 | |||
|Region=NTSC-U | |||
|OS=Windows 10 | |||
|CPU=i9 10900k | |||
|GPU=Geforce RTX 3070ti | |||
|Revision=1.7.2900 | |||
|Graphics=GSdx | |||
|Sound=SPU2-X | |||
|Comments= I just beat this game with zero game breaking issues. There were flickering textures and weird texture warping (not sure if that's the game or PCSX2) but other than that it ran great with Vulkan renderer, EE Cycle Rate set to 180%, and MTVU enabled. | |||
|Tester=Optim | |||
}} | }} | ||
{{TestingFooter}} | {{TestingFooter}} | ||
| Line 411: | Line 423: | ||
|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. | |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). | |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). | ||
}} | |||
{{Issue | |||
|IssueName=Low framerate | |||
|IsFixed=0 | |||
|IssueLevel=-1 | |||
|Description=R&C runs at low framerates out of and in combat. | |||
|Workaround=Try enabling MTVU under Settings > System which as of writing is default turned OFF. This should be a good fix for most people. If this isn't enough, try setting EE Cycle Rate to 130% or 180%. If this still isn't enough, try switching to the Vulkan renderer (Under Graphics > Renderer). | |||
}} | }} | ||