Kingdom Hearts II: Difference between revisions

From PCSX2 Wiki
Jump to navigation Jump to search
(Added Links/Picture/Game Info)
(Added a few more things for all easily available info, took off stub)
Line 1: Line 1:
{{info-stub}}
 


{{infobox game
{{infobox game
Line 6: Line 6:
|developer        = Square Enix
|developer        = Square Enix
|genre            = Action RPG
|genre            = Action RPG
|wikipedia        = http://en.wikipedia.org/wiki/Kingdom_Hearts_2
|wikipedia        = [http://en.wikipedia.org/wiki/Kingdom_Hearts_2 Link]
|gameinfo          =
|gameinfo          = The sequel to [[Kingdom Hearts]]
<!-- NTSC-U props -->
<!-- NTSC-U props -->
|NTSCU            = 1
|NTSCU            = 1
Line 62: Line 62:
|cputype          = Intel Core i7 920 @ 3.4 Ghz
|cputype          = Intel Core i7 920 @ 3.4 Ghz
|gputype          = GeForce GTX 285
|gputype          = GeForce GTX 285
|pccomment        = 60/60FPS
|pccomment        = 60/60FPS, works fine.
}}
}}



Revision as of 20:58, 19 April 2012


Kingdom Hearts II

NTSC-U Boxart
Region NTSC-U:
Serial numbers: SLUS-21005
Release date: 03/28/06
CRCs: DA0535FD
Windows Status: Playable
Linux Status: ?
Mac Status: ?
Region PAL:
Serial numbers: SLES-54114
Release date: 09/28/06
CRCs: C398F477
Windows Status: Playable
Linux Status: ?
Mac Status: ?
Region NTSC-J:
Serial numbers: SLPM-66233
Release date: 12/22/05
CRCs: 93F8A60B
Windows Status: Playable
Linux Status: ?
Mac Status: ?

Developer(s): Square Enix
Genre: Action RPG
Wikipedia: Link
Game description: The sequel to Kingdom Hearts

Test configuration on Windows:

PCSX2 version: 0.9.8 r4463
Graphics by GSDX: r4459
Sound by SPU2-X: 1.4
Pad plugin is LilyPad: 0.10.0
BIOS version: USA v02.00


Test configuration on Linux:

PCSX2 version: untested
Graphics by ZZogl: untested
Sound by SPU2-X: untested


PC specs used to test the game:

CPU: Intel Core i7 920 @ 3.4 Ghz
GPU: GeForce GTX 285

Comments: 60/60FPS, works fine.

Known issues:

Sun lights are seen thru walls

  • Solution - Use GSdx software mode (F9). If you switch back to hardware mode it is fixed temporarily in hardware too.