Zone of the Enders: The 2nd Runner: Difference between revisions

From PCSX2 Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 92: Line 92:
|Workaround=[[GSDX#Quick guide to the settings|Allow 8-bit textures]] in GSdx hardware mode can help, unavoidable in DX9 hardware modes (shows "Out of memory" error after a bit).
|Workaround=[[GSDX#Quick guide to the settings|Allow 8-bit textures]] in GSdx hardware mode can help, unavoidable in DX9 hardware modes (shows "Out of memory" error after a bit).
}}
}}
{{ForumLinksList|list=
*[http://forums.pcsx2.net/Thread-Zone-of-the-Enders-The-2nd-Runner-SLES-51113-E--30554 Zone of the Enders - The 2nd Runner (SLES 51113) (E)]}}

Revision as of 09:59, 5 December 2014

Zone of the Enders: The 2nd Runner

North American cover art.
Region NTSC-U:
Serial numbers: SLUS-20545
Release date: March 10, 2003
CRCs: FD12A397
Windows Status: Playable
Linux Status: ?
Mac Status: ?
Region PAL:
Serial numbers: SLES-51113
Release date: September 26, 2003
CRCs: 3E0BEB3A
Windows Status: Playable
Linux Status: ?
Mac Status: ?
Region NTSC-J/C/K:
Serial numbers: SLPM-65236
Release date: February 13, 2003
Windows Status: ?
Linux Status: ?
Mac Status: ?

Developer(s): KCEJ
Genre: Action
Wikipedia: Link
Game description: Also known as "Anubis: Zone of the Enders" in Japan. The sequel to Zone of the Enders.
Throughout Zone of the Enders: The 2nd Runner, the player controls Jehuty, the Orbital Frame piloted by Dingo, from a normally behind-the-back third-person viewpoint that centers itself between the player and enemy when locked on. The gameplay is linear, eschewing the "world map" of Zone of the Enders in favor of consecutive stages in which the player must defeat large amounts of robotic enemies, as well as other Orbital Frames and combat vehicles. The player can fully repair Jehuty by collecting Metatron, and save their progress at the beginning of each stage.
The game’s protagonist is Dingo Egret, a former BAHRAM pilot who, at the beginning of the game, works as an ice miner on the moons of Jupiter. After he finds the orbital frame Jehuty, he is attacked by Nohman and his BAHRAM troops. After his capture, he is mortally wounded, but is saved after Ken Marinaris, a disgruntled member of BAHRAM, has Dingo wired into Jehuty’s life-support system. As the game progresses, Dingo and Ken get to be close friends.


Test configurations on Windows:


Environment Configurations Comments Tester
Region OS CPU/GPU Revision Graphics Sound/Pad
NTSC-U ?
  • Intel Core i7 920 @ 3.4 Ghz
  • GeForce GTX 285
0.9.8 GSDX r4600
  • SPU2-X r4600
  • Lilypad r4510
BIOS: USA v02.00, There is a graphical glitch, invisible beams, in hardware mode. These problems still exist in r5492. Varying speeds, down to 30FPS in boss battles. Software mode (F9) in older GSdx revisions (r3693) can actually be faster. Native resolution in hardware mode is the key. In smaller areas 2-3 enemies its fine with 3x upscale, but other than that, it will be painfully slow. Machina




Known Issues

Lights seen through walls

  • Status: Active
  • Type: Minor
  • Description: Happens in hardware mode, you can see enemy lights or just any lights through solid objects.
  • Workaround: Software mode (F9)

Ram and Vram Spikes

  • Status: Active
  • Type: Major
  • Description: Can use a ton of RAM and VRam resources.
    Out of memory comes up also when you use save states somewhat frequently (DX11 mode). Corrupts your current savestate file. Previous state can be restore from backup. Also PCSX2 needs to be restarted before you can use states again.
  • Workaround: Allow 8-bit textures in GSdx hardware mode can help, unavoidable in DX9 hardware modes (shows "Out of memory" error after a bit).
Public compatibility forum links