Raw Danger!: Difference between revisions

Raw Danger! (view source)

Revision as of 17:51, 14 September 2014

420 bytes removed , 14 September 2014

no edit summary

Ngng

Bureaucrats, ninja, Administrators

67,565

edits

@@ Line 34: / Line 34: @@
 }}
-[[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=?
+|Status=1
-|Region=?
+|Region=NTSC-U/J
+|OS=?
+|CPU=Intel i5 2500k CPU (3.3Ghz Turbo set at 3.7Ghz)
+|GPU=ATI Radeon HD 5770
+|Revision=PCSX2 0.9.8 r4600
+|Graphics=GSdx 4600
+|Sound=
+* SPU2-X r4600m
+* LilyPad r4510
+|Comments=BIOS: SCPH39001, FPS: 8-50 FPS. 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. 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.
+|Tester=MyDreamName
+}}
+{{TestingEntry
+|Status=2
+|Region=NTSC-U/J
 |OS=?
 |CPU=Intel i5 2500k CPU (3.3Ghz Turbo set at 3.7Ghz)
@@ Line 48: / Line 61: @@
 * SPU2-X r4701m
 * LilyPad r4656
-|Comments=BIOS: SCPH39001, HACKS:
+|Comments=Any level of VU Cycle Stealing can contribute to any of the severe graphical errors. 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. The game is completely playable to the end of the game plus whatever extras the game has. The game is playable using software rendering.
-'''Hacks:'''
+|Tester=MyDreamName
-* INTC Spin Detection is safe.
-* Wait Loop Detection is safe.
-* mVU Flag Hack is safe.
-* mVU Block Hack is safe.
-* 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.
-* 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.
-|Tester=?
 }}
 {{TestingFooter}}