XI
you are not logged in
News

Destiny 2's Trials Of The Nine Suspended Until Early November

And Day One issues on PC.

A number of seemingly minor bugs and glitches have been disrupting Destiny 2 over the last few weeks, first pushing back the harder Prestige Raid as they sought to stop an exploit in the final battle – in the end it launched this week with them simply tracking who had completed it legitimately – then this week’s Nightfall was changed at the last minute after a progression stopping bug, and now with the Trials of the Nine multiplayer mode suspended until a fix can be deployed in early November.

The glitch has been affecting Crucible, as players discovered that the Beurocratic Walk emote based off a famous Monty Python sketch would let them glitch through many of the walls in the game. It’s rather innocuous fun when you’re glitching into Tess Everis’ shop, but completely breaks multiplayer and Trials of the Nine in particular, when teams are seeking to go unbeaten and reach the top of The Spire and all the rewards that brings.

Who would’ve thought John Cleese’s antics could cause so much bother for Destiny players?

This bug will naturally mean that Trials of the Nine won’t be available right away when the PC version of the game launches next week on 24th October. A number of other issues are known about on day one, many of which are edge case scenarios from rare PC set ups, which you can find in the expandable section below.

Day One PC Known Issues

 

  • SLI, HDR, and VSYNC: Players may experience some rare issues when enabling SLI, HDR, or disabling VSYNC in some non-native resolutions. For the best experience, players are encouraged to use these features while running at their display’s maximum available resolution.
  • Saxophone Errors when Launching: Players may erroneously encounter Saxophone errors when launching the Destiny 2 application directly from the .exe file. Players who encounter this issue must close the application and relaunch through Blizzard’s Battle.net app.
  • Idling to Title Screen: In some activities, players who are returned to the title screen due to idling may be unable to log back in. Players who encounter this issue must close and relaunch the Destiny 2 application.
  • Login after Disconnects: A generic error code may appear to players who lose internet connection, which may block an affected player from logging back in even after reconnecting. Players who believe they are encountering this issue should close the Destiny 2 application and relaunch.
  • Buffalo Errors on multiple PCs: Players may encounter Buffalo errors when logging in to Destiny 2 on multiple PCs at the same time. To prevent this issue, players must ensure that they are logged out of Destiny 2 on any PC that they do not currently intend to play on.
  • Cursor in Tri-Monitor Configurations: Changing resolution between 5760×1080, 4080×768, and 3072×768 may trap the mouse cursor in the right-most monitor. Players who encounter this issue should ALT+TAB out of the Destiny 2 application, then back. Players may also toggle Windowed Mode by pressing ALT+ENTER.
  • Tri-Monitor Depth of Field: DOF effects may be overly aggressive on some tri-monitor configurations. Players who encounter issues with DOF can disable this feature in the Graphics Settings.
  • Windows 10 Game Bar: The Windows 10 game bar may not work in Fullscreen Mode. Affected players who wish to use this feature should use Windowed or Windowed Fullscreen Mode.
  • NumPad Binding: Players are not able to bind controls to most NumPad keys.
  • Screen Bounds on AZERTY Keyboards: Players may receive an incorrect key prompt when adjusting screen bounds on an AZERTY keyboard.
  • IME in Fullscreen: Players who are running Input Method Editors may encounter a black screen or delay when inputting characters in Fullscreen Mode. For the best experience, these players are encouraged to play in Windowed or Windowed Fullscreen Modes.
  • Closing Application: When closing Destiny 2 on PC, players must close the application via mouse input. Controllers cannot select the in-game button to close the Destiny 2 application.
  • Corporate and University Networks: Some players may be unable to play Destiny 2 on corporate or university networks. Players who encounter this issue must contact their IT department, to meet the connectivity standards outlined in our Network Troubleshooting Guide.

 

Source: Bungie, via Eurogamer

Read more: #
4 Comments
  1. Tony Cawley
    Pint! Pint!
    Since: Feb 2009

    Why they didn’t just remove the emote I don’t know. Trials is just about the only thing in the game worth doing right now. It’s removal, combined with GT Sport’s release means I won’t be playing Destiny 2 for the foreseeable.
    Bungie have really dropped the ball unfortunately.

    Comment posted on 20/10/2017 at 13:47.
    • Stefan L
      Community Team
      Since: May 2009

      They removed it from sale, but not from the game.

      Comment posted on 20/10/2017 at 15:09.
      • Tony Cawley
        Pint! Pint!
        Since: Feb 2009

        Yep. They should’ve removed it from the game, replaced it with a different one and refunded anyone’s silver who bought it.
        Then trials could’ve just gone ahead as normal.

        Comment posted on 20/10/2017 at 15:40.
  2. jeffyg3
    Member
    Since: Oct 2017

    Well I guess Super Mario Odyssey will be the only new game worth play next week. Either way Forza Motorsport 7 just came out and puts all other racing games to shame, might as well get catch up with that game while Destiny gets fixed…again.

    Comment posted on 20/10/2017 at 15:05.
19 hours ago
3
1 day ago
0

Latest Comments