Overclock.net - An Overclocking Community - Reply to Topic
Thread: [PCGamesN] [Updated] Early Ryzen 3000 adopters can’t play Destiny 2 Reply to Thread
Title:
Message:

Register Now

In order to be able to post messages on the Overclock.net - An Overclocking Community forums, you must first register.
Please enter your desired user name, your email address and other required details in the form below.
User Name:
If you do not want to register, fill this field only and the name will be used as user name for your post.
Password
Please enter a password for your user account. Note that passwords are case-sensitive.
Password:
Confirm Password:
Email Address
Please enter a valid email address for yourself.
Email Address:

Log-in


  Additional Options
Miscellaneous Options

  Topic Review (Newest First)
07-31-2019 07:30 PM
Diablosbud
Quote: Originally Posted by tpi2007 View Post
Hmm, thanks for the info, but does that mean that the game won't work on Sandy Bridge systems? (Edit: the official Recommended Specifications table states an i5 2400, so it will run) The first time Intel implemented a hardware number generator was with Ivy Bridge. I guess Bungie has a software mode built into the game to work around that, no? They could just use that for Ryzen 3000 series and there would be almost no downtime.
I think you're right. It seems like Destiny has a work-around if the instruction is missing. So the new Ryzen chipset patch disables the instructions and makes it playable again.
07-31-2019 08:49 AM
WannaBeOCer
Quote: Originally Posted by VeritronX View Post
New Chipset driver patch launched that should allow people to play destiny 2:

https://community.amd.com/community/...-and-destiny-2
That chipset driver list the same beta workaround listed in the article. Glad they can finally play, just in time for the Solstice 2.0 patch.

Quote from your link:

Quote:
Chipset Driver 1.07.29 also contains a beta workaround that resolves Destiny 2 application launch issues. This will ensure Destiny 2 players can immediately get back into the game.
07-31-2019 08:38 AM
tpi2007
Quote: Originally Posted by Diablosbud View Post
Destiny uses the RDRAND hardware random number generator. It uses specialized instructions, which fail on Ryzen 3000. Some Linux distros are also using these instructions.

It's definitely an overkill way to get random numbers for a game, but they probably decided it would be better for the loot system. I have no idea why, though, since other games work fine with software RNG.

Hmm, thanks for the info, but does that mean that the game won't work on Sandy Bridge systems? (Edit: the official Recommended Specifications table states an i5 2400, so it will run) The first time Intel implemented a hardware number generator was with Ivy Bridge. I guess Bungie has a software mode built into the game to work around that, no? They could just use that for Ryzen 3000 series and there would be almost no downtime.
07-31-2019 08:09 AM
EniGma1987
Quote: Originally Posted by WannaBeOCer View Post
No, which is a bit disappointing. I bet it's Bungie's anti-hack monitoring tool.
Ha. Like Bungie has something like that. So much BS went on in PvP in that game. Reminded me of the blatancy that CS 1.6 hackers had back in the day.
07-31-2019 12:17 AM
VeritronX New Chipset driver patch launched that should allow people to play destiny 2:

https://community.amd.com/community/...-and-destiny-2
07-31-2019 12:12 AM
Diablosbud
Quote: Originally Posted by tpi2007 View Post
Did Robert Hallock and / or Bungie at any point in the past actually explain what on earth a single game is doing to fail launching? Is it some overcomplicated form of DRM that happens to collide with AMD's chipset driver or encounters a rare bug in said driver or firmware?
Destiny uses the RDRAND hardware random number generator. It uses specialized instructions, which fail on Ryzen 3000. Some Linux distros are also using these instructions.

It's definitely an overkill way to get random numbers for a game, but they probably decided it would be better for the loot system. I have no idea why, though, since other games work fine with software RNG.
07-30-2019 11:28 AM
WannaBeOCer
Quote: Originally Posted by tpi2007 View Post
Did Robert Hallock and / or Bungie at any point in the past actually explain what on earth a single game is doing to fail launching? Is it some overcomplicated form of DRM that happens to collide with AMD's chipset driver or encounters a rare bug in said driver or firmware?
No, which is a bit disappointing. I bet it's Bungie's anti-hack monitoring tool.
07-30-2019 11:10 AM
tpi2007 Did Robert Hallock and / or Bungie at any point in the past actually explain what on earth a single game is doing to fail launching? Is it some overcomplicated form of DRM that happens to collide with AMD's chipset driver or encounters a rare bug in said driver or firmware?
07-30-2019 10:27 AM
WannaBeOCer Updated OP with update 3, they're working on a chipset driver workaround. They provided a link to the beta driver.
07-12-2019 11:07 AM
WannaBeOCer Looks like it turned out to be an AMD issue not Bungie's

https://www.phoronix.com/scan.php?pa...Linux-Zen2-Fix

Quote:
I just received the following official statement from AMD:
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.
This thread has more than 10 replies. Click here to review the whole thread.

Posting Rules  
You may post new threads
You may post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off