[Fixed] [GZDoom 4.1.2] Vulkan Crashes "AMD 400/500 Series"

[MasterBeavis]

where do i grab the nightly? if the one i got on appvoyer is correct then no its didnt fix it

[dpJudas]

It will be the next one from appvoyer - it is still building according to github's yellow circle for that commit. So try with that one or wait for the next nightly that should show up whenever its night according to Rachael's build servers.

[MasterBeavis]

the best test cases are probably the Radeon 400/500 series since they are both Polaris

Edit. Nope still crashes with the latest commit

[Rachael]

https://mega.nz/#!pFEkwKwJ!XRgCH4yoxe5l ... Zx1jgjLtoE

Can you please try this build? It has debug symbols included. Please post the crash log you get from it.

[MasterBeavis]

Heres a Crash From Pirate Doom.

[Rachael]

This crashes in the AMD driver, with no stack trace. Is it possible for you to do another one, perhaps with another mod?

[MasterBeavis]

yea hold on


Heres one playing Vanilla doom with a diff soundtrack

[Rachael]

I have no idea what's going on here. It's the same thing - crash in the driver, no stack trace. I'm going to compile something different for you.

[MasterBeavis]

Heres a crash from just playing doom 2 Vanilla no mods at all

[dpJudas]

Guys, at the risk of sounding like a broken record, I'll repeat what I said:

I need confirmation from a different AMD GPU user that this crash is not machine specific. I need that confirmation because the vulkan driver on MasterBeavis's computer already misreports its own device name. That a driver cannot give the name of its own card is a strong indicator that there may be a local problem not directly caused by GZDoom.

[Rachael]

And on that note - MasterBeavis - I recommend completely uninstalling and removing your AMD driver, and installing the latest version from scratch.

[MasterBeavis]

like i said before ive done that already used AMD Remover and DDU nothing has changed. wouldnt this effect other programs that use vulkan if it was a big issue?

[dpJudas]

I am not ruling out that it could be a bug in GZDoom. And I have no direct evidence the driver has more bugs than the most basic "what's your name?" "it's Unknown AMD GPU!"

But consider this: GZDoom is a small project with only a few unpaid developers. If it really is a local problem we can be sending endless copies of test builds and shit and still possibly not get anywhere close to a solution. Simply put, this is too expensive for our resources. That is why I need other AMD users to confirm the crash.

_mental_ already concluded the crash happens when GZDoom attemps to bind a pipeline vulkan object, inside the AMD driver. Why does it crash in it? It could be GZDoom giving it bad data, but it could also be the driver just shitting itself because it seemingly isn't fully aware what card it's interfacing with.

[Graf Zahl]

@MasterBeavis:

It may be a good idea to install the Vulkan SDK, then run GZDoom with vk_debug set to 1 and see if the validation layer outputs something useful.

[MasterBeavis]

uh how do i run gzdoom with that?