Raw Danger!: Difference between revisions
no edit summary
m (21 revisions) |
MyDreamName (talk | contribs) No edit summary |
||
| Line 13: | Line 13: | ||
|CRCsNTSCU = 2905C5C6 | |CRCsNTSCU = 2905C5C6 | ||
|releasedateNTSCU = June 19, 2007 | |releasedateNTSCU = June 19, 2007 | ||
|statusNTSCU = | |statusNTSCU = 2 | ||
|linuxstatusNTSCU = | |linuxstatusNTSCU = | ||
|macstatusNTSCU = | |macstatusNTSCU = | ||
| Line 29: | Line 29: | ||
|CRCsNTSCJ = C988ECBB | |CRCsNTSCJ = C988ECBB | ||
|releasedateNTSCJ = March 30, 2006 | |releasedateNTSCJ = March 30, 2006 | ||
|statusNTSCJ = | |statusNTSCJ = 2 | ||
|linuxstatusNTSCJ = | |linuxstatusNTSCJ = | ||
|macstatusNTSCJ = | |macstatusNTSCJ = | ||
| Line 51: | Line 51: | ||
* EE Cyclerate is safe. | * 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). Saving using virtual memory cards is much faster than it is on a real console (I timed 18 seconds for the console). | |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). The game is playable using software rendering. | ||
<!-- Linux specs --> | <!-- Linux specs --> | ||
|linuxpcsx2ver = | |linuxpcsx2ver = | ||
| Line 70: | Line 70: | ||
(12M Cache, 2.33 GHz, 1333 MHz FSB) | (12M Cache, 2.33 GHz, 1333 MHz FSB) | ||
|gputype = ATI Radeon HD 5770 | |gputype = ATI Radeon HD 5770 | ||
|pccomment = A gamefix which lowers the amount of VRAM needed to run this game is currently in development. As the modification currently stands | |pccomment = A gamefix which lowers the amount of VRAM needed to run this game is currently in development. As the modification currently stands; if you have 1GB of VRAM, the game should be CPU limited. | ||
}} | }} | ||
| Line 78: | Line 78: | ||
* '''Affected Game Versions:''' All (as of GSdx r4675) | * '''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. | * '''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, | * '''Solution:''' No definitive solution known, a fix is being worked on. Until then, software rendering can be used as a work around, and it should be faster than hardware mode for this game. | ||
===Broken Postprocessing Effects=== | ===Broken Postprocessing Effects=== | ||
| Line 84: | Line 84: | ||
* '''Affected Game Versions:''' All (as of GSdx r4675) | * '''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. | * '''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, | * '''Solution:''' No definitive solution known, a fix is being worked on. Until then, software rendering can be used as a work around, and it should be faster than hardware mode for this game. | ||
===Missing Polygons=== | ===Missing Polygons=== | ||
| Line 90: | Line 90: | ||
* '''Affected Game Versions:''' All | * '''Affected Game Versions:''' All | ||
* '''Description:''' Some polygons will be missing during gameplay, most notably on character models. | * '''Description:''' Some polygons will be missing during gameplay, most notably on character models. | ||
* '''Solution:''' This is caused by the skipdraw hack being set to | * '''Solution:''' This is caused by the "skipdraw" hack in GSdx being set to anything but 0. Setting this back to 0 should fix the problem. | ||