Raw Danger!

From PCSX2 Wiki
Revision as of 19:57, 13 June 2011 by MyDreamName (talk | contribs) (Another known issue.)
Jump to navigation Jump to search
Raw Danger!
250px
Raw Danger!
Region NTSC-U:
Serial numbers: SLUS-21501
Release date: June 19, 2007
CRCs: 2905C5C6
Windows Status: Ingame
Linux Status: ?
Mac Status: ?
Region PAL:
Release date: June 8, 2007
Windows Status: ?
Linux Status: ?
Mac Status: ?
Region NTSC-J:
Serial numbers: SLPS-25606
Release date: March 30, 2006
CRCs: C988ECBB
Windows Status: Ingame
Linux Status: ?
Mac Status: ?

Developer(s): Irem
Genre: Action Adventure RPG, Disaster, Survival
Wikipedia: http://en.wikipedia.org/wiki/Raw_Danger!
Game review links: http://ps2.ign.com/objects/703/703781.html
Game review score: 7.5/10 (IGN)
Game description: The second in a series of "disaster" games from the Japanese game development company Irem. Typically known as "Raw Danger!" or "Disaster Report 2", Disaster Report being the first game. The game is referred to as "Zettai Zetsumei Toshi 2: Itetsuita Kiokutachi" (絶体絶命都市2 -凍てついた記憶たち) in Japan. Loosely translated, it means "Desperate Cities 2: Frozen We Remember". A PAL version of the game exists, although it was never released in the UK. It can be found imported from France.

Winlogo.png Test configuration on Windows:

PCSX2 version: PCSX2 0.9.8 r4600
Graphics by GSdx: r4675
Sound by SPU2-X: r4600m
Pad plugin is LilyPad: r4510
DVD plugin is cdvdGigaherz: r4510
BIOS version: SCPH39001

Comments: Game typically runs very slowly on hardware mode, so software mode may or may not be faster. This is due to the amount of filters that the game uses. The tutorial will be the fastest area, considering how small of a map it is and what seems to be the smallest amount of filters. Some filters create huge graphical errors which make the game difficult to play while on hardware mode, but completely playable on software mode. It is unknown if the entire game is playable, but the first chapter is confirmed playable at the least (short method). Hack comments:

  • INTC Spin Detection is safe.
  • Wait Loop Detection is safe.
  • mVU Flag Hack is safe.
  • mVU Block Hack is safe.
  • VU Cycle Stealing is safe, although may cause slowdowns on higher levels as is typical.

Linlogo.png Test configuration on Linux:

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


Pclogo.png PC specs used to test the game:

CPU: Intel® Xeon® Processor E5410

(12M Cache, 2.33 GHz, 1333 MHz FSB)

GPU: ATI Radeon HD 5770


Known Issues

VRAM Usage

  • Type: Slowdown
  • Affected Game Versions: All (as of GSdx r4675)
  • Description: The game uses a massive amount of VRAM when postprocessing filters are used (most times whilst in-game), causing severe slowdown.
  • Solution: No definitive solution known, a fix is being worked on. Until then, software rendering can be used as a work around, although it is typically slower.

Broken Postprocessing Effects

  • Type: GFX Glitches
  • Affected Game Versions: All (as of GSdx r4675)
  • Description: Whenever postprocessing filters are used, they are not rendered correctly by the GSdx plugin. As such, this causes graphical glitches; some more severe than others.
  • Solution: No definitive solution known, a fix is being worked on. Until then, software rendering can be used as a work around, although it is typically slower.

Missing Polygons

  • Type: GFX Glitches
  • Affected Game Versions: All
  • Description: Some polygons will be missing during gameplay, most notably on character models.
  • Solution: This is caused by the skipdraw hack being set to a value of 1 or higher. Since the hack is by default set to 3, this can be fixed by setting the skipdraw hack to 0 in the "gsdx.ini" text file.