Bizhawk Medievil 2 Guide

## Required Downloads for this guide

- Bizhawk "2.8" - **Compatible with community savestates as for BIOS**
- PSX BIOS 55xx
- Copy of Medievil 2 (ISO)

# Emulator Setup

Create a Bizhawk folder and place all contents of the emulator in this folder. The bizhawk folder should some what resemble what is below. The first thing you are going to want to do is navigate to the **Firmware** folder. If it does not exist make sure to create it.

![](/static/blob/1n7v064n.png)

Place all of the SCPH55xx.bin BIOS in this folder. Personally I create a sub folder in here for my games, just so everything is in a somewhat similar location.

![](/static/blob/7n6vk7oz.png)

Make sure to have all of your games files in the same location, bin+cue. Medievil 2 has 2 bin files so make sure all 3 files are together.

![](/static/blob/rnqvom4e.png)

Now as for launching a game first you must launch the emulator "EmuHawk.exe". After you launch it for the first time a config file will be made

![](/static/blob/7e93dlye.png)

One of 2 things will happen when you launch bizhawk for the first time, either you will have it open a window automatically to search for the BIOS or you will be left with the normal Bizhawk blank emulator screen. If you end up with an initial blank screen and no pop up, just navigate to the firmwares section under config

![](/static/blob/ynl9mvln.png)



Under Firmwares search for PSX by scrolling down, and if it is blank make sure to scan and if that does not work manually import the BIOS

![](/static/blob/7z33pwqz.png)

Now that the BIOS is all setup now you need to launch a game for the first time. Now unlike most emulators when you launch a game you use the bin file, but with Bizhawk we have to use the CUE file. Bizhawk also autodetects the region of your game.

![](/static/blob/qny0qwwe.png)![](/static/blob/4zj9jv2n.png)



# **How To Use Autofire + Controller Setup**

Navigate to Config -> Controllers

![](/static/blob/1n8jwlve.png)



There will be 3 tabs for controls, Normal , Autofire, and Analog. For normal controls you are going to want to leave the dpad completely blank. Everything else can be mapped as normal to your controller.

![](/static/blob/3nv25xyz.png)

Now under the Autofire Controls tab you map your dpad to the dpad controls. Leave everything else blank aside from the dpad

![](/static/blob/dz4j1drz.png)

Now to configure autofire now that you have your controller setup. To do this navigate to Config -> AutoFire

![](/static/blob/wzxr605z.png)

To configure autofire you must change both of these values

![](/static/blob/yzr9krgz.png)







**To be continued...**





Bizhawk Submission Guide as of 2025 Q4

# Overview

The purpose of this guide is to show what an acceptable submission for Bizhawk would look like.

### **Turbo Explanation** 

Bizhawk is a tasing emulator which allows us as runners to use specific tools to our advantage. The only tool that us as runners are interested in using is the autofire function. This game has a speed glitch that requires massive amounts of button repetition through out the entirety of the run. Now if you automate this glitch you realize that the run drastically changes. The mindset of how you run the game entirely changes. For example, you enter a room for the first time without autofire, then you do the most optimal path to the room transition. Now let's do that again with autofire, you will notice that you will need many less inputs to reach the room transition. This in theory allows you to make setups for rooms in their entirety. You can enter a room and just hold right to finish the room instead of doing 30 unnecessary inputs to achieve the same goal but slower. The turbo category in itself is a different skillset, different mindset, and just overall takes a different approach to a traditional speedrun of medievil 2.

### Submission Expectations 

When submitting a run for bizhawk you are required to have certain things displayed along side your run. This is mainly to confirm that it is indeed you that is playing the game.

**Example of a proper submission**

![](/static/blob/1n5joxpe.png)

**Requirements**

- Video Footage 
- Input Display
- Frame Counter Display **or** Handcam/physical proof 1/2

**Video Footage -** Make sure your footage is clear and that we can tell what is actually going on in the game. Video must have game audio. If you are going to obscure the game in anyway such as chat windows, or facecam, please make sure that the background is transparent for chats, and for facecam just make sure that it does not obscure anything of importance such as health,gold,inventory.

**Input Display -** Display your controller inputs on video. This can be done by using Bizhawks built in input display via the **messages tab** , or you can use any external input display method (Gamepad Viewer). Using handcam is another option and covers 2/3 of these requirements.

**Frame Counter Display / Physical Proof -** For Bizhawk specifically you are required to show the frame counter or proof that you are actually playing the game. The Frame Counter tells us there is a movie(TAS) being played back. If there is no movie being played back and it is just someone playing then and there you will see 1 number, but if a movie is being played back you will see an appearance of xxxx/xxxx instead of xxxx. This 100% confirms that the game is actively running in real time and being controlled by a player and not a file. Now as for Physical Proof you can either display handcam, or be creative in a sense where you have someone in your stream chat tell you to go to a certain location after your run or something along these lines . The main goal is to prove you are playing the game. Just please make it clear that you are providing such evidence to your run so that we know what to look out for in your footage.

### Cheated Frame Count

![](/static/blob/1n7v024n.png)

### Valid Frame Count

![](/static/blob/7n6vkxoz.png)

### How to Display Frame Counter

First make sure that under "View" you have "Display FrameCounter" Checked off. This can be done for all other information if desired.

![](/static/blob/ynl9m8ln.png)

Config -> Messages

![](/static/blob/rnqvo84e.png)

Select Frame Counter and modify it's position

![](/static/blob/7e93drye.png)

MediEvil 2 Any% (Turbo) Speedrun guide (2022)

#Info
Any% (Turbo) has two changes from normal Any%:

1. You can use a savestate that has previously viewed all cutscenes in order for them to all be skippable.
2. You may use autofire in order to perform the speed glitch without injury. Autofire has been mapped to the DPAD.

Everything required to make this work is in a pack called "MediEvil_2_Settings_Pack.zip" that you can find under "Resources" -> "Tools" -> "Any% (Turbo) settings".
You will have to download BizHawk 2.8 (the emulator) and PSX BIOS collection yourself elsewhere.

If you use a controller other than PS2 you may have to map the buttons manually. Simply copy what I have set. You have to run the game before you can edit controls.

#Emulator setup

**__Required files__**
[quote]1. Download "BizHawk 2.8"
2. Download PSX BIOS collection ("SCPH5500.BIN", "SCPH5501.BIN", "SCPH5502.BIN")
3. Download "MediEvil_2_Settings_Pack.zip"[/quote]

**__Setup__**
[quote]1. Place "config.ini" into "BizHawk" folder 
2. Place "MediEvil_II_USA.No-Cutscenes-by-Crash41596.State" into PSX/State folder 
3. Place PSX BIOS collection into "Firmware" folder[/quote]

[quote]To load the no cutscenes savestate:
File -> Load state -> Load named state -> MediEvil_II_USA.No-Cutscenes-by-Crash41596.State[/quote]

Name	Autor
Bizhawk Medievil 2 Guide	Crash41596 11 months ago
Bizhawk Submission Guide as of 2025 Q4	Crash41596 11 months ago
MediEvil 2 Any% (Turbo) Speedrun guide (2022)	NoobKillerRoof 4 years ago
New Setup for Whitechapel	Thefoxy1978 5 months ago