Warhammer 40,000: Rogue Trader Update 1.3 Release Date
Warhammer 40,000: Rogue Trader’s launch is part of Owlcat Games’ CRPG’s journey. In addition to its first DLC, patch 1.3 brings a variety of improvements to help smooth out the game’s overall play.
Rogue Trader’s patch 1.3 release date and content have not yet been announced, but we know when we can expect it to arrive. As stated in a thread in the Steam Discussions section, “the next major patch 1.3 is expected after/around DLC1.”
Void Shadows, the DLC referred to here, is currently expected to launch on September 24, 2024. Warhammer 40,000: Rogue Trader patch 1.3 release date: Around September 24, 2024.
It’s likely that Owlcat Games will reveal Rogue Trader’s patch 1.3 contents closer to launch, either through a teaser or two or by sharing the patch notes in their entirety.
However, the Steam Communi Page of Rogue Trader has created its own agenda and a list of problems to be resolved in the upcoming 1.3 update. The post stated that “The next major patch 1.3 is expected after/around DLC1. As usual, in the meantime, we’ll focus on bug fixes and minor updates.”
Awaiting Update 1.3 Release Date on the Steam Community Page
One of the features of this page is that both players and developers frequently post information that serves as an open guide. The players rest assured that their concerns are being addressed and the devs find an easy way to identify bugs.
In addition, there is an ongoing thread that lists problems and quick fixes from the devs. Here is an example:
1) The game’s loading bar is stuck or there’s a black screen after launching the game.
Solved by refreshing the cache.
Done by deleting all files except saved games, portraits and screenshots from the following folder: C:\Users\ <username>\AppData\LocalLow\Owlcat Games\Warhammer 40000 Rogue Trader
or, in the case of Mac:
~/Library/Application Support/unity.Owlcat Games.Warhammer 40000 Rogue Trader
As noted, meanwhile the players await update 1.3, they list their common problems on the website/ Devs try to find a hotfix or include it for the new update.
