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

Direct3D 9 does not display images of 3D games #11477

Closed
DmdHoH000 opened this issue Oct 17, 2018 · 4 comments
Closed

Direct3D 9 does not display images of 3D games #11477

DmdHoH000 opened this issue Oct 17, 2018 · 4 comments
Labels
D3D9 Direct3D 9
Milestone

Comments

@DmdHoH000
Copy link

DmdHoH000 commented Oct 17, 2018

What happens?

When the renderer is set to Direct3D 9 no 3D games display images

Some games that i have tested

Tekken Dark Resurrection

ulus10139_00001

MegaMan Maverick Hunter X

ulus10068_00000

K-On! Houkago Live!!

uljm05709_00000

Dissidia 012

ules01505_00000

Kingdom Hearts Birth By Sleep Final Mix

uljm05775_00000

Project Diva 2nd

uljm05681_00000

Fate Unlimited Codes

npuh10009_00000

What should happen?

The games should have been displaying images normally but that is not what happening

Although that 2d games display fine on Direct3D 9

Here s some pics

ulus10062_00000

ulus10584_00000

What hardware, operating system, and PPSSPP version? On desktop, GPU matters for graphical issues.

My specs
OS: Windows 7 Ultimate Service Pack 1
Processor: Pentium(R) Dual-Core E5400 2.70 Ghz
RAM memory: 4,00 GB (3,87 usable)
GPU: Intel(R) GMA X4500
Last version that work: PPSSPP-v1.6.3-472-g3f34c7a21
Version that broke: PPSSPP-v1.6.3-478-gacfd68864

Sorry if my english is not good because im from Brazil
I have to use Google Translate

@AkiraJkr
Copy link

That's...pretty weird, considering I am able to emulate just fine on my GMA 450...

Kingdom Hearts Birth by Sleep
image

Dissidia 012
image

Do you mind going to Discord? That way, further can be discussed much faster, and maybe we could find a fix for your issue. https://discord.gg/5NJB6dD

@unknownbrackets
Copy link
Collaborator

It sounds like some testing had narrowed this down to a certain commit range, right? I remember seeing a note that it was suspected related to #11393 - can you confirm?

If so, maybe we disable that on Direct3D 9 (theory: only people on older hardware more likely to bug out with that change use Direct3D 9)?

-[Unknown]

@AkiraJkr
Copy link

That could be a good solution since older hardware can only use D3D9- But what if there's people with less older hardware having that issue in this or other backends? Well, we may never know, since there's not many people to test... sigh

I can confirm for him that his issue is caused by #11393. It seems to be on the version that this commit was implemented that it broke, but what's more interesting...it completely broke for him, while for me, it was barely, very specific areas and camera angles.(theory: The older the hardware, the more broken it gets?) Really weird. So yes, Try disabling it for D3D9.

@hrydgard hrydgard added this to the v1.7.0 milestone Oct 19, 2018
@hrydgard hrydgard added the D3D9 Direct3D 9 label Oct 19, 2018
@hrydgard
Copy link
Owner

I'm disabling it for Intel GPUs on D3D9 - I don't think we have any issues with this on NV or AMD.

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

No branches or pull requests

4 participants