Mario Kart Wii with WiiCompiled: Wheel Wizard beta mode, first shaders and a 60 FPS race
ItsOOGWAY · PC guides & recorded tests
Mario Kart Wii with WiiCompiled: Wheel Wizard beta mode, first shaders and a 60 FPS race
Play Mario Kart Wii on PC with this step-by-step WiiCompiled setup guide, including Wheel Wizard, Retro Rewind and a real 60 FPS race test.
The key checkpoint: Use Wheel Wizard with the WiiCompiled beta option enabled for this route. The earlier setup-window problem and first-launch shader work are different stages.
Before you start
- Use the recorded versions and the supported inputs listed in the original notes below.
- Compare the last successful checkpoint before choosing a fix.
- Keep original files, relevant logs and a known working setup when testing changes.
Resources from this video
Links, downloads & documentation
Every original URL from the video description is collected here, including recorded releases, setup discussions and related videos. Use the version-specific notes when following a recorded build.
Watch the complete video
Open this video on YouTube ↗. Screenshots below link to their exact recorded moments.
Walkthrough 01
Separate the game backup from the launcher
There are two separate things here. Wheel Wizard is the application that manages the installation. WiiCompiled is the native PC project that we are installing through it. Once we reach the game, we will check the menus, get into a race, and let it run long enough for you to see the result yourself. Before downloading anything, get your own Mario Kart Wii disc backup ready. The WiiCompiled project currently specifies a clean PAL image, with the game ID R M C P zero one.
Do not choose a different region just because the name says Mario Kart Wii, and do not assume that renaming a folder changes the game inside it. The project lists Windows ten or eleven, sixty-four bit, and about twenty gigabytes of free space during installation. Check the linked requirements against your hardware before starting. Keep that space available while the installer is working, rather than only making room for the final game.
Walkthrough 02
Use the recorded Wheel Wizard route
First, open the official WiiCompiled GitHub page. The links will be in the description, so you can go straight to the projects used here. The release shown in my recording is version zero point nine point zero, which is described as the version one beta. I originally downloaded WiiCompiled Setup directly. When I launched it, this message appeared explaining that Mario Kart WiiCompiled is installed through Wheel Wizard. If you see the same message, that is the handoff to the launcher.
You do not need to keep opening the same file and waiting for a different result. Follow the official Wheel Wizard link, open Releases, and download the Windows application from the release assets. In this recording, that file is called Wheel Wizard Windows dot exe. Download the application itself, rather than choosing the source-code archive by mistake. Keep the launcher somewhere you can find again, and open it. We are using Wheel Wizard version two point six point two in this walkthrough.
A later release may move a button, but I will point out the names of the settings so you know what to look for.
Walkthrough 03
Select a supported disc image
Now prepare the disc image. If your own backup is stored inside an archive, extract that archive first. Wait until extraction finishes, then open the resulting folder and find the actual game image. The archive, the folder containing it, and the image inside are three different selections. The game-file picker needs the image.
Walkthrough 04
Enable the WiiCompiled beta choice
Before going through the location settings, open the gear icon in Wheel Wizard and go to Other. Look for Enable WiiCompiled, marked beta, and turn it on. When you return to Home, the main panel should say WiiCompiled. That label is our useful checkpoint before we begin the native installation. This also explains the confusing Dolphin fields that appear earlier in my recording. Wheel Wizard supports another launch route as well. I spent time filling those fields before switching modes, including an executable selection that you should not copy.
We are following the WiiCompiled route here, so do not point a Dolphin field at the Wheel Wizard application just to make an indicator turn green. For the game location, open Settings and the Wheel Wizard location page. Beside Mario Kart Wii Game File, click Change. Browse to your extracted disc image, select the file, and click Open. Check that the selected location is the file you intended to use. If the file is rejected, check the image and region first.
Repeating the same selection will not repair an incompatible or modified backup. Go back to the requirements on the project page and compare them with the image you prepared.
Walkthrough 05
Complete Retro Rewind and compilation
The recording also includes a Retro Rewind download before the native build. That is relevant because Retro Rewind is the version you will see running at the end. I will keep that stage visible, including the download completing and the files being extracted, so it does not suddenly appear installed between two cuts. The part you do not need to sit through is several minutes of a progress bar. I am speeding up the waiting, while keeping the beginning, the stage changes, and the completed result.
You can leave the application working at its normal speed on your own computer. With WiiCompiled enabled, return to Home and click Install. The installation window first downloads the WiiCompiled installer, and later shows the game compilation stage. Those are different stages of the same setup, so reaching another progress bar does not mean you have gone back to the beginning. During my recording, the compilation message specifically says this is the longest step. Give it time to finish.
The useful thing to watch is the stage message and the eventual completed state, rather than expecting the estimated time to count down perfectly every second.
Walkthrough 06
Check first shaders, controls and a real race
Once the installation finishes, Home changes to a green Play button. That is the point where I launch the game. We have now gone from selecting the game image to having an installed build ready to start. On this first launch, there is another black window, but it is different from the message at the beginning. This one says WiiCompiled and shows shaders compiling, with a remaining count. In my recording, that count decreases before the title screen appears.
Let that preparation finish. Now we reach the Mario Kart Retro Rewind title screen. Continue into the game, create or select your license, and choose a Mii. I use the guest selection shown here and then enter Single Player. From there, I choose the race mode, character, vehicle, and the driving options shown on screen. These menu choices are preferences for the race. They are not extra Windows installation steps, so you can choose the character and driving style you actually want to use.
Before racing, make sure you can move through the menus and confirm a selection with your controller. If you need to change the native build's controls or display settings, the project documents F ten as the in-game settings shortcut. I am not claiming a custom controller profile or a graphics preset that I did not demonstrate in this recording. Here is the result. The race loads, the controls respond, and the frame counter reads sixty in the gameplay samples shown.
This is a test on my machine and this course. It gives you something concrete to compare with your setup, rather than promising the same performance on every computer or every track. I am going to leave a stretch of the race at normal speed now. You can see the driving, items, and other racers without an installation time-lapse making the game look faster than it is. And that is the race finished. We started with the launcher handoff, prepared the game image, enabled WiiCompiled, completed the installation, and reached a working race with Retro Rewind.
If your result differs
| Situation | Next useful check |
|---|---|
| The process stops at a different checkpoint | Record the exact message, current build and last successful stage. Compare that stage with the matching video section. |
| A setting is selected but the result differs | Repeat the same scene and change one option at a time. A menu target does not establish measured performance. |
| A newer release changes the interface | Check the linked release notes and instructions. This companion preserves the recorded route and its limitations. |
Comments
Post a Comment