AMD has confirmed the rollout of an updated chipset driver that will allegedly solve the problems Destiny 2 has faced in regards to launching on third-generation Ryzen builds.
The company issued a call on social media platform Reddit to collect testers for the new rollout. The call was posted by the company's technical marketing head for processors Robert Hallock, who apologised the fix had been so long in the making from AMD's side.
I know you're pissed off, and I totally get it, and I want to make it right with you. I want to earn your trust back," he said in the Reddit post.
The short and narrow of this situation is that Destiny 2 does not run on AMD's latest CPU. Considering it's a popular choice for PC gamers, it basically cut off the supply of Bungie's ongoing title to some of its most hardcore Guardians.
The problem arose a few weeks ago after the Ryzen 3000 early upgrades. Now, the company believes they have solved the issue, and are rolling it out to the chosen beta testers.
"AMD has identified the root cause and implemented a BIOS fix for an issue impacting the ability to run certain Linux distributions and Destiny 2 on Ryzen 3000 processors. We have distributed an updated BIOS to our motherboard partners, and we expect consumers to have access to the new BIOS over the coming days," the company said in a release.
Hallock also issued another apology alongside confirmation the patch had been solved and admitted the company only found out about the Destiny 2 problems "after launch."
"Plain and simple: I'm sorry. It is not a title that is in our standard test suite, as it's difficult to reliably benchmark. Going back to the topic of Destiny 2, I'm hoping you can help me test the workaround driver that should get you into the game. This is a beta chipset driver, and it may give you an installer warning or two if you're upgrading an existing driver, but I believe this should work around the D2 launch issue."
The issue apparently affects both current generation (X570) and previous generation (X470) motherboards, when running a Ryzen 3000 series processor. If you are affected by this, the first thing you should do is see if there is a BIOS update available, as that could fix the issue. If not, you can download the beta chipset driver here.