Well, another Destiny 2 bug has been encountered by a number of players. According to reports, the Tracing the Stars 2 quest is not progressing and atlas skews are not respawning in the game for many players. So, here we are to share all the details about it with you. Continue reading this article to know more.
So, anyone who’s an avid Destiny 2 player should know that after Season 15, Destiny 2’s bug count increased rapidly. From minor annoying bugs to game-breaking major bugs like crashing, missing .dll files, the game is just getting worse day by day. Well, it is also true that Bungie is consistently working on providing solutions to the problems but without a hotfix, that won’t be possible. However, they did release a new hotfix for the game which fixed some of the most popular bugs in the game. But, most of the annoying bugs still remain in Destiny 2.
According to reports, Destiny 2 players are facing issues in the Tracing the Stars II quest as the Atlas skews are not appearing. If you have encountered the same issue, make sure to read the article till the end.
Did you know that players are getting errors codes in Destiny 2? The Marionberry error code seems to be appearing for a lot of players. To know more about this and how to get it fixed, consider visiting our detailed article here.
Destiny 2 Tracing the Stars II (2) Atlas skews are not appearing
So, on the official Bungie support forum, a player reported that after completing the quest, Tracing the Stars 2 on their hunter, and collecting the atlas skews on their Titan, the quest stopped progressing and the atlas skews are not respawning as well. Even after reacquiring the quest on all 3 characters, the atlas skews are not showing up as reported by the player.
Well, it is rather unfortunate for a player to be facing this issue, but we have good news as well. Bungie has acknowledged the issue and stated that they are currently investigating it. So, it is just a matter of time before the bug gets fixed. However, there is no official confirmation on the release date of a hotfix that will be fixing this bug. Therefore, all we can do now is wait and let Bungie come up with a fix asap.
