Raw Danger!: Difference between revisions
no edit summary
MyDreamName (talk | contribs) m (1 revision) |
MyDreamName (talk | contribs) No edit summary |
||
| Line 44: | Line 44: | ||
|biosver = SCPH39001 | |biosver = SCPH39001 | ||
|hacks = | |hacks = | ||
'''Hacks:''' | |||
* INTC Spin Detection is safe. | * INTC Spin Detection is safe. | ||
* Wait Loop Detection is safe. | * Wait Loop Detection is safe. | ||
| Line 52: | Line 53: | ||
|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). The game is playable using software rendering. The game suffers from unsteady FPS and long loading times on both the console and emulator. Frameskipping causes severe graphical errors; but can also cause the bad postprocessing filters to be removed - unuseful since the game is unplayable using frameskipping. | |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. The game suffers from unsteady FPS and long loading times on both the console and emulator. Frameskipping causes severe graphical errors; but can also cause the bad postprocessing filters to be removed - unuseful since the game is unplayable using frameskipping. | ||
*As of August 29, 2011, this game is not listed on the official compatibility list (PAL version). | |||
<!-- Linux specs --> | <!-- Linux specs --> | ||
|linuxpcsx2ver = | |linuxpcsx2ver = | ||
| Line 85: | Line 88: | ||
* '''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, and it should be faster than hardware mode for this game. | * '''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. | ||
[[Category:Not on Compatibility List]] | |||