Bungie Support
Marathon Support活動概述
Bungie Support 的最新活動-
Bungie Support 已評論， 正式評論Hi there,Thanks for reaching out.What are your output device setting under Sound on your PS5? Is Switch Output Device Automatically On or Off?Also, have you tried selecting your TV as the output de...
-
Bungie Support 已評論， 正式評論Hello there, Thank you for this report. We have taken note of your report and will investigate this on our end.
-
Bungie Support 已評論， 正式評論Hi there, Thank you for reaching out. I'm sorry to hear that you are having issues with the game stability when trying to play the game.To start out, please ensure that all of your drivers, windows...
-
Bungie Support 已評論， 正式評論Hi there, Thank you for the report. We are aware of players reporting this issue and are investigating.
-
Bungie Support 已評論， 正式評論Hello there, Thanks for reaching out. Error code: WEASEL typically signifies you’re encountering a broad networking problem. If you haven't already, we recommend you refer to our Network Troublesho...
-
Bungie Support 已評論， 正式評論Hi there, Thanks for reaching out.While it may be possible to play on certain laptop configurations, we do not officially support them per our Marathon Storage and System Requirements guide. Beca...
-
Bungie Support 已評論， Hi there, Thanks for reaching out. Error code: WEASEL typically signifies you’re encountering a broad networking problem. We recommend you refer to our Network Troubleshooting Guide to explore pote...
-
Bungie Support 已評論， 正式評論Hi there, Thanks for reaching out. Error code: WEASEL typically signifies you’re encountering a broad networking problem. We recommend you refer to our Network Troubleshooting Guide to explore pote...
-
Bungie Support 已評論， Hi there,I have confirmed that this is intended. As per the patch notes: While this mode is running, other Rook queues will be disabled and all Rooks will filter into Sponsored Survival. For th...
-
Bungie Support 已評論， 正式評論Hi there,Thanks for reaching out.While there was previously an issue affecting the latest batch of Twitch Drops, a fix was implemented yesterday, so the issue should be resolved. Could you check if...
