Bureaucrats, ninja, Administrators
67,565
edits
Raw Danger!: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 57: | Line 57: | ||
* EE Cyclerate is safe. | * 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. | * 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=? | |Tester=? | ||
}} | }} | ||
| Line 100: | Line 97: | ||
|Workaround=There are ways to disable these effects which cause these artefacts, but these leave more minor artefacts and can be a bit of a mess to handle. The easiest workaround is to use software rendering. If software rendering is slow, try setting the 4-byte value of address 2048D824 to 0 using Cheat Engine in order to disable postprocessing color filters and gain a massive speed boost. | |Workaround=There are ways to disable these effects which cause these artefacts, but these leave more minor artefacts and can be a bit of a mess to handle. The easiest workaround is to use software rendering. If software rendering is slow, try setting the 4-byte value of address 2048D824 to 0 using Cheat Engine in order to disable postprocessing color filters and gain a massive speed boost. | ||
}} | }} | ||