{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
7/22/2019 5:40:41 PM
14
They already talked to ryzen a week or so ago. They will have a solution out most likely soon. Go check bungie’s help page on twitter
English
-
That was the talk about Agesa 1.0.0.3ABA, where AMD had said they found the problem... But that bios version has been pulled because it was buggy, and who knows how long it will take to fix. But even if, all the people that don't have X570 platforms are going to be waiting even longer to get the bios update. The game should be patched instead of bungie waiting for AMD.
-
Edited by TuxyDoh: 7/22/2019 5:55:30 PMThe real question is why AMD processors do not work with it? RDRand is an instruction to return random numbers from the chip, Destiny is build on RNG. AMD added this support in 2015 and should have known if their latest chip no longer complied with it. I would recommend putting pressure on AMD so that your several hundred dollar chip functions as they intended it to.
-
Edited by SagiC: 7/22/2019 6:00:29 PMLike I said, I heard RDRand is depreciated, I could be wrong though. That may be why it was not included? But weighing on whether it's depreciated or not, being that D2 is the only game with a problem I assume Bungie should be responsible.
-
Just because bungie is the only game using it does not mean they need to recode their game due to 1 chip that the manufacturer made an error. AMD has stated they are going to fix it as their product is not working right. From the wiki, it is not depreicated and is still commonly used in many cryptography and physics applications, so while d2 might be the only game you have that uses it, there are other uses for it and AMD need to fix their bug.
-
I know it's a bit tricky, I wonder how long it's going to take. What concerns me is that for users of X470 or B450 it may take multiple months to see a fix, which isn't really fair. Thats why I'm wondering how hard it would really be for Bungie to fix it on their end. And if that would be more practical in the end.
-
It depends on the level the game is pulling on it. Being a random number generator, my thinking goes to it being an integral part of the game since 90% of the game seems to be based on RNG. I think it could be done but question what would break in the change.
-
Edited by SagiC: 7/22/2019 6:16:36 PMI feel like it could be done too, there are many sources for random number generation these days. But ya, of course the consideration for what will prompt them to make the change is in question. Thats what I'm trying to figure out, but I have no clue how to get bungie's attention besides spiking a conversation about the problem. Any better ideas?
-
they know the conversations are out here. They are going to have to look at it at a business level, what are the costs and potential costs versus the risks and benefits of reworking the code versus waiting for AMD to fix it. Right now a very small population is impacted where in if their code bugs or has a negative impact on the game it would impact a much higher population.
-
I guess my Ryzen build is just going to have to gather dust then. What a shame. Suppose I could set up my second computer to have my old processor and move my graphics card to it when I want to play D2... What a pain though.
-
TBH this is why I am usually a generation behind. I do not like the downsides to early adopting tech. I prefer the bugs to be worked out. I am using my 2600x and eyeing the 3000 series for next year's build
-
Ya, I usually wait too, but the benches don't lie, Ryzen 3000 clearly performs very well. My OC'd 4770K is getting old and is starting to degrade, so I decided it was time. This just happens to be the bad luck that I usually get.
-
yeah the benches are crazy for them, I was tempted but held fast to my waiting stance. AMD has a good track record for their fixes. I mean they already know how to fix it, they just need to fix it without buggering the pci-e buss
-
Edited by SagiC: 7/22/2019 6:41:05 PMHoneslty I wouldn't even care about being in PCIE Gen2 temporarily, at least it would still work. Should have released them with an at your own risk disclaimer. But the Bios coders obviously don't want to be bothered with it. I assume that there were other bugs too.
-
I don’t know how that works, but if was a problem that could be fixed on bungie’s end wouldn’t they?
