Project

General

Profile

Actions

Emulator Issues #10436

closed

After Wii safety warning, Vulkan shows black screen if anti-aliasing is set to on

Added by huginn over 7 years ago. Updated over 7 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:
5.0-5150

Description

Game Name?

Various games: Super Mario Galaxy, Wii Sports Resort, New Super Mario Bros.

(Not Donkey Kong Country Returns, though.)

Game ID? (right click the game in the game list, properties, info tab)

Various games, but not all.

MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)

Various games, but not all.

What's the problem? Describe what went wrong.

After the Wii safety warning displays, the game proceeds (judging by sound) but renders nothing.

What steps will reproduce the problem?

  1. Use Vulkan back end.
  2. Set Anti-Aliasing to 2x MSAA or higher. (Anything that puts the GFX.ini setting at MSAA = 0x00000002 or higher will work.)
  3. Start the game. After the Wii safety warning, sounds will play as normal, but the screen will be black.

Setting MSAA = 0x00000001 fixes this.
Alternatively, not using Vulkan fixes this.

Some games aren’t affected at all, but many seem to be.

Which versions of Dolphin did you test on? Does using an older version of Dolphin solve your issue? If yes, which versions of Dolphin used to work?

5.0-4992

Vulkan used to work fine, but I couldn’t say when. I’ve been playing GameCube games so long I’m not sure how long this has affected Wii games.

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

i5-4690k @ 4.5 GHz, GTX 960 @ 2 GB, 16 GB DDR3

I’m not running Afterburner, RivaTuner, or anything like that—no antivirus, no GeForce Experience.

Is there any other relevant information? (e.g. logs, screenshots,
configuration files)

Thank you, by the way, to whoever fixed the bug, present in 5.0-4873, that required multiple tries to turn anti-aliasing entirely off. I was about to report that, too, and switched to the newest version before doing so—and it was fixed.

Actions

Also available in: Atom PDF