Corrupting the PSX

by Mismagius

Corrupting the PSX

Introduction

Corrupting the PSX is quite complex when compared to NES and SNES, and can be more difficult than floating point based systems such as the GC/Wii, but it’s still quite feasible for beginners.

Recommended setup: Vector Engine Limiter: _[MIPS]_AllBranches, Value: _[MIPS]_AllBranches Limiter: _[MIPS]_AllBranches, Value: _MIPS_NOP Limiter: _[AnySystem]_AnyFixedPoint, Value: _MIPS_NOP Recommended Intensity: 50-200

Recommended Settings

For most games it is rarely ever worth messing with anything other than the MainRAM. The GPURAM will specifically target textures and sprites. The SPURAM will only mess with the audio, but doesn’t do much other than popping sound and maybe stuttering. BiosROM won’t do anything other than crash the system when corrupting a game. DCache won’t usually do anything worthwhile and the System Bus is simply all of these together.

For Vector Engine settings, any of the MIPS lists into MIPS_NOP (same as Zero) will work most optimally. AllBranches also works into AllBranches as well as it does with NOP. You can also take the _[AnySystem]_AnyFixedPoint (or Any32) lists and pair them with a NOP, but these will usually need very low intensity. In general we’re talking anywhere from 10 intensity to 200.

Expected Results

Most of the effects you will notice when corrupting the PSX with the MIPS lists will affect the game’s logic, differently than the NES/SNES, where it is more common to get clown vomit and audio corruptions. Since games will often store audio, video and models using raw data, you can mostly affect the way they are rendered on screen, but hardly ever change their properties with lists alone.

	An example of texture corruption effects.
	An example of model/rendering corruption effects.
	An example of code corruption effects.