Bureaucrats, ninja, Administrators
67,565
edits
Raw Danger!: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{infobox | {{infobox | ||
|image = Raw-danger.jpg | |image = Raw-danger.jpg | ||
|caption = Raw Danger! | |caption = Raw Danger! | ||
| Line 32: | Line 32: | ||
|linuxstatusNTSCJ = | |linuxstatusNTSCJ = | ||
|macstatusNTSCJ = | |macstatusNTSCJ = | ||
<!-- Windows | }} | ||
| | |||
| | [[Category:Temp - unverified automatically converted pages]] | ||
| | <!-- Windows and Linux testing tables (remove comment signs on usage, for Macintosh you have to add the same lines begin with {{TestingHeader|OS=Mac}}) --> | ||
| | {{TestingHeader|OS=Windows}} | ||
| | {{TestingEntry | ||
| | |Status=? | ||
| | |Region=? | ||
| | |OS=? | ||
| | |CPU=Intel i5 2500k CPU (3.3Ghz Turbo set at 3.7Ghz) | ||
| | |GPU=ATI Radeon HD 5770 | ||
|Revision=PCSX2 0.9.9 r4713 | |||
|Graphics=GSdx r4675 | |||
|Sound= | |||
* SPU2-X r4701m | |||
* LilyPad r4656 | |||
|Comments=BIOS: SCPH39001, HACKS: | |||
'''Hacks:''' | '''Hacks:''' | ||
* INTC Spin Detection is safe. | * INTC Spin Detection is safe. | ||
| Line 51: | Line 56: | ||
* 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. VU Cycle Stealing also reduces the GS load when using software rendering, although it is not recommended as the game quickly becomes very choppy. | * 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. VU Cycle Stealing also reduces the GS load when using software rendering, although it is not recommended as the game quickly becomes very choppy. | ||
* EE Cyclerate is safe. | * EE Cyclerate is safe. | ||
* Multithreaded VU (mtVU) is safe. | * Multithreaded VU (mtVU) is safe., 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. | ||
As of August 29, 2011, this game is not listed on the official compatibility list (PAL version)., Most of the GPU load is taken up by the broken color filter. | |||
|Tester=? | |||
}} | |||
{{TestingFooter}} | |||
<!-- | |||
<!-- | {{TestingHeader|OS=Linux}} | ||
| | {{TestingEntry | ||
|Status=? | |||
| | |Region=? | ||
| | |OS=? | ||
| | |CPU=? | ||
| | |GPU=? | ||
| | |Revision=? | ||
|Graphics=? | |||
|Sound=? | |||
| | |Comments=? | ||
| | |Tester=? | ||
| | |||
| | |||
| | |||
}} | }} | ||
{{TestingFooter}} | |||
--> | |||
==Known Issues== | ==Known Issues== | ||