Destiny 2 Pc Issues
Yvette Burkhammer
I am having an extremely hard time getting my family working on this new router, we played this game all the time on our old routers and never really had too many issues. Something is absolutely broken on the new router but only for this game. It cannot login to the game (well I say that, it works 1% of the time after a very long time), it is 100% the wifi on the router as old router still works, even hotspot off my phone using the new routers internet works just fine. I have gone through every single setting I have found on the routers config page 192.168.1.1 and nothing has changed. Reaching out to see if there is any stupid things like hardcoded blocked ports or something somewhere that is blocking this game from doing what it wants. I can't really find any firewall type configs as far as I can tell nothing is blocked as far as traffic goes.
If you do have more then one game console that's all playing same game, you need to switch NAT filter to OPEN. It's the only way to get open NAT across all game consoles on NG routers. For some reason games when there are two or more consoles playing same game, can't use same ports so combined with uPnP and NAT Filter set to OPEN, allows the consoles to connect and get open NAT or in case of Sony, NAT type 2 which will all you'll ever see on PS consoles.
I've done a lot of research and testing back in 2010-2017 on game consoles, NAT types and NAT Kinds. Found that NAT filter to OPEN with a modem only unit and host router allows OPEN NAT for two or more games consoles.
Since you only have a CM1000, I would not use the Multi gig port for the internet connection to the CM1000 since the max rate the CM1000 can handle is 1000Mpbs. There is no reason to use the MG port unless you have something to connect to it that can support it. Connect the modem using the yellow internet port in back. Connect the PS console using the 1000Mpbs LAN ports in back as well.
I appreciate your replay but, This was something I tried, and this makes more sense in the context of the actual game itself once we start playing together that is when the p2p starts, the issue in this ticket is actually logging into the game. In my prior routers and also my current old router which I have plugged into this new model solely for the purpose of this game, I never switched off secured NAT so your statement is not entirely true, I have seen 3 or 4 nat errors over the 5 years playing this game so could pop up at times.
I appreciate your reply but, as mentioned in the ticket, I have no issues on other equipment all other things equal, also agree that the game could be to blame, however I am not interested in both sides of this playing the finger pointing game, "It's their fault". Thinking something new on this router as it is somewhat new that the game doesn't support. Seeing if there was some kind of toggle somewhere I could toggle off, but honestly I have tested everyone I have seen thus far.
Currently there are connection issues being experienced by FIOS customers in the US and Canada when connecting to the Xbox 360, Xbox One, Playstation 3 and Playstation 4 versions of Bungies mmorpg Destiny. Various errors are being presented to the end user including error codes newt, lion, bee, eel, fly, anteater, groundhog, jackrabbit, coconut, quail, weasel and pineapple. Connections to the game server are interrupted after a short amount of time ranging from several seconds to several minutes. Further reports of this issue can be found on the Reddit Destiny forum at Reddit.com/r/Destiny and the Bungie forum
This all happened following destiny's latest patch. I think any objective observer would be left wondering how this is a fios issue? Wouldn't this be better directed to bungie network support so they can either revert the changes they made, or for them to get with experienced engineers to find out what happened?
I also have connection issues (for 4-5 hours last night). Constantly kicked to orbit after 2-3 minutes in a game. Started sometime yesterday (it was working fine in the morning, then evening started disconnecting).
I'm having the same issues. Couldn't play for more than five miutes at a time without being kicked. More than anything, I'd like to know that this is being worked on or even acknowledged. Many people from the NY, NJ, and DC areas are having issues with this. Whether it be Bungie or Verizon's fault, this needs to be resolved.
I own a GIGABYTE Radeon RX 6600 XT and it's paired with a Ryzen 5 2600. I play a lot of Destiny 2. I usually get 100+ frames and smooth performance, truly something that I enjoyed. After 23.2.1, I've noticed an increase in CPU and GPU usage. The most disappointing outcome was that my game won't peak past 70 frames. It doesn't stop there. Even when getting 60 frames, when I'm in an environment with 3+ enemies, I lag and stutter HARD. I would drop into frames to low that some inputs are responsive during those sessions. I saw that in the notes for 23.2.2 that performance is improved with 6000 series GPUs and Ryzen processors. I was relieved that the situation was fixed. I tested Destiny 2 after the update and it's still the same. The driver update did not fix the issue. I have tired everything. Lightfall, the next big expansion, drops in less than a week. I would love to experience the expansion that I paid money pre-ordering. I have tried rolling back the driver but there isn't a previous instance of it on my PC so rolling back isn't an option. Is there anything else I can do?
Eh? Even if you can't roll back on the driver (whatever that means, as I've never heard of this for GPU drivers, yes, you can roll back to an older OS if the new one does doesn't suit you....I've heard of this), can't you simply uninstall the new driver (using DDU) and reinstall the old one?
That's is the best solution "You can find older drivers in the same page as the latest driver, just above the bold heading Knowledge base, you can find 'Previous drivers'.' ... System restore is not rolling back to an older O/S it is restoring your present O/S back to the way it was before installing Windows updates or driver installs or any major change to your system. If you want to learn how to use system restore and set it up here is a good article on how to do it -use-system-restore-windows-10
Have you double checked settings in the AMD drivers? It is possible that there is a changed setting that is affecting performance. I tweak my AMD settings and exported them once I was happy with them. I make sure I re-import them after doing a driver update. I always see roughly 6 settings needed to be updated.
I had the exact same issues in Destiny 2 with my 6750xt. I reinstalled my old drivers and it runs just fine. Hopefully AMD will roll out a fix soon, but until they do I'll stick with the drivers that work.
Using a 6600XT, Ryzen 7 2700X and 16 gb Ram. Well with my old driver everything ran perfectly smooth now I have a lot of lags, I have tried every possible settings like Vsync, Freesync and more. Nothing worked for me. I try to use an older driver now because this is unplayable.
Freesync and most older games have horrible performance, mega stutters on even the easiest game to run, I play CSGO, GW2 and L4D2. Those used to be smooth and now super bad, only way to play games is to roll back drivers.
Please could you provide some steps to reproduce the stuttering issue you see in Destiny 2 on 6650 XT with 23.2.2 driver? Additionally, please can you let me know what image qualitysettings you are using in the game?
Its the same problem with me currently, running a 5900x and a 6900xt gpu, never had these problems before - I have tried a reinstall of game = no luck, i have tried all settings on low = no luck.
Close to giving up, i will admit first time using a amd gpu on destiny 2 and ive had this problem, used a old 980ti back in the day and it was buttery smooth.
I have a 6700XT Elite and have the same problem as well, the only option to fix the stuttering is to roll back to driver version 22.11.2. This can be painful if you ever want to play a newer game released in 2023 that requires the latest supported drivers. so if I want to play destiny roll back, restart computer, load exported driver configs from 22.11.2. If I want to play a new game, upgrade drivers to latest version, reboot then start it up. It's been a lot of fun. not sure If I'll buy another AMD card in the future. I'm guessing AMD has no plans to fix this as they are already on 23.5 2 at the time of writing this. The problem happened at version 23.0.0
The list of issues includes lack of incentive (which is the biggie), lack of new maps, maps being taken away, lack of modes and options, and the overall structure. The most recent bone of contention in the community is the presence of Stasis. I would also propose that the very nature of what Destiny 2 is means that PvP will always be contentious.
Therefore, my suggestion is that we need a better flow of material rewards from Crucible, as well as better PvP loot. And these rewards need to be farmable in an intentional way by players. Without proper incentive, we will never have the PvP population the game deserves.
When it comes to the timing of the Stasis effects on guardians, those should also be kept to a minimum. Bungie already fixed that earlier this season, so it should never have a longer effect than it has now.
Hi Team
Recently i purchased a brand new A770 and the game runs perfectly on games such as Apex Legends, Hogwarts Legacy, Metro 2033, so many games i have tested and i can 100% say the issue is not the card nor hardware since every other game in existence runs fine.
But destiny 2 specifically during dungeons and in Neomuna during is display artifacts on the screen, white and purple flashes, and performance issues which is really disappointing since this issue has been raised for months with no fix in site and proven by alot of people so its not just me experiencing this.