Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SpongeBob: ROTFD (NTSC-U) - Black splotches covering the screen in D3D HW renderers #1685

Closed
escape209 opened this issue Dec 3, 2016 · 8 comments

Comments

@escape209
Copy link
Contributor

escape209 commented Dec 3, 2016

PCSX2 version:
1.5.0-1676

PCSX2 options:
Defaults, except for MPEG Skip, but that's just because the intro FMVs are normally unskippable, and I can confirm that MPEG Skip has no effect on the issue.

Plugins used:
(Relevant/Non-default settings of GS/PAD/SPU2/CDVD/USB plugins)

Description of the issue:
D3D11 SW
gsdx_20161203170501

D3D11 HW
gsdx_20161203170450

GS Dump from D3D11 HW:
rotfd_gsdump.zip

How to reproduce the issue:

  1. Boot the game.
  2. Sit through the intro FMVs.
  3. Press Start when prompted.
  4. Voila.

Last known version to work:
Not sure.

PC specifications:
(For example: CPU: Intel Core 2 Duo E4600 GPU: Gigabyte GTX 750Ti OS: Windows 10 64 Bit)

@ssakash
Copy link
Member

ssakash commented Dec 3, 2016

What about OpenGL (hardware mode)?

@escape209
Copy link
Contributor Author

@ssakash Same as D3D11 software.

@ssakash
Copy link
Member

ssakash commented Dec 3, 2016

Could you bisect and find out the commit which fixed the issue in OpenGL (hardware mode)?

@escape209
Copy link
Contributor Author

Sure thing 👍

@escape209
Copy link
Contributor Author

escape209 commented Dec 3, 2016

@ssakash The earliest commit I tried, 7AAE0CE, is broken with OpenGL HW, but is fixed by enabling Hardware Depth. This obviously isn't the last commit where the issue is present, though.

@ssakash
Copy link
Member

ssakash commented Dec 3, 2016

Ah, I see. Then it's related to depth emulation which is a PITA to implement :P

@FlatOutPS2
Copy link
Contributor

We can probably close this as it can be resolved with OpenGL, and it isn't really a bug, but just the lack of hardware depth in D3D.

@lightningterror
Copy link
Contributor

Fixed on dx11.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants