sorry to post here, but I can't open a thread in the forum 'OpenGL and Vulkan',
so please move this post over there if possible.
I have a question related to Vulkan and the AMD RX 560 GPU.
A few month ago we ported our rendering engine to the Vulcan API.
Our game runs just fine on many GPU's including Intel and NVIDIA
and even on the AMD RX 460 GPU. We seem to pass a validation test,
and do not observe any validation errors at all.
However, when running our game on AMD RX 560 we get real driver
crashes, e.g. the driver itself seems to crash and we sometimes
even have to reboot our computer. This is on Windows 10 with the
latest AMD driver.
Keep in mind this is not isolated to a single developer machine,
we have customers reporting the same on various other hardware
configurations. E.g. only the AMD RX 560 gives a crash when running
We tried to pin point down the issue using various methods,
including adding full pipeline barriers and so on, but we can't
find out whats causing it.
Any idea on what we can do to find out what's causing the issue?
What is the general hardware difference between the AMD RX 460
and AMD RX 560 that could cause this? Is there any special debug
driver we might be able to try?
We even prepared a demo executable and tried to get help from
AMD developers, but nobody has responded so far.
Any help would be greatly appreciated as we are really at the
end with any ideas on what the cause might be.
I can of course provide more information and might even try to
provide a source sample.
Thank you dorisyan for your reply.
Please give me a little bit to prepare a working ( e.g. crashing ) demo for you. Stripping down everything with respect to code and assets will take some time.
Is there a private channel or email where I can post instructions and download links as we don't want to freely distribute our source code around?
I have now prepared a demo with source code that shows you the issue we encounter. The GPU we tried for this is a AMD RX 580.
The demo is a 64 Bit executable. The source code project is done with Visual Studio 2017 latest version.
Please let me know where I can send instruction on how to get the demo with some small explanations on what to do. I don't want to post the link to the demo online.
Thank you for reporting back. I would like to mention that it was a cross platform bug as well, e.g. this issue was present on Linux, Mac OS and Windows drivers. Our workaround for now is to not use triangle strips with 16 bit size and the primitive restart index.