Zone of the Enders: The 2nd Runner: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{infobox game | {{infobox game | ||
|image = | |image = Zoe2_cover.jpg | ||
|caption = | |caption = North American cover art. | ||
|developer = | |developer = [[Konami|KCEJ]] | ||
|genre = | |genre = Action | ||
|gameinfo = Also known as "Anubis: Zone of the Enders" in Japan. | |gameinfo = Also known as "Anubis: Zone of the Enders" in Japan. The sequel to ''[[Zone of the Enders|Zone of the Enders]]''.<br/> | ||
|wikipedia = | 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.<br/> | ||
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. | |||
|wikipedia = [http://en.wikipedia.org/wiki/Zone_of_the_Enders:_The_2nd_Runner Link] | |||
|reviewlinks = | |reviewlinks = | ||
|reviewscore = | |reviewscore = | ||
| Line 14: | Line 14: | ||
|serialsNTSCU = SLUS-20545 | |serialsNTSCU = SLUS-20545 | ||
|CRCsNTSCU = FD12A397 | |CRCsNTSCU = FD12A397 | ||
|releasedateNTSCU = | |releasedateNTSCU = March 10, 2003 | ||
|statusNTSCU = 2 | |statusNTSCU = 2 | ||
|linuxstatusNTSCU = | |linuxstatusNTSCU = | ||
| Line 22: | Line 22: | ||
|serialsPAL = SLES-51113 | |serialsPAL = SLES-51113 | ||
|CRCsPAL = 3E0BEB3A | |CRCsPAL = 3E0BEB3A | ||
|releasedatePAL = | |releasedatePAL = September 26, 2003 | ||
|statusPAL = 2 | |statusPAL = 2 | ||
|linuxstatusPAL = | |linuxstatusPAL = | ||
| Line 30: | Line 30: | ||
|serialsNTSCJ = SLPM-65236 | |serialsNTSCJ = SLPM-65236 | ||
|CRCsNTSCJ = | |CRCsNTSCJ = | ||
|releasedateNTSCJ = | |releasedateNTSCJ = February 13, 2003 | ||
|statusNTSCJ = | |statusNTSCJ = | ||
|linuxstatusNTSCJ = | |linuxstatusNTSCJ = | ||
| Line 46: | Line 46: | ||
|biosver = USA v02.00 | |biosver = USA v02.00 | ||
|hacks = | |hacks = | ||
|comment = Software mode runs fine but slow, and there is a graphical glitch, invisible beams, in hardware mode. It is not known yet whether it has been fixed in svn. | |comment = Software mode runs fine but slow, and there is a graphical glitch, invisible beams, in hardware mode. It is not known yet whether it has been fixed in svn. These problems still exist in r5492. | ||
<!-- Linux specs --> | <!-- Linux specs --> | ||
|linuxpcsx2ver = | |linuxpcsx2ver = | ||
| Line 65: | Line 65: | ||
|gputype = GeForce GTX 285 | |gputype = GeForce GTX 285 | ||
|pccomment = Varying speeds, down to 30FPS in boss battles. Software mode (F9) in older GSdx revisions (r3693) can actually be faster. | |pccomment = Varying speeds, down to 30FPS in boss battles. Software mode (F9) in older GSdx revisions (r3693) can actually be faster. | ||
<br/> The game is very high demanding in resources (both CPU and GPU wise), if not the highest. An overclocked CPU around 4GHz might help to gain mostly full speed.<br/> | |||
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. | |||
}} | }} | ||
==Known Issues | ==Known Issues== | ||
===Lights seen through walls=== | |||
* '''Type:''' Graphical issue | |||
* '''Affected Game Versions:''' All | |||
* '''Description:''' Happens in hardware mode, you can see enemy lights or just any lights through solid objects. | |||
* '''Solution:''' Software mode (F9). | |||
===Ram and Vram Spikes=== | ===Ram and Vram Spikes=== | ||
Can use a ton of RAM and VRam resources. | * '''Type:''' Graphical issue | ||
*Solution: '''Allow 8-bit textures | * '''Affected Game Versions:''' All | ||
* '''Description:''' Can use a ton of RAM and VRam resources. | |||
* '''Solution:''' [[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). | |||
Revision as of 11:11, 6 January 2013
| Zone of the Enders: The 2nd Runner | |||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
 North American cover art.
| |||||||||||||||||||||||||||||||||||||||||
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 configuration on Windows:
| PCSX2 version: | 0.9.8 |
| Graphics by GSDX: | r4600 |
| Sound by SPU2-X: | r4600 |
| Pad plugin is LilyPad: | r4510 |
| BIOS version: | USA v02.00 |
Comments: Software mode runs fine but slow, and there is a graphical glitch, invisible beams, in hardware mode. It is not known yet whether it has been fixed in svn. These problems still exist in r5492.
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:
Varying speeds, down to 30FPS in boss battles. Software mode (F9) in older GSdx revisions (r3693) can actually be faster.
The game is very high demanding in resources (both CPU and GPU wise), if not the highest. An overclocked CPU around 4GHz might help to gain mostly full speed.
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.
Known Issues
Lights seen through walls
- Type: Graphical issue
- Affected Game Versions: All
- Description: Happens in hardware mode, you can see enemy lights or just any lights through solid objects.
- Solution: Software mode (F9).
Ram and Vram Spikes
- Type: Graphical issue
- Affected Game Versions: All
- Description: Can use a ton of RAM and VRam resources.
- Solution: Allow 8-bit textures in GSdx hardware mode can help, unavoidable in DX9 hardware modes (shows "Out of memory" error after a bit).