My 2 cents:
1. According to latest Steam survey - there is still around 5-6% people using Windows 7 so we can safely assume that similar precentage of Destiny 2 player population (probably even higher addinng Win8 and some Win10 users) cannot even start the game right now. It's not some kind of "silly" - "triumph/activity/etc. is not working and/or bugged" or "I cannot see an emblem"... but literally "I cannot launch the game at all". In Customer Support and ticketing terms - it's a freaking P1 incident!
2. How is it possible that a company releasing a product and stating the minimum and recommended requirements in terms of OS is not checking if the product works on that OS? You already had a yellow card once Beyond Light launched with the 1 FPS cutscenes on Windows 7 (not fixed until today BTW but at least it's not game breaking) and you still didn't learn a lesson? Now it's a red card unfortunately...
English
-
Oh, did they fix the cutscene thing?
-
Edited by GaJoS: 8/26/2021 9:25:50 AMI'm pretty sure they didn't. Maybe I phrased it wrongly - what I meant was that it is still not fixed to this date.
-
Ah I see what you meant now. It was the "until" that confused me.
-
How could that be confirmed, when everyone it affects, can't run the game because of this issue?
-
You have an excellent point and that's part of why I asked for confirmation
-
Unless... this bug is the "fix". We no longer have 3 FPS cutscenes because we no longer have cutscenes.
-
What if we correspondingly fixed Bungie's executive pay gap problems by letting the company go bankrupt so there isn't a Bungie to have executives overpaid millions a year? Just a thought. I feel for all the underpaid, overworked Bungie workers and ex-workers who aren't fortunate enough to be in the executive management suite. Especially the ex-workers who were replaced with lower-paid entry-level graduates with no work experience. And people like Martin O'Donnell, Peter Dinklage, Jamie Chung and Gina Torres. I am no fan of Pete Parsons or his income.
-
Well said, but let me counter with this: Destiny 2 is specifically a multi-year-old game, not one of the newest releases from scratch. The total Destiny 2 userbase of pre-win10 users is probably much LARGER than for a new title or Steam as a whole. Then also consider what a small percentage of affected users are probably logging in and/or creating forum accounts to report the problem or even upvote the threads about it, since they can see that it has at least been reported. I'd like to encourage all affected players to login and make it clear to Bungie that you, too, are affected. It may get this resolved quicker and better. Don't just sit back and wait, everybody!