Raw Danger!: Difference between revisions

Added a hyperlink to Irem. Corrected something involving VU Cycle Stealing. Still can't figure out why I can't get a bulletpoint for the first hack. Sadface.
(Another known issue.)
(Added a hyperlink to Irem. Corrected something involving VU Cycle Stealing. Still can't figure out why I can't get a bulletpoint for the first hack. Sadface.)
Line 4: Line 4:
|developer        = Irem
|developer        = Irem
|genre            = Action Adventure RPG, Disaster, Survival
|genre            = Action Adventure RPG, Disaster, Survival
|gameinfo          = 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|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.
|gameinfo          = 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|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.
|wikipedia        = http://en.wikipedia.org/wiki/Raw_Danger!
|wikipedia        = http://en.wikipedia.org/wiki/Raw_Danger!
|reviewlinks      = http://ps2.ign.com/objects/703/703781.html
|reviewlinks      = http://ps2.ign.com/objects/703/703781.html
Line 33: Line 33:
|macstatusNTSCJ    =
|macstatusNTSCJ    =
<!-- Windows specs -->
<!-- Windows specs -->
|pcsx2ver          = PCSX2 0.9.8 r4600
|pcsx2ver          = PCSX2 0.9.9 r4713
|gsname            = GSdx  
|gsname            = GSdx  
|gsver            = r4675
|gsver            = r4675
|soundname        = SPU2-X
|soundname        = SPU2-X
|soundver          = r4600m
|soundver          = r4701m
|padname          = LilyPad
|padname          = LilyPad
|padver            = r4510
|padver            = r4656
|dvdplugname      = cdvdGigaherz
|dvdplugname      = cdvdGigaherz
|dvdplugver        = r4510
|dvdplugver        = r4510
Line 48: Line 48:
* mVU Flag Hack is safe.
* mVU Flag Hack is safe.
* mVU Block Hack is safe.
* mVU Block Hack is safe.
* VU Cycle Stealing is safe, although may cause slowdowns on higher levels as is typical.
* Any level of VU Cycle Stealing can contribute to any of the severe graphical errors. Typically, this causes vertical green lines in addition to whatever graphical error appears.
* EE Cyclerate is safe.
|fpsinfo          = 8-50 FPS
|fpsinfo          = 8-50 FPS
|comment          = 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).
|comment          = 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). Saving using virtual memory cards is much faster than it is on a real console (I timed 18 seconds for the console).
<!-- Linux specs -->
<!-- Linux specs -->
|linuxpcsx2ver    =
|linuxpcsx2ver    =
279

edits