Ratchet & Clank: Going Commando: Difference between revisions

Jump to navigation Jump to search

Ratchet & Clank: Going Commando (view source)

Revision as of 14:40, 18 December 2020

2,745 bytes added ,  18 December 2020
→‎Fixed Issues: Removed duplicate item (is more accurately described in →‎Known Issues: Crash after finishing the Jammer Array level
m (Corrected issue of mine.)
(→‎Fixed Issues: Removed duplicate item (is more accurately described in →‎Known Issues: Crash after finishing the Jammer Array level)
(9 intermediate revisions by 5 users not shown)
Line 42: Line 42:
|releasedatePAL    = November 21, 2003<br />August 13, 2004 <small>(Platinum)</small><br />2003 <small>(Australia)</small>
|releasedatePAL    = November 21, 2003<br />August 13, 2004 <small>(Platinum)</small><br />2003 <small>(Australia)</small>
|statusPAL        = 2
|statusPAL        = 2
|linuxstatusPAL    =
|linuxstatusPAL    = 2
|macstatusPAL      =
|macstatusPAL      =
<!-- NTSC-J props -->
<!-- NTSC-J props -->
Line 271: Line 271:
|Comments=Much better graphical fidelity than 1.4.0 (especially with mipmapping), though minor issues persist such as the pause menu being completely opaque. Slowdown between 90 and 100% is somewhat common. However, more demanding levels such as Endako will frequently be in the high 80s and low 90s, and will sometimes even dip down into the mid-to-high 70s. No crashes thus far. Note: I did not see a noticeable speed difference between D3D11 and OpenGL, although Ratchet's shadow was broken with D3D11.
|Comments=Much better graphical fidelity than 1.4.0 (especially with mipmapping), though minor issues persist such as the pause menu being completely opaque. Slowdown between 90 and 100% is somewhat common. However, more demanding levels such as Endako will frequently be in the high 80s and low 90s, and will sometimes even dip down into the mid-to-high 70s. No crashes thus far. Note: I did not see a noticeable speed difference between D3D11 and OpenGL, although Ratchet's shadow was broken with D3D11.
|Tester=TheTechnician27
|Tester=TheTechnician27
}}
{{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
<spoiler show="Settings" hide="Hide">
* MTVU (Multi-Threaded microVU1): Checked
* All else default.
</spoiler>
|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: Basic (Fast)
* 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. Crashed once when a level was being loaded, but it was after hours of play. The game auto-saves before this. Anisotropic Filtering is optional.
|Tester=Otamajakushi
}}
{{TestingEntry
|Status=2
|Region=NTSC-U
|OS=Windows 10 Pro x64
|CPU=Intel i7-4790k @ 4.00Ghz
|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. This may make the game play better but YMMV, it slows some sections down to a crawl. Solid background menus are fine, since other than that and some minor lighting glitches, the game looks great.
|Tester=Darkshadows
}}
}}
{{TestingFooter}}
{{TestingFooter}}
Line 312: Line 375:
* Original names: '''ラチェット&クランク2 ガガガ!銀河のコマンドーっす''' (SCPS-15056) & (SCPS-19302) & (SCPS-19317), '''라쳇&클랭크: 공구전사 대박몰이''' (SCKA-20011)
* Original names: '''ラチェット&クランク2 ガガガ!銀河のコマンドーっす''' (SCPS-15056) & (SCPS-19302) & (SCPS-19317), '''라쳇&클랭크: 공구전사 대박몰이''' (SCKA-20011)
* Also known as '''Ratchet & Clank 2: Locked and Loaded''' (EU, AU), '''Ratchet & Clank 2''' (JP), '''Ratchet & Clank 2: Gagaga! Ginga no Commando-ssu''' (JP)
* Also known as '''Ratchet & Clank 2: Locked and Loaded''' (EU, AU), '''Ratchet & Clank 2''' (JP), '''Ratchet & Clank 2: Gagaga! Ginga no Commando-ssu''' (JP)
* The game has a built in 16:9 widescreen mode that results in a smaller portion of the world being visible.




== Known Issues ==
== Known Issues ==
{{Issue
|IssueName=Crash after finishing the Jammer Array level
|IsFixed=0
|IssueLevel=1
|Description=During the level completion cut-scene you can only hear the audio while the screen remains black. The game crashes after the cut-scene.
|Workaround=Go to Config > Emulation Settings > Game Fixes > Enable manual game fixes > enable 'EE timing hack'. See [https://github.com/PCSX2/pcsx2/issues/964 this GitHub issue].
}}
{{Issue
|IssueName=Game slows down after a cut-scene
|IsFixed=0
|IssueLevel=0
|Description=After certain cut-scenes (e.g. the final Siberius cut-scene) the game will slow down to 50% normal speed.
|Workaround=Restart PCSX2. Saving works correctly when running at 50% speed.
}}
{{Issue
|IssueName=Glitched menu backgrounds
|IsFixed=0
|IssueLevel=0
|Description=Most menu backgrounds are glitched in GSdx hardware modes.
|Workaround=Use software mode, or ignore it (gameplay is not affected).
}}
{{Issue
{{Issue
|IssueName=Megaturret Glove's turrets don't work
|IssueName=Megaturret Glove's turrets don't work
|IsFixed=1
|IsFixed=0
|IssueLevel=0
|IssueLevel=0
|Description=The upgraded turret glove's turrets loop the deployment animation and sound continuously and can't shoot anything.
|Description=The upgraded turret glove's turrets loop the deployment animation and sound continuously and can't shoot anything. By revision 1.5.0, this issue only affects the PAL version.
|Workaround=There's no known solution.
|Workaround=There's no known solution. If you want to avoid this issue, you'll have to stick to the U.S. version for the time being.
}}
}}


==Fixed Issues==
{{Issue
{{Issue
|IssueName=Broken textures
|IssueName=Broken textures
Line 329: Line 418:
|Description=Many textures are broken until you stand close to objects due to GSdx not supporting mip-mapping in Hardware mode.
|Description=Many textures are broken until you stand close to objects due to GSdx not supporting mip-mapping in Hardware mode.
|Workaround=Mipmapping is automatically enabled for this game in recent PCSX2 v.1.5.0 development builds. For earlier v1.5.0 builds go to Config > Video (GS) > Plugin Settings, and manually set '''Mipmapping''' to "'''Basic (Fast)'''". Or switch to Software mode by setting Renderer to any of the "(Software)" options.
|Workaround=Mipmapping is automatically enabled for this game in recent PCSX2 v.1.5.0 development builds. For earlier v1.5.0 builds go to Config > Video (GS) > Plugin Settings, and manually set '''Mipmapping''' to "'''Basic (Fast)'''". Or switch to Software mode by setting Renderer to any of the "(Software)" options.
}}
{{Issue
|IssueName=Cutscene doesn't load
|IsFixed=1
|IssueLevel=0
|Description=After disabling the Thugs-4-less jamming array, only the audio from the following cutscene is loaded. The next cutscene doesn't load at all and the game is stuck on a black screen.
|Workaround=Is resolved in recent PCSX2 v1.5.0 git builds as long as "Automatic Gamefixes" is enabled. For older versions go to Config > Emulation Settings > Game Fixes tab, click "Enable manual game fixes" and enable the "EE timing hack" fix.
}}
}}


Pandubz
ninja
54

edits

Retrieved from "https://wiki.pcsx2.net/Special:MobileDiff/94099...96661"

Navigation menu