Project

General

Profile

Actions
Copy link

Emulator Issues #6465

closed

Fortune Street Cloud/Water flickering regression OpenGL

Added by JMC4789 over 11 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
degasus
Category:
GFX
% Done:

0%

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

Description

Game Name: Fortune Street, ST7E01

Basically,r737df2a68cd5c5cdfa1e73cede0dbf85bde01abc or Dolphin 3.5-1595 broke stuff. First load shows it not flickering in Dolphin 3.5-1594. Second time through I show Dolphin 3.5-1595 and how bad the flickering is.

http://www.youtube.com/watch?v=GvOVe1VYWIc

I tested a bunch of builds to confirm 1595 as the culprit.

3.5-1301 - Works
3.5-1313 - Works
3.5-1505 - Works
3.5-1535 - Works
3.5-1551 - Works
3.5-1561 - Works
3.5-1591 - Works
3.5-1593 - Works
3.5-1594 - Works
3.5-1595 - Broken
3.5-1596 - Broken
3.5-1597 - Broken
3.5-1648 - Broken
3.5-1655 - Broken
3.5-1727 - Broken

This issue doesn't show up on a fifo-log because that geometry does not draw in a fifo-log.

Actions
Copy link
 #1

Updated by JMC4789 over 11 years ago

  • Issue type set to Bug
  • Category set to gfx
  • Regression set to Yes
Actions
Copy link
 #2

Updated by MayImilae over 11 years ago

Confirmed. That video is the worst possible place to demonstrate it (looks like an FMV), but yea, it's there. Appears to be a bloom issue to my non-coder artist eyes.

JMC -really- wants to make this as accepted so I'll let him do it. :P

Actions
Copy link
 #3

Updated by NeoBrainX over 11 years ago

  • Milestone set to Current
Actions
Copy link
 #4

Updated by delroth over 11 years ago

  • Status changed from New to Accepted
  • Priority set to High
Actions
Copy link
 #5

Updated by degasus over 11 years ago

Actions
Copy link
 #6

Updated by JMC4789 over 11 years ago

wow, I didn't realize you could just get it like. I figured all the backgrounds would just get lost.

Actions
Copy link
 #7

Updated by degasus about 11 years ago

  • Status changed from Accepted to Fixed

This issue was closed by revision 0255e1391244.

Actions
Copy link
 #8

Updated by degasus about 11 years ago

This issue was closed by revision 0255e1391244.

Actions
Copy link
 #9

Updated by JMC4789 over 10 years ago

  • Status changed from Fixed to Accepted

This is happening again >:(

Actions
Copy link
 #10

Updated by mathon over 10 years ago

Still happens on 4.0-1603. Any updates?

Actions
Copy link
 #11

Updated by JMC4789 about 10 years ago

Can we please have this looked at again? It was fixed before and broken again.

Actions
Copy link
 #12

Updated by Autoran1 about 10 years ago

  • Status changed from Accepted to Fixed

Whatever it was it's not an issue now, on recent master build OGL renders it perfectly
Tested on r-3488

Actions
Copy link
 #13

Updated by JMC4789 about 10 years ago

  • Status changed from Fixed to Accepted

This is not fixed.

Actions
Copy link
 #14

Updated by Autoran1 about 10 years ago

Maybe we are on the different systems, cause i've tested on offician non-modiffied build and it still works perfect

Actions
Copy link
 #15

Updated by JMC4789 about 10 years ago

NVIDIA vs Other stuff? Is this a nvidia bug?

Actions
Copy link
 #16

Updated by Autoran1 about 10 years ago

I've got nvidia, so i guess it's other stuff

Actions
Copy link
 #17

Updated by JMC4789 about 10 years ago

It doesn't happen on my Radeon. Can you give me more details about your drivers?

Actions
Copy link
 #18

Updated by Autoran1 about 10 years ago

GF 780, Driver 340.52

Actions
Copy link
 #19

Updated by JMC4789 about 10 years ago

Are you testing the game or the fifolog. It's very, very obviously failing at 2x IR.

Actions
Copy link
 #20

Updated by JMC4789 about 10 years ago

EFB2RAM works fine on my NVIDIA in OGL. EFB2Texture glitches up. Radeon works fine on both settings. D3D works fine on EFB2Tex on NVIDIA and Radeon.

Actions
Copy link
 #21

Updated by JMC4789 about 10 years ago

  • Milestone deleted (Current)
  • Priority changed from High to Normal

I'm guessing this is yet another NVIDIA driver bug. Moving off current because EFB2RAM works fine.

Actions
Copy link
 #22

Updated by degasus about 10 years ago

@JMC4789: So it's fine at 1xIR ?

Actions
Copy link
 #23

Updated by JMC4789 about 10 years ago

no. It's broken at 1x, 2x, 3x IR. But at 4x IR the bloom is so high resolution it's hard to notice.

Actions
Copy link
 #24

Updated by idan345 about 10 years ago

There has been an update to the nvidia drivers today.
Version number is at 344.48 , stable version.
Seeing as it has been tested with 340.52, maybe its worth a shot to try it with the newer drivers.

Actions
Copy link
 #25

Updated by JMC4789 about 10 years ago

  • Status changed from Accepted to Fixed

I can't reproduce it again.

Actions
Copy link

Also available in: Atom PDF