Title is copied from Mr. Avocado as I'm experiencing the same issue as well, not to mention a bunch of other people (CaliFreak, MAS, Term, Cluas, Aedin, NL & Grim as far as I've seen on the 'Help' section). Started happening to me on Monday, 26th September. I can load into the game, pick my character, traverse my inventory and everything else. But when I pick a destination to go to (this happens on every destination), it goes through the pre-flight animation (where the ship just chills for a bit before it takes off) and then the game crashes, without any error codes or a black screen. It just closes. I've tried the usual fixes (restarting the game, verified integrity of game files, restarted my modem, deleting game cache, updating drivers, reinstalling the game, etc) to no avail. Here's hoping that Bungo sees our cries for help. We'll be alright, boys <3 EDIT 1: Putting this here JUST in case BNGHelp4 doesn't see the fresh post I made with my PC details (https://www.bungie.net/en/Forums/Post/261836203?sort=0&page=0): Here are my details. Platform: Steam System Specs CPU: Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz 3.50 GHz RAM: 16.0 GB (15.8 GB usable) GPU: NVIDIA GeForce GTX 960 GPU Driver Version: 517.48 OS Version: Windows 10 Pro, 20H2 ISP Provider: Dhiraagu (A Maldivian ISP, I'm from & living in the Maldives) Speed: Upload - 19.59. Download - 15.16 Connection Type: Wireless (I would like to explain here that my pc doesn't have in-built wifi so I've had to use a dongle (I suppose?) from TP-LINK that allows me to connect to my home wifi. This dongle somehow bumps my download & upload down to 2mbps-3mbps and even with this bump down, I've never had lag/pullback issues of any sort while playing Destiny 2 (unless I used up my wifi data and it gets throttled, then my speed falls to 1mbps.) EDIT 2: I can play Destiny again! I checked on Saturday morning and the orbit bug was gone. I didn't want to jump the gun and update immediately, so I gave it the weekend. I'm not sure if this was Bungie that helped me out or if it just fixed itself randomly. In any case, thanks for Bungie for looking into this issue. Hopefully everyone else's bug gets fixed as well!