Warhammer 40K: Darktide is a first-person action game set in the Warhammer 40K universe, developed and published by Fatshark. It was released for Microsoft Windows on 30 November 2022. The release for Xbox Series X/S will be revealed by Paul Naylor of the entertainment zone at a later date. The game has received a new update named March 23rd, which focuses on several fixes. As seen, the latest version does not offer major things. Check out the Warhammer 40K: Darktide Hotfix 50 patch notes below.
Warhammer 40K: Darktide Hotfix 50 Update Out Now, Patch Notes
- The Game Can Crash When Switching Between Fullscreen and Windowed Mode with FSR 3.1 Frame Generation Turned On
- FSR 3.1 Frame generation is unstable when used in combination with exclusive Fullscreen Screen. Specifically switching between screen modes is prone to crashing.
- We recommend using Borderless Fullscreen.
[*]FSR 3.1 Frame Generation does not do anything during excessive fullscreen effects
- FSR 3.1 Frame Generation excludes the entire screen from generation when there are a lot of fullscreen effects playing that impact all pixels on screen. This will cause frame gen to just copy the previous rendered result which results in the framerate looking like framegen is disabled while frame counters saying that it is running correctly.
- Penances Shown As Not Completed
- While migrating to the new Itemization system, there is a chance for a visual bug to occur where players with a lot of progression on their weapons might not see their Penances displayed as complete. This is only a visual issue which might occur when opening the Penances menu for the first time. Closing and opening the UI again will update it properly.
- Misaligned Weapon Skins in the Penance Preview Squares
- There are some weapon skin rewards in the penance previews that are misaligned or don’t fit in the square.
- Incorrect Rounding of Weapon Stats
- On uncommon occasions when looking at a weapon card, the total value of the potential stats distribution shown might add up to 1% higher or lower than the maximum (380).
- UPDATED: This is now known to not be a visual issue only. Rather, it involves different values being delivered by the backend than expected. This is being investigated.
