Ratchet & Clank: Difference between revisions

Jump to navigation Jump to search
m (Updating test after tweaking settings)
(17 intermediate revisions by 8 users not shown)
Line 213: Line 213:
|OS=Windows 10 x64
|OS=Windows 10 x64
|CPU=Intel Core i7-4770 @ 3.40 GHz
|CPU=Intel Core i7-4770 @ 3.40 GHz
|GPU=1050ti 2GB
|GPU=NVIDIA GeForce GTX 1050 Ti 2 GB
|Revision=v1.5.0 (dev-3199 g2f8932e37) (
|Revision=v1.5.0 (dev-3199 g2f8932e37) (
<spoiler show="Settings" hide="Hide">
<spoiler show="Settings" hide="Hide">
Line 232: Line 232:
|Sound=*SPU2-X 2.0.0
|Sound=*SPU2-X 2.0.0
*LilyPad 0.12.1
*LilyPad 0.12.1
|Comments=BIOS: USA v2.30, Semi-Consitent FPS around 60. No clear graphical glitches. Main source of fps dropping seems to be crates. (NOTE: without using merge sprite skipdraw Will remove parts of the player)
|Comments=BIOS: USA v2.30, Semi-Consitent FPS around 60. No clear graphical glitches. Main source of fps dropping seems to be crates. (note: this game is EE heavy)
|Tester=YFNS
|Tester=YFNS
}}
{{TestingEntry
|Status=2
|Region=NTSC-U
|OS=Windows 10
|CPU=Intel Core i7-4790K @ 4.0 GHz
|GPU=NVIDIA GeForce GTX 1070
|Revision=1.5.0-20191008140206
<spoiler show="Settings" hide="Hide">
* Speedhacks:
** EE Cyclerate: 1
** VU Cycle Stealing: 0
</spoiler>
|Graphics=GSdx 1.1.0 AVX2
<spoiler show="Settings" hide="Hide">
* Renderer: Direct3D11 (Hardware)
* Allow 8-Bit Textures
* Internal Resolution 2x (720p)
* CRC Level: Aggressive
* HW Hacks:
** Merge Sprite
</spoiler>
|Sound=
* SPU2-X 2.0.0
* LilyPad 0.12.1
|Comments= Using BIOS USA 1.60, game runs decently, says it's running at full speed always but you can see it lagging. To combat this a little, I raised the target framerate to 105%, so it runs at around 63 but it looks a little better.
|Tester=ClubSpade12
}}
{{TestingEntry
|Status=2
|Region=PAL
|OS=Windows
|CPU=AMD Ryzen 5 2600
|GPU=Nvidia GeForce 750 TI OC
|Revision=1.6.0 Stable
|Graphics=GSdx SSE4.1/AVX 1.2.0
<spoiler show="Settings" hide="Hide">
* Renderer: Direct3D11 (Hardware)
* Interlacing: Automatic
* Texture Filtering: Bilinear
* Resolution: 3x Native
* Mipmapping: Basic
* CRC Hack Level: Full
* DATE Accuracy: Fast
* Blending Accuracy: Basic
</spoiler>
|Sound=SPU2-X 2.0.0
<spoiler show="Settings" hide="Hide">
* Interpolation: Hermite
* Module: Xaudio 2
* Synchronizing mode: Timestretch
* Audio Expansion Mode: Surround 5.1
</spoiler>
|Comments=Plays at full speed even with widescreen hack. Minor Blue glitch in background menus
|Tester=Zerel
}}
{{TestingEntry
|Status=2
|Region=NTSC-U
|OS=Windows 10
|CPU=Intel Core i7-6700K @ 4.0GHz
|GPU=Nvidia GeForce GTX 1070
|Revision=PCSX2 1.6.0-20200506140834
|Graphics=GSdx AVX2 1.2.0
<spoiler show="Settings" hide="Hide">
* Renderer: OpenGL (Hardware)
* Interlacing: Automatic (Default)
* Texture Filtering: Bilinear (PS2)
* Resolution: 3x Native (~1080p)
* Anisotropic Filtering: 4x
* Mipmapping: Automatic (Default)
* CRC Hack Level: Automatic (Default)
* DATE Accuracy: Fast (Default)
* Blending Accuracy: Basic (Recommended)
</spoiler>
|Sound=
* SPU2-X 2.0.0
* LilyPad 0.12.1
<spoiler show="Settings" hide="Hide">
* Interpolation: 3 - Hermite
* Module: XAudio 2 (Recommended)
* Synchronizing mode: Timestretch
* Audio Expansion Mode: Surround 5.1
</spoiler>
|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
}}
{{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 280: Line 394:


{{Issue
{{Issue
|IssueName=Broken textures
|IssueName=Glitched menu backgrounds
|IsFixed=1
|IsFixed=0
|IssueLevel=1
|IssueLevel=0
|Description=Garbage textures until you stand close to objects due to GSdx not supporting mipmapping in hardware mode.
|Description=Most menu backgrounds are glitched in GSdx hardware modes.
|Workaround=This can be resolved with the latest v1.5.0 git builds. Go to Config > Video(GS) > Plugin Settings, and set Mipmapping to "Basic". Or switch to Software Mode by setting Renderer to any of the "(Software)" options. Note: To minimize the potential performance impact of Software Mode, set Rendering Threads to one less than the number of available CPU cores.
|Workaround=Use software mode, or ignore it (gameplay is not affected).
}}
}}


{{Issue
{{Issue
|IssueName=Glitched menu backgrounds
|IssueName=Crash on MTVU + Disabled Framelimiter
|IsFixed=0
|IsFixed=0
|IssueLevel=0
|IssueLevel=0
|Description=Most menu backgrounds are glitched in GSdx hardware modes.
|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=Use software mode, or ignore it (gameplay is not affected).
|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==


{{Issue
|IssueName=Broken textures
|IsFixed=1
|IssueLevel=1
|Description=Garbage textures until you stand close to objects due to GSdx not supporting mipmapping in hardware mode.
|Workaround=This can be resolved with the latest v1.5.0 git builds. Go to Config > Video(GS) > Plugin Settings, and set Mipmapping to "Basic". Or switch to Software Mode by setting Renderer to any of the "(Software)" options. Note: To minimize the potential performance impact of Software Mode, set Rendering Threads to one less than the number of available CPU cores.
<gallery widths="175px" heights="100px">
<gallery widths="175px" heights="100px">
File:V1.5.0-dev-2155 - Ratchet & Clank -hardware mode-.jpg|Glitched background (OpenGL hardware)
File:V1.5.0-dev-2155 - Ratchet & Clank -hardware mode-.jpg|Glitched background (OpenGL hardware)
Line 300: Line 423:
}}
}}


==The gallery==
 
<spoiler show="Show Screenshots" hide="Hide screenshots">
==Gallery==
<gallery>
<gallery>
File:Ratchet_&_Clank_Forum_5.png|Ratchet & Clank (SCUS 97199)
File:Ratchet_&_Clank_Forum_5.png|Ratchet & Clank (SCUS 97199)
Line 313: Line 436:
File:Ratchet_&_Clank_Forum_4.png|Ratchet & Clank (SCUS 97199)
File:Ratchet_&_Clank_Forum_4.png|Ratchet & Clank (SCUS 97199)
</gallery>
</gallery>
</spoiler>


{{Ratchet & Clank series}}
{{Ratchet & Clank series}}
ninja
54

edits

Navigation menu