Project

General

Profile

Actions

Emulator Issues #6269

closed

Mario Kart Double Dash Darkened Player Character in Viewport (D3D11)

Added by JMC4789 almost 11 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
Category:
GFX
% 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:

Description

Game: Mario Kart Double Dash - GM4E01

Sometimes (About 50% for me) the characters you choose will be severely darkened when using OpenGL or D3D9. I tried messing with the texture cache and EFB Settings.

Not sure, but this may be related to - code.google.com/p/dolphin-emu/issues/detail?id=6169 where there is a similar darkened character problem in the two back-ends.

Here is comparison screenshots

http://i.imgur.com/fqXcQ8T.jpg

Reproducing this is relatively easy, just select any characters (I find Wario to trigger it the most) and go into a race. If it doesn't happen, try again. Using 2/4 player increases your chances of it happening because it happens per viewport. It can happen in one player, though.

I tested this is 3.0, 3.5 and 3.5-1251. This has always happened to my knowledge.

Here's a Fifolog to make seeing the issue easier - http://www.mediafire.com/download.php?8ubm4gjmb4fwr2b


Related issues 3 (0 open3 closed)

Related to Emulator - Emulator Issues #6543: Blacked out Graphics in Mega Man Network TransmissionFixed

Actions
Related to Emulator - Emulator Issues #6125: Fire Emblem: Radiant Dawn [Wii] shading/lighting problemFixed

Actions
Related to Emulator - Emulator Issues #5453: Super Mario Galaxy 2 - Directx11 lighting bugFixed

Actions
Actions #1

Updated by JMC4789 almost 11 years ago

It apparently can happen to computer opponents, also per-viewport. Player 1 will see them correctly but Player 2 won't.

This makes it much more common to find the error in GrandPrix mode, because it doesn't always have to be your kart. I can't believe I didn't notice before.

Actions #2

Updated by JMC4789 almost 11 years ago

AND, the name of the issue report is correct, not my typo. This is an OpenGL/D3D11 issue, while D3D9 is totally unaffected by it.

You can confirm it for yourself in the fifo-log. Sorry for all the quick updates, but someone decided to remind me after I had already commented. MaJoR.

Actions #3

Updated by Billiard26 almost 11 years ago

  • Issue type set to Bug
  • Category set to gfx
Actions #4

Updated by MayImilae over 10 years ago

  • Status changed from New to Accepted

Reproduced. It was a little hard to get in OpenGL, but I got it eventually. D3D11 was instantaneous.

Tested on:
3.5-1593 win64
Windows 7 x64
Core i5 3570K @ 4.7ghz
nVidia GeForce GTX 760

Actions #5

Updated by JMC4789 over 10 years ago

This is fixed in OpenGL as of revision 75f2738f5c32bc7a28078983d1a7da2c31e7acbf

Actions #7

Updated by JMC4789 over 9 years ago

  • Status changed from Accepted to Fixed
Actions #8

Updated by pokechu22 about 2 years ago

Actions #9

Updated by pokechu22 about 2 years ago

Actions #10

Updated by pokechu22 about 2 years ago

Actions

Also available in: Atom PDF