• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
Showing developer posts only. Show all posts in this thread.
While investigating crashes we have found a walkaround for the PS5 savegame issue. We’re working on a permanent solution to this problem, but meanwhile you can use the following:
The issue with PS5 made it impossible to play while using an old save game. You should start a new Royal Court game that will override the most recent autosave. Then you can proceed with your manual save of Northern Lords that should load and work.
 
Dear Players

We have some important news to share.
We have released a patch that aims to fix many of the smaller issues encountered after the release of the Royal Court, in particular the one that prevented you from Holding the Court.

The issues that are causing game crashes have top priority and while this patch does not resolve them, we’re working to have them fixed as soon as possible - expect more info shortly.

Below is the changelog for the current patch:



  • Fixed an issue where you are unable to “Hold Court” due to hidden events occuring.
  • Fixed an issue in the tutorial where you get stuck on the Court Artifact window.
  • Fixed an issue where incorrect exclamation marks appear on the Court Menu.
  • Fixed an issue where decisions or pop ups can cause the game to lose focus and navigation.
  • Fixed an issue in the UI where the Relatives box is misaligned in the character menu.
  • Fixed the position of the Artifact buttons.
  • Fixed an issue where the progress bar in the Marshal section jumps to the end when it is almost completed.
 
  • 1Like
Reactions:
Once you fix obvious top priority issues like crashes or being unable to retract vassal, can you take a look at other, game breaking, long lasting bugs:


Really, please, make the game playable if you can, because it's sad to wait months and didn't even get a feedback.

We are testing and preparing further patches that are aimed at resolving these issues. We want to make the game playable for everyone, and very soon.
 
Dear console players,

Today we have released patch 9.2 for XBOX, aimed at solving the identified memory issues.
This fix should result in less instances of game crashing, in particular for XBOX series S.

PlayStation5 patch is undergoing additional testing and we’re aiming to release it next week.
We are constantly working on new patches aimed at solving the game crashes and other critical bugs. Please follow this thread and expect to hear more from us next week.
 
Loading a pre-existing autosave from a previous patch can affect the game by causing crashes or making it unstable. While we work on fixing this issue, we recommend not load auto-saves but manual saves instead.
 
I'm on series s and before the update I couldn't manually save ironman games because it would crash most of the time, so I shouldn't even try to load those yet? Also it kept telling me that I didn't have room for save files and to delete some saves to make room for new ones so I deleted all of them and it still kept saying it when I don't have anything saved

There is a risk your game wouldn't work properly.
HOWEVER, it does not mean it's doomed - it could actually work fine. Please let us know if it worked!
 
It started out fine and worked great but then started saying the same save stuff. It will still auto save most of the time it just pops up what's in the first picture and then the second picture happens and it takes everything and wipes it.

So it started out great but after about 3 years in game time it started saying the save stuff again but it still auto saves it just does a pop up so I went to manually save and the first picture happened, it froze then went to home screen. The second picture is right after and it shows it deleted everything but I closed the game and restarted and it's all back to normal as shown in third picture. It hasn't crashed yet though so that's fixed it seems. I'm on ironman if that makes a difference.

Sorry to hear that!
Thank you for sharing details though - it helps and I hope we could find a solution soon.