Vulkan renderer is broken

[Whatnoww]

It'll only display these memory errors before crashing. Looks like some parameters might have been srt wrong in a previous build or the driver update really broke some stuff.

This is on the SD835 on the OnePlus 5 and dolphin build 5.0-8574


   
   
   

[JonnyH]

What games is this with?

What driver are you using?

With my oneplus 5 I've not see these issues (Maybe there's been a new update since last week? That reports "OpenGL ES 3.2 V@269.0 (GIT@4bff8b9, Ida6448821d) (Date:06/14/18)" in GL_VERSION, and "Driver Version: 18.1023.2233" from vulkan)

But I know the V@313 driver (as in the sd820 Google Pixel android P update) has completely broken vulkan rendering - apparently due to more limited number of variables you can use to communicate between the vertex/fragment shaders, which breaks /everything/. It also seemed to break the version string for vulkan - hence me quoting the GL version (on the assumption they're shipped and updated in lockstep anyway)

So I haven't seen this myself, but not really optimistic about future driver updates at all.

[Nintonito]

What games is this with?

What driver are you using?

With my oneplus 5 I've not see these issues (Maybe there's been a new update since last week? That reports "OpenGL ES 3.2 V@269.0 (GIT@4bff8b9, Ida6448821d) (Date:06/14/18)" in GL_VERSION, and "Driver Version: 18.1023.2233" from vulkan)

But I know the V@313 driver (as in the sd820 Google Pixel android P update) has completely broken vulkan rendering - apparently due to more limited number of variables you can use to communicate between the vertex/fragment shaders, which breaks /everything/. It also seemed to break the version string for vulkan - hence me quoting the GL version (on the assumption they're shipped and updated in lockstep anyway)

So I haven't seen this myself, but not really optimistic about future driver updates at all.

I’m always impressed by how dolphin manages to expose these changes that sound basic and ridiculous, yet somehow nobody else notices. Hopefully google doesn’t waste that graphicsfuzz acquisition, those guys were definitely into something (their webGL actually fails a couple of parts on my Pixel).

[JonnyH]

I’m always impressed by how dolphin manages to expose these changes that sound basic and ridiculous, yet somehow nobody else notices.  Hopefully google doesn’t waste that graphicsfuzz acquisition,  those guys were definitely into something (their webGL actually fails a couple of parts on my Pixel).

Really, most apps *avoid* trying to use the latest and greatest APIs and features - as it cuts out most of the market. 

Dolphin really was one of the first apps using all this stuff on mobile - which is kinda why I ended up here - trying to find an app that actually used vulkan on android (outside of 'toy' renderers)

And most OEMs just don't care - they do the bare minimum that google demands (their dEQP testing is a step in the right direction - but tends to test each features in isolation, not the combinations actually seen in games, or dolphin . Once they've got your $$$ and sold their phone, they're already thinking about the next-next generation refresh. And people have shown they'll pay for their $900 phones without thinking of this stuff before, so why should they invest time and money in fixing it?

[Whatnoww]

What games is this with?

What driver are you using?

With my oneplus 5 I've not see these issues (Maybe there's been a new update since last week? That reports "OpenGL ES 3.2 V@269.0 (GIT@4bff8b9, Ida6448821d) (Date:06/14/18)" in GL_VERSION, and "Driver Version: 18.1023.2233" from vulkan)

But I know the V@313 driver (as in the sd820 Google Pixel android P update) has completely broken vulkan rendering - apparently due to more limited number of variables you can use to communicate between the vertex/fragment shaders, which breaks /everything/. It also seemed to break the version string for vulkan - hence me quoting the GL version (on the assumption they're shipped and updated in lockstep anyway)

So I haven't seen this myself, but not really optimistic about future driver updates at all.

I've got that exact same driver version. But the solution is what the other user said.

I re-registered on this site to respond to this topic. You have to disable GPU Texture Decoding under "Hacks" settings to avoid crashing on Vulkan. BTW, I also have a OnePlus 5.

Thanks for your reply!