[GZDoom 4.1.2] Vulkan Crashes "AMD 400/500 Series"
Moderator: GZDoom Developers
Forum rules
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.
- MasterBeavis
- Posts: 43
- Joined: Mon May 13, 2019 5:19 pm
- Preferred Pronouns: Ask Me
- Operating System Version (Optional): Windows 11
- Graphics Processor: ATI/AMD (Modern GZDoom)
Re: [GZDoom 4.1.2] Vulkan Crashes "AMD 400/500 Series"
im just glad you narrowed it down more lol
-
- Posts: 72
- Joined: Wed Jun 28, 2017 3:07 am
- Graphics Processor: ATI/AMD with Vulkan/Metal Support
Re: [GZDoom 4.1.2] Vulkan Crashes "AMD 400/500 Series"
You're the one who got me looking into Display settings, and you were right about it being something in post-processing. I just started trying settings until something broke, lol. You'd probably have gotten there. More than anything I'm glad I was able to corroborate the issue. Would have been bad if this got written off as just a problem with your hardware.MasterBeavis wrote:im just glad you narrowed it down more lol
Re: [GZDoom 4.1.2] Vulkan Crashes "AMD 400/500 Series"
Vulkan is disabled on the 32 bit builds, so that's why it doesn't crash. This doesn't really mean anything.
- MasterBeavis
- Posts: 43
- Joined: Mon May 13, 2019 5:19 pm
- Preferred Pronouns: Ask Me
- Operating System Version (Optional): Windows 11
- Graphics Processor: ATI/AMD (Modern GZDoom)
Re: [GZDoom 4.1.2] Vulkan Crashes "AMD 400/500 Series"
Yea we already figured that out lol its Bloom in Post Processing with Vulkan thats causing itRachael wrote:Vulkan is disabled on the 32 bit builds, so that's why it doesn't crash. This doesn't really mean anything.
Re: [GZDoom 4.1.2] Vulkan Crashes "AMD 400/500 Series"
Yes, thanks once again in confirming this bug report. And thanks for narrowing it down the bloom pass and seemingly related to load/save code (save game thumbnail, most likely). It will help figuring out what could be causing it.Dwailing wrote:More than anything I'm glad I was able to corroborate the issue
Re: [GZDoom 4.1.2] Vulkan Crashes "AMD 400/500 Series"
Okay, I pushed a commit that I think may fix the issue reported here. Please test again with the next nightly build.
- MasterBeavis
- Posts: 43
- Joined: Mon May 13, 2019 5:19 pm
- Preferred Pronouns: Ask Me
- Operating System Version (Optional): Windows 11
- Graphics Processor: ATI/AMD (Modern GZDoom)
Re: [GZDoom 4.1.2] Vulkan Crashes "AMD 400/500 Series"
Oh well. I don't have a clue what is causing the crash then.
Re: [GZDoom 4.1.2] Vulkan Crashes "AMD 400/500 Series"
With this fix I managed to reproduce the crash on Vega occasionally. It's somewhere inside vkCmdBeginRenderPass function.
Spoiler: CallstackIt doesn't happen with validation layers enabled though.
Re: [GZDoom 4.1.2] Vulkan Crashes "AMD 400/500 Series"
I pushed another commit that may be the source to that BeginRenderPass crash.
- MasterBeavis
- Posts: 43
- Joined: Mon May 13, 2019 5:19 pm
- Preferred Pronouns: Ask Me
- Operating System Version (Optional): Windows 11
- Graphics Processor: ATI/AMD (Modern GZDoom)
Re: [GZDoom 4.1.2] Vulkan Crashes "AMD 400/500 Series"
one build failed
https://ci.appveyor.com/project/coelcke ... 14f0aq8aic
the issue is fixed after trying the studio 2015 one
https://ci.appveyor.com/project/coelcke ... 120fug18ba
https://ci.appveyor.com/project/coelcke ... 14f0aq8aic
the issue is fixed after trying the studio 2015 one
https://ci.appveyor.com/project/coelcke ... 120fug18ba
Re: [GZDoom 4.1.2] Vulkan Crashes "AMD 400/500 Series"
Fixed for me as well.