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

Star Ocean First Departure longstanding graphical issues still persistent in vanilla PPSSPP yet nonexistent in Libretro port #8244

Closed
Warriors-Blade opened this issue Nov 28, 2015 · 7 comments

Comments

@Warriors-Blade
Copy link

I just tested Star Ocean First Departure in the Libretro port of PPSSPP which is a little old since its still on 1.0.1 and surprisingly in the libretro port ran via Retroarch Star Oceans FDs graphical issues regarding invisible sprites and choppy screen movement are nonexistent.

Those issues are still present in the latest vanilla build of PPSSPP in both OpenGL and Direct3D and I am posting this as I think it may be important info for any development for PPSSPP on intel chipsets.

Also the standard screen tearing in vanilla PPSSPP is nonexistent in Retroarch.

Tested on Windows 7 64
Intel chipset laptop

@unknownbrackets
Copy link
Collaborator

This is on an Intel video card with default settings? The game works fine on an NVIDIA 9800 GT.

Retroarch just runs PPSSPP, possibly with slightly changed settings. At most maybe they load OpenGL differently?

-[Unknown]

@unknownbrackets
Copy link
Collaborator

From discussion on IRC, it sounds like the GL context is created differently, glew is stubbed out, and the window is created differently. Maybe one of these is making the Intel driver make better decisions.

-[Unknown]

@Warriors-Blade
Copy link
Author

Yes this is on a Intel chipset laptop with default settings (really can't change anything honestly)

I thought it was important information and wanted to let you all know since I was pretty pleased seeing Star Ocean FD work as intended but it was not in vanilla sadly.

The Retroarch environment? seems to make emulators run better but I am not sure of the details.

@tilkinsc
Copy link
Contributor

tilkinsc commented Aug 3, 2017

Stencil test? #8171 may be the solution. Which is important to see if it is actually working. #7577 links back here because it is a dupe.

@hrydgard
Copy link
Owner

hrydgard commented Aug 7, 2017

Is this even still the case?

@unknownbrackets
Copy link
Collaborator

Even if it is, it might be resolved by Direct3D 11. I've never experienced this issue, though.

There are reports of issues with Intel cards:
http://report.ppsspp.org/game/ULUS10374_1.00
http://report.ppsspp.org/game/ULJM05290_1.01
http://report.ppsspp.org/game/ULES01154_1.00

However, they give it full marks in graphics.

-[Unknown]

@hrydgard
Copy link
Owner

hrydgard commented Aug 8, 2017

Alright. Doesn't seem worth investigating more since we indeed now have a range of backends to try in case of buggy drivers - pretty sure the bug isn't in our code, anyway.

@hrydgard hrydgard closed this as completed Aug 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants