Raw Danger!: Difference between revisions

Jump to navigation Jump to search
21 bytes removed ,  10 October 2011
m
no edit summary
mNo edit summary
mNo edit summary
Line 52: Line 52:
* 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). 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 postprocessing 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 use of postprocessing filters. Some filters create huge graphical errors which make the game difficult to play while on hardware mode, but completely playable on software mode. The game is completely playable to the end of the game plus whatever extras the game has. 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.




Line 71: Line 71:
|linuxcomment      =
|linuxcomment      =
<!-- Minimal PC specs -->
<!-- Minimal PC specs -->
|cputype          = Intel® Xeon® Processor E5410
|cputype          = Intel i5 2500k CPU (3.3Ghz Turbo set at 3.7Ghz)
(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; if you have 1GB of VRAM, the game should be CPU limited.
|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.
279

edits

Navigation menu