Real-Time Corruptor: Tips, tricks and quirks
Not all memory domains can be rewinded
The default selected memory domains in RTC are supposed to be rewindable. If you select all or add more, you might end up in situations where rewind cannot erase corruption. Game Protection in Detached mode can allow for a more compatible but chunkier rewind.
Time travel to a parallel universe
When you rewind using bizhawk, corruption also get rewinded. After you've let go of the rewind button, different corruption will be applied if Auto-Corrupt is enabled. For example, if the music dies, you can quickly rewind before it died and it should stay alive in this parallel universe.
Playing with the settings
All the games corrupt differently. Some games may give better results with certain engines or settings.
N64 works best with Vector engine but if you are able to target specific zones using VMDs, you can get excellent corruptions with the nightmare engine.
The external ROM plugins are additional options that can allow you to get crazy results.
Control your game from any window
Annoyed that you have to constantly click back and forth between the RTC window and the Bizhawk window in detached mode? Toggle "Accept Background Input" (Config > Customize)
If you think you've got a masterpiece in your stockpile, try rerolling it a few times. Maybe you'll end up with something better or even completely different. Rerolling reuses the same target addresses but generates new corruption for it. You might find a case where different values in the same addresses allow you to get cooler stuff
Sanitizing and merging
Most of the times, corruptions tend to corrupt a lot of useless addresses which can result in game crashing. Sanitizing corruptions using the Blast Editor can allow you to reduce a corruption to its minimal state. Sometimes, an interesting effect is caused by a single corruption unit. When corruptions are sanitized, they are more stable and therefore can be merged more easily. Using this method, you can craft custom corruptions with very specific effects.
Working off existing knowledge
Some games are very well documented online. You can find documentations on ROM layouts and exploit this knowledge in order to generate VMDs and target specific areas of a ROM. The same can apply for other memory domains, if such documentation exists.
N64 is running slow
By default, BizHawk doesn't enable rewind on large systems like N64 but RTC does. You can disable Large Savestates in the Rewind options.
Large Savestates require a powerful cpu and an SSD to run well. If you don't then you may very well need to disable Large Savestates for rewind.
Detached mode timing out
RTC3 uses a fairly new technology called NetCore. NetCore allows to split RTC in two processes so your progress is kept even if BizHawk crashes. However, just like BizHawk, NetCore isn't perfect and can sometimes glitch out.
If BizHawk restarts and the RTC Main window doesn't come back on, you might need to restart the whole thing. If the Glitch Harvester was open, you will notice an "Emergency Stockpile Save" button that can save your progress. Most of the time, RTC will survive BizHawk crashes but the unexpected can happen.
In extremely rare cases, you may find that newly generated corruptions don't properly stash in the Glitch Harvester. You can fix this by pressing "Clear History"
On this same note, Detached Mode uses more CPU and RAM than Attached mode. Creating huge blasts on detached mode can freeze the program for a few seconds and even jam NetCore if done repeatedly. If your computer is too slow for Detached mode, consider using Attached Mode with the classic Auto-KillSwitch.
As always, save your progress regularly.
N64 can be quirky and unstable
When corrupting N64 games, if you're using autocorrupt or manual blast and rewind or if you "send raw to stash" and try playing back the stashed corruption, you may find that Bizhawk crashes This is a result of how the emulator works. You can prevent these crashes by changing the N64 CPU mode to "Pure Interpreter" but do note, you'll experience more crashes overall and it uses significantly more CPU.
Sometimes Bizhawk will just break and throw an error about the core accepting the rom but throwing an exception. This isn't an RTC bug, it's a Bizhawk bug. Just restart BizHawk and you should be fine.
Game Capture Software doesn't work properly with my RTC
Having trouble capturing Bizhawk with OBS or XSplit? Try changing the display option from OpenGL to Direct3D, or vice-versa (Config > Display > Display Method).
Game running slow on some engines
Game running slow after using the Pipe, Freeze, or Hellgenie engines? Try turning down the intensity. These engines are significantly more CPU intensive than other engines.