Emulator Issues #12195

Mario Kart Wii graphic layering/clipping issue

Added by McAwesome 9 months ago. Updated 7 months ago.

% Done:


Operating system:
Issue type:
Relates to usability:
Relates to performance:
Relates to maintainability:
Regression start:
Fixed in:


Game Name?

Mario Kart Wii

Game ID? (right click the game in the game list, Properties, Info tab)

RMCE01 (00010004524d4345)

MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)


What's the problem? Describe what went wrong.

Graphic layering/clipping issue.
I.e: Characters and vehicles appear messed up, parts of the courses appear in front of other parts (which should be infront) (e.g: water and other things appearing in front of the road when they're on the other side of the course

What steps will reproduce the problem?

Run the game and go to character select and/or enter a course.

Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.

Yes (v5.0-12322)

Is the issue present in the latest stable version?

Unk (v5.0) (fails to run game -- "Tried to decrypt data from a non-Wii volume")
No (v5.0-9453)

If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool and anyone who is building Dolphin on their own can use git bisect.)

First Broken: v5.0-9638 [Move a significant amount of video backend logic to VideoCommon (PR #7753 from stenzek)]
Last Working: v5.0-9633 [DolphinQt: clean up includes (PR #7822 from Tilka)]

Note: Manually tested

If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here:

Attached are 3 FIFOLogs and 1 screenshot from each version. Note that the screenshot for both versions was taken from 9633_MKWii-3.dff, frame 0 to 1.

What are your PC specifications? (CPU, GPU, Operating System, more)

CPU: Intel Xeon E5450 @ 3.00 GHz
GPU: ATI Radeon HD 4770
OS: Windows 10 Pro x64
RAM: 8.00 GB DDR2 @ 800.0 MHz

Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)

Using OpenGL Backend
Using default graphics settings, except:

  • Show FPS: Enabled
  • Compile Shaders Before Starting: Enabled
  • Skip EFB Access from CPU: Enabled
  • Ignore Format Changes: Disabled [Auto]
  • Defer EFB Copies to RAM: Disabled [Auto]
  • Borderless Fullscreen: Enabled

(In version v5.0-9633) (3.97 MB) From version 5.0-9638 McAwesome, 07/20/2020 08:28 AM (3.84 MB) From version 5.0-9633 McAwesome, 07/20/2020 08:29 AM
9638_MKWii.png (2.23 MB) 9638_MKWii.png From version 5.0-9638 McAwesome, 07/20/2020 08:37 AM
9633_MKWii.png (2.16 MB) 9633_MKWii.png From version 5.0-9633 McAwesome, 07/20/2020 08:37 AM


#1 Updated by McAwesome 9 months ago

The FIFOLogs are in a zip due to size.

#2 Updated by JosJuice 9 months ago

  • Regression start set to 5.0-9638
  • Regression changed from No to Yes
  • Milestone set to Current

#3 Updated by JMC4789 7 months ago

  • Assignee set to Stenzek

I didn't even know we supported an AMD Radeon 4xxx card still. Holy crap.

Are we targeting those GPUs currently?

Also available in: Atom PDF