Original Post — Direct link
Recently, I keep having this weird issue. I get the error, seemingly randomly, when I try to run the game with Vulkan that there was "no compatible driver/hardware found", or something among those lines.

What I do is that I simply download AMD's driver update software and let it reinstall everything for my CPU, and after this I can play the game with Vulkan... for a while.

Sometimes it takes a couple of day, but inevitabely, the game will simply refuse to start with Vulkan and give me the aftorementioned error.
If I repeat the process of AMD driver reinstallation, Siege works flawlessly for as long as I'm playing it, but eventually, I'll have to repeat the process.
Also, this happens with Ghost Recon: Breakpoint, but that game runs awfully with Vulkan so I don't really care, but you should

To clarify, I have Nvidia GPU (RTX 3070) and keep those drivers up-to date. I only need to download and (re)install the CPU (Ryzen 7 5800H) related drivers to fix this issue.
It is also worth mentioning that I was able to play other Vulkan titles like "Detroit: Become Human" (which runs exclusively on Vulkan) on Steam while Siege was unable to find compatible driver/hardware.
over 3 years ago - Ubi-Orion - Direct link
Originally Posted by geostigma_
Recently, I keep having this weird issue. I get the error, seemingly randomly, when I try to run the game with Vulkan that there was "no compatible driver/hardware found", or something among those lines.

What I do is that I simply download AMD's driver update software and let it reinstall everything for my CPU, and after this I can play the game with Vulkan... for a while.

Sometimes it takes a couple of day, but inevitabely, the game will simply refuse to start with Vulkan and give me the aftorementioned error.
If I repeat the process of AMD driver reinstallation, Siege works flawlessly for as long as I'm playing it, but eventually, I'll have to repeat the process.
Also, this happens with Ghost Recon: Breakpoint, but that game runs awfully with Vulkan so I don't really care, but you should

To clarify, I have Nvidia GPU (RTX 3070) and keep those drivers up-to date. I only need to download and (re)install the CPU (Ryzen 7 5800H) related drivers to fix this issue.
It is also worth mentioning that I was able to play other Vulkan titles like "Detroit: Become Human" (which runs exclusively on Vulkan) on Steam while Siege was unable to find compatible driver/hardware.
Originally Posted by geostigma_
No reply, huh? Well, I kind of get you since I don't know what to say either...

Perhaps you could help me with some additional issues?
  1. Shift + F2 isn't working either (it's not the "F" keys since Alt+F4 works just fine)
  2. When Siege launches, ESC isn't working. I have to alt+tab out of the game and go back to it to make temporarily fix it. Further alt+tabbing sometimes mekes it come back.
  3. Nvidia Shadowplay overlay is not working now either. I can no longer record my gameplay and check those suspicious kill cams.
Hey there.

Sorry for the delay in getting back to you on this.

The first thing I would suggest is to attempt each step suggested here.

If after doing so you're still experiencing issues I'd then recommend opening a support case. You can reach us either through the support website by opening a live chat session or alternatively through our social media accounts on Facebook and Twitter and they will be able to create a support case for you.

After you've opened the case if I can also ask you to attach two system reports to the case that will assist us in identifying any potential cause. The reports we need from you are:

MSInfo
DxDiag

Thanks.
over 3 years ago - Ubi-Thrupney - Direct link
Thanks for confirming that for us, geostigma_ - we really appreciate the update!

As Ubi-Orion's explained, the next step is to troubleshoot further with the help of some system files - a DxDiag.txt and an MsInfo.txt. The two articles I've linked there will show you how to find each of them.

Once you have those files, you can reach out to us via our support website, or via Facebook PM or Twitter DM, to send them across, and we'll be able to use them to investigate the issue.

Let me know if you have any trouble contacting those teams
over 3 years ago - Ubi-Karl - Direct link
Originally Posted by geostigma_
Unfortunately, I've never had this sort of technical issue fixed this way so I'll just wait for a couple of updates and play something else in the meantime.

Not that I'm saying that they're not going to do anything with it, just that whenever it comes to submitting dxdiag or following some premade technical troubleshooters, it only turns out to be a waste of time. Thanks anyway.
Hey geostigma_, thanks for the update and apologies about the delayed response.

Should you ever change your mind and if you are happy to look at the resolution steps, please send us the requested documents and we will be able to proceed.

Until then, should you have any further queries, feel free to get in touch at any time!