[url=https://www.bungie.net/en/Explore/Detail/News/50712]Hotfix 3.3.0.2 [/url]should resolve this issue. Apologies to those affected by this issue.
English
-
Still getting the exact same issue even after updating and validating the game files :(
-
After Hotfix it still [b]DOESN'T WORK[/b] !!!!! Several attempts to launch itself. And finally the error: "[i]Steam - Error. An error occurred while updating Destiny 2 (the application is already running[/i])" What should I do ?!
-
Working for me on Windows 7 Pro SP1. ***I removed the 'community fix' DLL files that I had added to the game folder before I updated, just in case they caused an issue*** Be great if Xur could stock the (same roll as week 1) 'Bite of The Fox' sniper rifle on Friday, so I have a chance to buy it this time!! Really did not want to install Win 10 just for this game. Thanks for the fix guys!!, hope Bungie keep supporting Windows 7 for the foreseeable future. [b]Still an issue (as you guys know):[/b] 1. The PS4 controller will switch to the default Destiny layout on Steam and is broken, have to use DS4Windows now to use it. 2. Some of the cut-scenes run at 2fps, some don't? Think it's the game engine ones that are fine. but the 'cartoon' type scenes are broken. Still its a great video game and helps distract me when I need an escape.
-
Destiny2.EXE Application Error "The instruction at 0x00000000 referenced memory at 0x00000000. The memory could not be written. Click on OK to terminate the program" It just does not work. And if you do some how get it to work we need some serious compensation. Like raid tokens or tons of silver or enough bright dust to suffocate someone. This is just asinine with how long this has been going.
-
Cool finally a fix, now how about compensation for missing out on 4 weeks worth of Bright Dust and 2 weeks of eververse seasonal gear ornaments in the shop?! Heck make it 5 weeks worth of bright dust for the troubles... now that's 5 weeks worth on 3 characters.
-
Usually when a game development company screws something up this [b]BIG[/b] and it takes this long to fix it. They usually will got through a 3 step process. First, they acknowledge it was their fault. You did that with admitting it was an issue with the build; however, never bothered to explain how this very clear bug got through testing. Which tells your players, the people paying the bills by the way, that you didn't test it. Second, they issue a sincere apology to the affected player base. One little sentence isn't an apology. Lastly, they attempt to reconcile their error with the player base for the downtime through some form of compensation. You do realize that players that pre-paid for the season or bought Beyond Light Deluxe Edition probably have [b]EVERY[/b] right to sue Bungie, right? And probably have a pretty solid case at this point. But oh no... the "We fixed. Sorry guys." seems adequate enough to you. If nothing else this shows a lot about how unprofessional the company has become and how little you care for the people that continue to keep you employed.
-
Well they are celebrating 30 years of people supporting their company by letting said people give them another $25 for special content and weapons.
-
can we now get a fix for the fps plz and tnx
-
Действительно работает! =))))
-
Edited by Feltharion: 9/16/2021 5:54:24 PMHELL YES WE'RE BACK! IT WORKS! Thanks Bungo! And, well...it's "fine" as long as it doesn't happen again. Just be sure you guys have a Win 7 PC running tests as well next time, please.
-
IT WORKS FOR ME YESSS! I'm finally free of this month long torment!
-
20: 07:55: Starting the BattlEye service... 20:07:57: Starting the game... 20:07:58: A modification of the Windows kernel was detected. Please repair or reinstall the system. 20:07:58: The game could not be started. And how does this mean where is the promised correction and ?
-
Lmao really doing the minimum there huh.