Hey Everyone, Hotfix #55 (1.6.2) is currently being rolled out across our platforms and it should be out everywhere in an hour. You can read the notes below! Audio Fixes Fixed an issue that caused audio stutter and performance degradation when using virtual surround functionality on Xbox and PC (e.g. the audio crackling). Merged fixes for the audio stutter and stall issues that were first introduced in the “Path of Redemption” update. These were made much worse recently with the issue introduced in 1.6.1. These specific fixes were the ones we tested on the experimental branch on Steam. Fixed priorities for file reader queues, meaning audio will have higher priority than other file reads. [Audio System] Removed code for cancelling a read request since it could stall/deadlock for some users. [Audio System] Made “open” and “cancel” async so the audio thread is NOT blocked if open is slow. Improved reporting of stalls. Proper initialization of BypassIO support for direct storage. We are now checking properly for Win11, NVMe and NTFS in order to support it. Deadlock detection for all platforms (Previously only active on PC). General Fixes Fixed an issue where the “Purging Flame” Penance didn’t increment correctly. New items marker now properly shows in the inventory for emotes. Fixed a crash which could occur when a cosmetics vendor UI got forcibly closed (e.g. while browsing cosmetics in the Commissary asa mission was about to start). Fixed an issue where the Penance icons for the Dark Communion mission used a fallback icon. Fixed an issue where the Heat UI indicator for the Munitorum Mk X Relic Blade remained displayed also when the weapon was not wielded. Fixed an issue where some visual effects were missing for the Munitorum Mk II Relic Blade. Fixed an issue where the Munitorum Mk II Relic Blade had an incorrect chain-timing from Block to Special activate/deactivate. Chain-time has now been changed from 0.68 to 0.35. Fixed an issue where the Munitorum Mk II Relic Blade played the incorrect Special activate animation when activating the weapon after performing a Push follow-up attack. Fixed an issue where equipping the Munitorum Mk X Relic Blade or Munitorum Mk II Relic Blade in the Inventory applied an offset on other weapon animations when switching between weapons and loadouts. Havoc Fixes Players on the Mourningstar that are stuck with an ongoing Havoc mission can now cancel it from the Havoc terminal, at the expense of a deployment charge. If a player cancels an ongoing Havoc deployment and no more deployments remain, the player will get demoted One Assignment Rank and get a new assignment. Dev Note: Cancelling a Havoc deployment will provide a refund of the charge used to start the Assignment if it’s done in the first 60 seconds of attempting to start a mission. Afterwards, a player will not receive a refund for the charge spent. Players can demote an Assignment Rank to get a new Assignment that is one rank lower. Havoc mission participants now appear on the Havoc menu when a player starts a mission session. No participants outside of that list can be in the party for the mission to take place. Updated the “Cry Havoc!” event text to fully match properly across all languages. Fixed remaining overlapping text in multiple languages in the Havoc menu. Unobtained Havoc cosmetic items will now show up in the corresponding list in the Cosmetics menu. Cosmetic Fixes Fixed the Veteran “Lucius Mk IV Death’s Head with a Skull Mask (Krieg 143rd).” headgear cosmetic being incorrectly assigned another name. Fixed an issue where the cosmetic item rewards from an event would not show up in the Inventory until after logging out and back in again. Update on Incorrect Note from Grim Protocols (11 December) The previous Hotfix (1.5.11) pulled three missions from the mission board (Chasm Station HL-16-11, Magistrati Oubliette TM8-707 and Excise Vault Spireside-13). They have all been re-introduced into the rotation today, December 3rd. CORRECTION: Chasm Station and Magistrati have been re-introduced to the game but Excise Vault is still being addressed and it has not been re-introduced. 32 posts - 24 participants
