Nightingale to weasel, tried everything plus what is on youtube
I am unable to launch into a match of Marathon while attempting cross-play with friends, despite my local network and Bungie's servers functioning perfectly for Destiny 2.
-
My Platform: PC (Steam)
-
Teammates' Platforms: PS5 (Two players joined my fireteam lobby)
-
The Trigger: The issue occurs immediately upon hitting "Run" to initiate matchmaking, while the game is actively loading and connecting.
Error Progression & Symptoms
-
First Attempt: Received Error Code: Nightingale during the initial load screen.
-
Second Attempt: Immediately hit with Error Code: Weasel upon trying to reconnect.
-
Subsequent Behavior: Persistent connection failure strictly within Marathon.
Troubleshooting Already Completed
To isolate the issue, I went through the official Bungie Help Guides and community resources, executing the following steps to no avail:
-
Followed all steps in the official Network Troubleshooting Guide (including flushing DNS and power-cycling network hardware).
-
Verified integrity of game files on Steam.
-
Completely uninstalled and cleanly re-installed Marathon.
Cross-Game Isolation Test
To verify if this was a localized hardware, account, or ISP issue, I launched Destiny 2 on the same PC and network:
-
Result: Destiny 2 loads completely normally.
-
Observation: I am able to freely navigate public spaces (the Tower) and utilize Bungie's live servers without a single error code or disconnection.
Request
Given that my network connects flawlessly to Bungie's Destiny 2 infrastructure, why am I experiencing persistent, game-breaking network errors (Nightingale/Weasel) specifically when initiating cross-play matchmaking in Marathon? I need technical insight into what is blocking this connection or if this is a known cross-play routing bug with Steam-to-PS5 lobbies.
Comments
Hi there,
Thanks for reaching out!
This sounds like a connection issue of some kind is occurring and could be an internet service provider issue.
Below are suggestions that may help with your issue:
Please sign in to leave a comment.