RTC Dev Discord

The Real-Time Corruptor for BizHawk is a Dynamic Corruptor for emulated games. More than a rom corruptor, the RTC works by modifying live data from the virtualized memory chips of emulated systems allowing both rom corruption and ram corruption in real-time.

Quick Start

The Real Time Corruptor was designed with ease of use in mind, if you want to get right into the action simply load a ROM and click “Easy Start” then "Start with Recommended Settings" and you are away! (Instant results not always guaranteed)

Fundamentals of RTC

First, let’s go over the basic fundamentals of how this corruptor functions.

Video game corruption happens when an emulated video game's program files are altered, either in the emulated game’s memory (RAM) or in the ROM itself. A real-time corruption is when the corruption itself occurs while the game is running or when the effects can be altered on a time basis.

RTC is a mod for BizHawk, which means that any emulated system that BizHawk supports should be compatible. Every system is detailed as a series of memory chips known as Memory Domains. The corruption will be generated for the selected domains in the main window. Certain engines/plugins may ignore the selected domains as part of their design.

What is usually known as an iteration in static corruptors, is called a Blast in the RTC. A blast consists of a series of operations that are to be applied in the data located on the emulated game’s memory banks. (RAM, VRAM, ROM, etc.)

The Auto-Corrupt function attaches the blast generation to the emulated game’s clock. Smaller blasts on a fast clock will create a constant flow of randomly generated corruption. This flow can be controlled by three parameters: The Error Delay, which is a divider linked to the game clock, The Intensity which is a multiplier for the number of corruption units to be generated (which depends on the selected engine). The Blast Radius determines how the corruption is spread on the selected domains.

Frequently asked questions

What is the difference between Attached Mode and Detached Mode?

As of 3.50, Attached mode has been deprecated and standard operation should take place in detached mode.

RTC doesn't start on my computer

-> Have you tried stock Bizhawk? Do note, that as of Bizhawk 2.x, Bizhawk is 64bit only and supports operating systems Windows 7 and upwards.

Alternatively, the "Start BizHawk without RTC" option will load BizHawk without the Mod.

-> Have you installed the prereqs? This is essential for BizHawk to run properly. You can grab those from there too:

-> Make sure your computer is decent. If it's too old then maybe the rendering options of BizHawk may not work. We've seen that problem happen with old Core2Duo chipsets for computers using Internal Graphics.

Why does RTC wants to be allowed in the Windows Firewall?

RTC uses networking for a bunch of stuff. As it's split between two processes, they need a way to communicate. To do this, they use TCP and UDP. This can prompt Windows Firewall.

Why are certain RTC Cores running slow or RTC running slow in general

BizHawk is one hell of an emulator. It features a ton of emulator cores and tools to create Tool-Assisted Speedruns. In order for these speedruns to be accurate to the real-life systems that they emulate, some of those do extra operations and disable optimizations that might cause faster but inaccurate emulation.

Some emulator cores are faster than others. QuickNes is generally faster than NesHawk for example.

Unfortunately, if the whole thing is still too slow, your only solution might be to upgrade your computer. For comparison, RTC works just fine on a mobile 2nd-Gen Core i3.

A certain Emulator core doesn't work with RTC

All normal cores within BizHawk should work fine although a libretro core loaded into Bizhawk won't work. If you run into issues, join the RTC Discord and we can provide support.

Can RTC work with another emulator than BizHawk?


Visit the Tips, tricks and quirks part of the guide for more details