Project

General

Profile

Actions

Emulator Issues #7033

closed

The Legend of Zelda: the Wind Waker - sun in the Dragon Roost Volcano

Added by tglcraig over 10 years ago.

Status:
Duplicate
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:

Description

Game Name?

The Legend of Zelda: the Wind Waker

Game ID?

GZLE01

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

I went into the Dragon Roost Volcano and there was a sun in the bottom of the room.

What did you expect to happen instead?

For there to not be a sun as the location is inside of a cave.

What steps will reproduce the problem?

  1. Play the game normally and get through the dungeon of Dragon Roost Island up to the part where one would acquire the Grappling Hook; unfortunately, I cannot think of a better way to describe the reference location.
  2. Go where the player is supposed to go after acquiring the Grappling Hook until you go inside of a cave.
  3. Inside the cave, look down and there should be an obvious misplaced sun along with the glare effect associated with it.

If any of these locations are not clear to anyone, I can provide more screen shots showing what one needs to see to know they are in the right spot and going the right way.

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?

Dolphin 4.0-879 x64

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

Not sure. I've never played Wind Waker up to this point in the game before on the emulator. I've checked the archive of issues and there appears to be nothing of this issue.

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

OS: Windows 8.1 x64
CPU: Intel Core i5-3330 @ 3.00GHz
GPU Intel HD Graphics
RAM: 8 GiB

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

64-bit

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

A screenshot of what I see: http://prntscr.com/2svvc2


Related issues 1 (0 open1 closed)

Is duplicate of Emulator - Emulator Issues #7963: The Lens Flare in Wind Waker is glitchy in dualcore (CPUTiming)Duplicate

Actions
Actions #1

Updated by JMC4789 over 10 years ago

Are you using D3D or OpenGL?

Actions #2

Updated by MayImilae over 10 years ago

  • Status changed from New to Questionable

What are your settings? Using savestates?

Actions #4

Updated by tglcraig over 10 years ago

I use the recommended settings for playing The Wind Waker suggested by the Wiki. Everything that does not fall under that, I use the tooltip recommendation.

I use the D3D graphics. I did not use any savestates.

This issue also appears to apply to other inside areas and occurs at random; although, I also may not be seeing the sun. When the sun first appeared, it stayed. I have recently gotten to the Forbidden Woods, and the problem occurred again.

Unrelated: I SEVERELY dislike having even part of my e-mail show. How can I apply a nickname?

Actions #5

Updated by JMC4789 over 10 years ago

Use OpenGL and submit another screenshot please.

D3D has a similar error in Twilight Princess, so I'd like to see if this is the same thing as in Twilight Princess. If it is it'll be easier to track down and fix.

Thank you for your cooperation, and I wish I knew more about the Google Code account settings to help you out with that issue.

Actions #6

Updated by MayImilae over 10 years ago

Does it happen in OpenGL?

Also, do you have a dedicated video card, or are you only running the "GPU Intel HD Graphics"? And can you specify which Intel HD graphics you have? Use GPU-Z to find out.

As for the email thing, sorry dude, only project members get that. Just how googlecode is.

Actions #7

Updated by tglcraig over 10 years ago

I am at the Forbidden Woods now and cannot return efficiently to the volcano. The Forbidden Woods has issues with this as well.

With D3D: http://prntscr.com/2t7aoo
With OGL: For whatever reason, Dolphin suddenly won't work with OpenGL. It happened after I ran GPU-Z. I'll try again tomorrow after I've shut down my computer and such.

I do not understand what a "dedicated card" is.
GPU-Z provides this information: http://prntscr.com/2t7bjh

Actions #8

Updated by JMC4789 over 10 years ago

I went back there on my computer and was unable to reproduce. It appears your GPU drivers are at fault.

Actions #9

Updated by MayImilae over 10 years ago

  • Status changed from Questionable to Invalid

Seems like an onboard graphics issue. Dolphin latest dev versions requires very modern tech and drivers to work properly, and Intel HD Graphics just doesn't have the support needed for it.

Actions #10

Updated by tueidj over 10 years ago

FYI this issue also occurs in Super Mario Sunshine. The sun rendering/lens flare effect is triggered by the game checking the Z buffer values of the screen area where the sun is located, if the Z values are "max" (0xFFFFFF) there has been nothing rendered on top of the sun and the lens flare is drawn. If EFB to cpu access is disabled, the Z values are faked to be 0 so the effect is always off. From this issue and #5999 it sounds like Z buffer EFB access with D3D11 is broken.

Actions #11

Updated by parlane over 10 years ago

  • Status changed from Invalid to Questionable
Actions #12

Updated by tglcraig over 10 years ago

Recently updated the graphics card.

With D3D: http://prntscr.com/2th2gw
With OGL: http://prntscr.com/2th0s9

So OpenGL does fix the issue.

Actions #13

Updated by tglcraig over 10 years ago

Updated to Dolphin 4.0-926.

Issue still persists with D3D.

Silly me, I forgot to get the new specs of the graphics card.
http://prntscr.com/2th5n7

Actions #14

Updated by MayImilae over 10 years ago

...How is that "new specs"? It's the same graphics hardware you posted previous.

Actions #15

Updated by NeoBrainX over 10 years ago

Just for reference, the depth read shaders in D3D11 probably suffer from overflow issue similar to the ones addressed in tev_fixes_new.

Would probably be worth trying to change depth_matrix_program in D3D/PixelShaderCache.cpp to use
"int4 EncodedDepth = ((int4(round(texcol.r * 16777215.0))&16777215) >> int4(16,8,0,0))) & int4(255,255,255,15);\n"
"texcol = float4(EncodedDepth) / float4(255.0f,255.0f,255.0f,15.0f);\n"
"ocol0 = float4(dot(texcol,cColMatrix[0]),dot(texcol,cColMatrix[1]),dot(texcol,cColMatrix[2]),dot(texcol,cColMatrix[3])) + cColMatrix[4];\n
instead of the analogous three lines that it uses currently. That's not really tested nor can I provide a build currently, though :p

Actions #16

Updated by NeoBrainX over 10 years ago

  • Status changed from Questionable to Accepted

Thanks to tueidj for the comment btw.

Actions #17

Updated by tueidj over 10 years ago

Where do those two "15" constants come from?

Actions #18

Updated by tglcraig over 10 years ago

I thought that updating the driver might change it. If it didn't, it didn't. I just put it there in case anything changed.

Actions #19

Updated by NeoBrainX over 10 years ago

@ tueidj: These are for the Z4 copy format. They copy out the least significant 4 bits of depth.

Actions #20

Updated by greatbrian2 over 10 years ago

Twilight Princess and Skyward Sword also suffer from this depth buffering issue.

Actions #21

Updated by darknessknightes over 10 years ago

Phantasy Star Online (OGL):
http://imgur.com/iG22R3V

Zelda TP (D3D11):
http://imgur.com/lAuQmDf

Salu2 - Darkness Knight

Actions #22

Updated by Autoran1 over 10 years ago

  • Status changed from Accepted to Duplicate
Actions #23

Updated by JMC4789 almost 10 years ago

This was a separate issue all along, but very stupidly so. Took me a very long time to figure it out.

Actions #24

Updated by AlxNissen almost 10 years ago

Is there any fix for this? I am getting it too on both D3D11 and Open GL

Actions #25

Updated by JMC4789 almost 10 years ago

Use single core.

Actions #26

Updated by AlxNissen almost 10 years ago

Could you explain that for me? What do you mean?

Actions #27

Updated by JMC4789 almost 10 years ago

This is caused by some kind of desync in communication between the CPU and the GPU; so if you want to fix the issue, you can set Dolphin to single core in options/config.

I'm just going off my experience with this issue; not sure if there are multiple causes or other dumb settings that can trigger it.

Actions #28

Updated by AlxNissen almost 10 years ago

You mean disable the option: "Enable Dual Core (speedup)"? I did that, and the flare is still there

Actions #29

Updated by AlxNissen almost 10 years ago

For some reason dying in the game fixed it..

Actions

Also available in: Atom PDF