{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
7/24/2019 8:18:58 PM
3
This long and still no fix. There is no way going to be pre-ordering a game that still cannot be run on my new hardware. If this is not fixed by the time Shadow Keep launches...Destiny 2 will be dead to me forever. There is no excuse given that AMD has identified the issue and the fix is still not here. In my opinion AMD should have thumbed their nose at Bungie and said fix it yourself...you are the only one with this issue. This is not Linux so Bungie's code is the issue.
English
-
Edited by Pickles Von Brine: 7/24/2019 8:23:14 PMYeah we are waiting on AMD at this point. I don’t think you understand what is going on. The issue is with the RdRAND instruction set. This is used for creating random numbers, important for cryptographic protection systems like found in Linux kernel and in Destiny 2’s security layer. To re-write something to not use this is a big task. Even with Linux you have to patch systemd to get it to work. However, if your system doesn’t boot that isn’t doable. This isn’t a Bungie issue. It is an AMD issue. It could have been caught if AMD used Ubuntu 19.04 during validation.
-
Issue is understood. They rolled the dice and found out they were not prepared for such an event. Placing the blame solely in AMD court is childish. It is always easier to point a finger at someone else. One cannot be prepared for every outcome just like AMD cannot be prepared in like. The issue still falls back on the coding no matter how much of a huge task it amounts to. There are other ways to accomplish the same task using similar methods. The cryptographic community did not all of a sudden come to halt and bash AMD for this incompatability. The PR nightmare would have been incessant giving Intel a big win to help soothe their security flaw bashing.
-
When both platforms use basically the same instruction set and one has an issue, that is not as easy of fix. Look, we are all frustrated. Bungie wants the game to work for us, we want it to work and so does AMD. We do not know officially the issues going on behind the scenes other than the fact it is a hardware issue. For now, the only thing we can do is wait. Early adopters ALWAYS get the short end of the stick. Something I should have kept in mind when buying my hardware. However, I still have my old system but others are not as lucky. Either way, it sucks regardless of how you look at it.
