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

[Vulkan] "Failed creating graphics pipeline!" #10065

Closed
Lyudmila17 opened this Issue Nov 6, 2017 · 22 comments

Comments

Projects
None yet
4 participants
@Lyudmila17

Lyudmila17 commented Nov 6, 2017

It crashes when I start the game.

Revision: gea2fc5521
ppsspplog.txt

@hrydgard

This comment has been minimized.

Owner

hrydgard commented Nov 6, 2017

Interesting. AMD, nVidia or Intel? Fresh drivers?

@Lyudmila17

This comment has been minimized.

Lyudmila17 commented Nov 6, 2017

Dammit, now for some reason it starts. Weird. Should I close?

@hrydgard

This comment has been minimized.

Owner

hrydgard commented Nov 6, 2017

Try some more and see if you can get it to happen. If you can't, yeah, go ahead and close, but sounds strange.

@Lyudmila17

This comment has been minimized.

Lyudmila17 commented Nov 6, 2017

It crashes randomly (this time loading a savestate of CoD). Another log:
ppsspplog.txt
Edit: AMD with latest drivers.

@Lyudmila17 Lyudmila17 changed the title from [Vulkan] [Burnout Dominator] "Failed creating graphics pipeline!" to [Vulkan] "Failed creating graphics pipeline!" Nov 6, 2017

@hrydgard

This comment has been minimized.

Owner

hrydgard commented Nov 6, 2017

I'm gonna have to improve logging for that error for the log dumps to be useful...

hrydgard added a commit that referenced this issue Nov 6, 2017

@hrydgard

This comment has been minimized.

Owner

hrydgard commented Nov 6, 2017

With that we might get more clues...

@hrydgard

This comment has been minimized.

Owner

hrydgard commented Nov 7, 2017

@AnKris Can you try again with the latest builds?

@Lyudmila17

This comment has been minimized.

Lyudmila17 commented Nov 7, 2017

Revision g7922a2ab5

ppsspplog.txt

@hrydgard hrydgard added the Vulkan label Nov 8, 2017

@hrydgard

This comment has been minimized.

Owner

hrydgard commented Nov 8, 2017

OK, so now we're getting

55:17:571 idle0 E[G3D]: Vulkan\PipelineManagerVulkan.cpp Failed creating graphics pipeline! result='VK_ERROR_INITIALIZATION_FAILED'

Very odd. Wonder if we might be accidentally using some feature that need to be explicitly enabled, without enabling it... but the validation layers should have caught that.

This could also be a case of we using a buggy glslang version or something, producting SPIR-V that AMD doesn't like - I'm going to try upgrading that soon.

@hrydgard

This comment has been minimized.

Owner

hrydgard commented Nov 10, 2017

@AnKris feel like trying out the latest build from the buildbot?

@Lyudmila17

This comment has been minimized.

Lyudmila17 commented Nov 10, 2017

Same issue.
ppsspplog.txt

@hrydgard

This comment has been minimized.

Owner

hrydgard commented Nov 10, 2017

Darn. Really no clue then... So it's very random when it happens? Does it seem related to the use of save states somehow, like, it doesn't happen if you don't use savestates, or something like that?

@Lyudmila17

This comment has been minimized.

Lyudmila17 commented Nov 10, 2017

It's not random this time, it happens instantly when I start specifically Burnout Dominator.

@hrydgard

This comment has been minimized.

Owner

hrydgard commented Nov 10, 2017

Interesting, looking at your log it happens when the first shader with dual source blending appears. So yet another vendor is affected. I'm going to try blacklisting AMD from using dual source blending in Vulkan.

hrydgard added a commit that referenced this issue Nov 10, 2017

@hrydgard

This comment has been minimized.

Owner

hrydgard commented Nov 10, 2017

There's a new build up, try that.

@hrydgard

This comment has been minimized.

Owner

hrydgard commented Nov 10, 2017

https://community.amd.com/thread/210605 so this appears to be an issue in drivers from early this year.

Can you check again that you really have updated drivers? And before you try to upgrade your driver, can you check what driver version is reported in PPSSPP's Settings/Tools/System Information? Might be able to make this conditional on driver version.

@Lyudmila17

This comment has been minimized.

Lyudmila17 commented Nov 10, 2017

It seems to work now.

image

image

It's up to date.

@LunaMoo

This comment has been minimized.

Collaborator

LunaMoo commented Nov 10, 2017

Just wondering, does disabling this feature(or it simply not working) could lead to inverted vertices(kind of looking like depth issues) or stuff like that? Because that's how I'm experiencing Vulkan in most more complex games and while I thought it's just something unfinished yet, it might as well be related to dual source blending as well:|.

Tested this game, and it works and looks same pre and post disabling dual source blending for AMD.
burnout vulkan
Similar glitches shows up for example in Metal Gear Solid PW, but does not in simple games like Monster Hunter.

Might just be a different driver issue;p, 16.12.2 doesn't seem anywhere close to latest one through, I'm on 17.11.1 right now and those versions are going by date I belive:].

@hrydgard

This comment has been minimized.

Owner

hrydgard commented Nov 10, 2017

No, the only thing that happens is that a few rare things don't show up like glows around transparent objects in Wipeout.

That's more likely to be this, which makes me sad: https://community.amd.com/thread/221378

I thought Vulkan would mean a new better era of drivers for AMD, but no...

That one can probably be worked around with a bit of projection matrix magic though.

@hrydgard

This comment has been minimized.

Owner

hrydgard commented Nov 10, 2017

@LunaMoo feel like reporting that as a separate issue btw? I'm closing this one since this particular error has been worked around.

@hrydgard hrydgard closed this Nov 10, 2017

@unknownbrackets

This comment has been minimized.

Collaborator

unknownbrackets commented Nov 11, 2017

Not that I'm arguing with the workaround, it's great (if unfortunate) - but not having dual source also causes issues like #7356 in some games, so it's not always a glow missing or etc.

-[Unknown]

@hrydgard

This comment has been minimized.

Owner

hrydgard commented Nov 11, 2017

Oh yeah, fair enough. Should really get around to implementing a dual pass workaround at some point...

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