TL;DR: Guy troubleshoots vulture error. Reveals his findings. Got a message from a friend in California, asking for help with troubleshooting his constant vulture errors. I decided to assist. I live in Germany, my XB1 is wired directly to my router via CAT6 cable; Open NAT and all services available / 50 Mb connection. Here's what we did, and what we found: - Started XB1, went to network settings and ran all 3 tests. No issues. Open NAT and all services available - Using my friend's credentials, we signed in on my XB1. - At the Destiny start screen, cleared the game cache (hold L&R bumpers + down on D-pad) - Selected a Class (Hunter), cut to ship in orbit and get a Vulture error before party can stabilize - Quit Destiny. Signed out friend's account. Signed in with my account. No issues. I ran a strike and control just to be certain. - Quit Destiny. Signed out of my account. Signed in with friend's account. Selected a Class (Titan), cut to ship in orbit and get a Vulture error before party can stabilize. We repeated the steps 7 times. Every time I signed in with my friend's account I got a Vulture error. This leads me to believe the issue is tied to the actual user account, and not some home network, hardware issue. I appreciate any help getting this message to the devs. Thanks for your time.