Zone of the Enders: The 2nd Runner: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
{{infobox | {{infobox | ||
|image = Zoe2_cover.jpg | |image = Zoe2_cover.jpg | ||
|caption = North American cover art. | |caption = North American cover art. | ||
| Line 34: | Line 34: | ||
|linuxstatusNTSCJ = | |linuxstatusNTSCJ = | ||
|macstatusNTSCJ = | |macstatusNTSCJ = | ||
<!-- Windows | }} | ||
| | |||
| | [[Category:Temp - unverified automatically converted pages]] | ||
| | <!-- Windows and Linux testing tables (remove comment signs on usage, for Macintosh you have to add the same lines begin with {{TestingHeader|OS=Mac}}) --> | ||
| | {{TestingHeader|OS=Windows}} | ||
| | {{TestingEntry | ||
| | |Status=? | ||
| | |Region=? | ||
| | |OS=? | ||
| | |CPU=Intel Core i7 920 @ 3.4 Ghz | ||
| | |GPU=GeForce GTX 285 | ||
|Revision=0.9.8 | |||
|Graphics=GSDX r4600 | |||
|Sound= | |||
* SPU2-X r4600 | |||
* Lilypad r4510 | |||
|Comments=BIOS: USA v02.00, 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., 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/> | <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. | 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. | ||
|Tester=? | |||
}} | |||
{{TestingFooter}} | |||
<!-- | |||
{{TestingHeader|OS=Linux}} | |||
{{TestingEntry | |||
|Status=? | |||
|Region=? | |||
|OS=? | |||
|CPU=? | |||
|GPU=? | |||
|Revision=? | |||
|Graphics=? | |||
|Sound=? | |||
|Comments=? | |||
|Tester=? | |||
}} | }} | ||
{{TestingFooter}} | |||
--> | |||
Revision as of 06:40, 14 August 2014
| 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 configurations on Windows:
| Environment | Configurations | Comments | Tester | ||||
|---|---|---|---|---|---|---|---|
| Region | OS | CPU/GPU | Revision | Graphics | Sound/Pad | ||
| ? | ? |
|
0.9.8 | GSDX r4600 |
|
BIOS: USA v02.00, 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., Varying speeds, down to 30FPS in boss battles. Software mode (F9) in older GSdx revisions (r3693) can actually be faster.
|
? |
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).