Project

General

Profile

Actions

Emulator Issues #7007

closed

Super Mario Galaxy 2 Underwater Fog Renders Incorrectly (all backends)

Added by JMC4789 about 10 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 Name?

Super Mario Galaxy MORE

Game ID?

SB4E01

What's the problem? Describe what went wrong in few words.

Fog doesn't render correctly in the underwater stages at the very least. Rather than going through a bunch of hoops and explaining what happens, let me show you.

Console: http://www.youtube.com/watch?v=bC9KiHUP_Tc
Emulator: http://www.youtube.com/watch?feature=player_detailpage&v=MgD3Q1ngvlg

Screenshots Provided for those who don't want to use youtube. I really think in motion shows the glitch more accurately, but screenshots also show the problem.

Console: http://i.imgur.com/dcWEFya.png
Emulator: http://i.imgur.com/US0pBoB.jpg

What steps will reproduce the problem?
[Don't assume we have ever played the game and know any level names. Be as
specific as possible.]

  1. Use the cheat included in Dolphin for 242 stars if you don't have a save file
  2. If you use the cheat, you must play through the intro, then zoom right past the castle to the world map. After that go to world 6, and select Slimy Spring Galaxy.
  3. Observe

Special note: D3D9 used to do something different because it probably emulated differently. In the 10 years of Dolphin video, D3D9 was used to avoid this very awkward looking glitch.

Dolphin 3.5 and 3.5-367 are old versions of Dolphin that have
known issues and bugs, so don't report issues about them and test the
latest Dolphin version first.
Which versions of Dolphin did you test on?

Probably 30 - 40 builds between 3.5 and 4.0-779 of TFN; including 4.0-752. I've known about this glitch forever, but didn't have the evidence I needed to post it.

Does using an older version of Dolphin solve your issue? If yes, which
versions of Dolphin used to work?

What are your PC specifications? (including, but not limited to: Operating
System, CPU and GPU)

Because I've known about this glitch so long, I actually have evidence of it running on three of my computers.

Core i5 3570K, GTX 760, Windows 7 x64
Core i5 760, Geforce GTX 280, Windows 7 x64
Core2duo @ 2.66GHz, Sapphire ATi Radeon 5850, Windows 7 32bit

Are you using the 32 or the 64 bit version of Dolphin?

Both.

Last but not least. A fifolog.

http://www.mediafire.com/download/utp1omfmai39dye/MarioGalaxy2Fog.7z

Actions #1

Updated by NeoBrainX about 10 years ago

autofire: Do not attach large pictures to GoogleCode, please. We have limited quota and cannot delete such pictures.

Actions #2

Updated by JMC4789 about 10 years ago

Yeah, I get the same glitch on Metroid Prime; I noticed it during the 10 years of Dolphin as well.

Actions #3

Updated by Autoran1 about 10 years ago

Didn't tested SMG2, but confirm metroid prime, renders perfectly on 3.5 but broken on 4.0, will investgate

Actions #4

Updated by JMC4789 about 10 years ago

I tested 4.0 with D3D9 again just to make sure, and it turns out I'm kinda stupid. D3D9 renders it accurately from what I can see. Technically a regression?! I don't think so, but whatever.

Actions #5

Updated by Autoran1 about 10 years ago

Well D3d9 always was unlike other backends, it prefer to act itself, sometimes better than others, but most of the time-not

Actions #6

Updated by JMC4789 about 10 years ago

  • Status changed from New to Accepted

Accepting for three reasons.

1: D3D9 and Software Renderer didn't/don't have the issue, meaning that there was a configuration within Dolphin that made it work.
2: I verified it on console, as well as messed with all the settings I could.
3: Metroid Prime series suffers from the same pattern and is confirmed by other users.

Actions #7

Updated by Autoran1 about 10 years ago

I also made some tests, the very first commits of GLSL branch (smth like from 3.0-770 to 3.0-920) caused this for metroid fog, also i tested it on another issue, Issue 5070, which probably has the same nature

Actions #8

Updated by JMC4789 almost 10 years ago

Galop1n's D3D Enhancements branch fixes this in the D3D11 backend.

Actions #9

Updated by JMC4789 over 9 years ago

  • Status changed from Accepted to Fixed

Fixed by 4.0-2626

Also fixes the same problem in Metroid Prime.

Actions

Also available in: Atom PDF