As in the title, I am almost 100 hours in the game, and never encountered Jomsviking at rank higher than 1. My Jomsviking Hall is not max upgraded, but it is at level 3, and from description it should be able to give me even rank 4 jomsvikings. While I can get some rank 4 raiders, players jomsvikings are always at rank 1. I saw similar topic created almost a year ago, but it seems like the issue was never properly addressed back then.
Re: [players' Jomsviking always at rank 1](/topic/95848/players-jomsviking-always-at-rank-1)

Well, for me the crashes went less frequently since I manually set vram to higher value, but still happen sometimes. As far as I noticed, crashes only happen in England, and the greatest probability of it happening is during first 30 minutes of game, if it's past that time, it won't crash anymore.


...unless you want to do a screenshot. In that case it crashes again.

• Have you been able to complete our basic PC troubleshooting guide? These steps help to tackle a number of common causes behind crashes / freezes, and provide us with a basis for further investigation. Answer: Yes
• What are your system specs (CPU/GPU)? Answer: i7-10700F, RTX 3060, 32GB RAM, Win 10 
• Have you been able to play the game without experiencing crashes / freezes before? Answer: Yes. Althought I had problems with crashes few months ago, at some point after 1.42.1 it was better. But since last week or so here we go again(I didn't play for some time, so I can't specify exact date when it started again)
• When did these crashes / freezes first occur? Please be as exact as possible. Answer: Anywhere in England, no matter where I am and what I do. Totally random. Nothing in Norway.
• Have you made any recent changes to your system, such as updating your Operating System or installing new software? Answer: I'm keeping system and graphisc drivers always updated. It is also recommended in point 1, troubleshooting..
• Are there any specific triggers for these crashes / freezes? For instance, do they happen when launching the game, or during a loading screen? Answer: None. It just freezes without any prior indication.

COME ON UBISOFT, TWO AND HALF YEAR SINCE THE PREMIERE AND YOU STILL CAN'T FIX THIS [censored]!

@camsaw1 Yup, in last few days it started to freeze every few minutes, making it totally unplayable. I had more than 100 hours, but now can't do anything. And definitelly won't buy any more games from them.

If anybody is interested - I solved this issude by manually restricting max FPS to 60 in my graphics card settings(I use NVidia graphics). I had max 60FPS set inside game earlier, but apparently it wasn't working properly. Played few hours now, no freeze happened. It caused me to see screen jumping instead of fluid moving when I synchronize point and camera shows enviroment and when I use minimap, but at least game is playable.. When I tried to set FPS to 90 and more, aforementioned issues wasn't noticeable, but freezes still happened.

@camsaw1 Yup, in last few days it started to freeze every few minutes, making it totally unplayable. I had more than 100 hours, but now can't do anything. And definitelly won't buy any more games from them.

• Have you been able to complete our basic PC troubleshooting guide? These steps help to tackle a number of common causes behind crashes / freezes, and provide us with a basis for further investigation. Answer: Yes
• What are your system specs (CPU/GPU)? Answer: i7-10700F, RTX 3060, 32GB RAM, Win 10 
• Have you been able to play the game without experiencing crashes / freezes before? Answer: Yes. Althought I had problems with crashes few months ago, at some point after 1.42.1 it was better. But since last week or so here we go again(I didn't play for some time, so I can't specify exact date when it started again)
• When did these crashes / freezes first occur? Please be as exact as possible. Answer: Anywhere in England, no matter where I am and what I do. Totally random. Nothing in Norway.
• Have you made any recent changes to your system, such as updating your Operating System or installing new software? Answer: I'm keeping system and graphisc drivers always updated. It is also recommended in point 1, troubleshooting..
• Are there any specific triggers for these crashes / freezes? For instance, do they happen when launching the game, or during a loading screen? Answer: None. It just freezes without any prior indication.

COME ON UBISOFT, TWO AND HALF YEAR SINCE THE PREMIERE AND YOU STILL CAN'T FIX THIS [censored]!

Well, for me the crashes went less frequently since I manually set vram to higher value, but still happen sometimes. As far as I noticed, crashes only happen in England, and the greatest probability of it happening is during first 30 minutes of game, if it's past that time, it won't crash anymore.


...unless you want to do a screenshot. In that case it crashes again.

@azullfr So basically you can't recruit players' Jomsviking with rank more than 1, and you can level only one Jomsviking - your own.. That means the description of Jomsviking hut is at fault, because it clearly states that it would have not Raiders, but Jomsvikings that have higher ranks.

As in the title, I am almost 100 hours in the game, and never encountered Jomsviking at rank higher than 1. My Jomsviking Hall is not max upgraded, but it is at level 3, and from description it should be able to give me even rank 4 jomsvikings. While I can get some rank 4 raiders, players jomsvikings are always at rank 1. I saw similar topic created almost a year ago, but it seems like the issue was never properly addressed back then.
Re: [players' Jomsviking always at rank 1](/topic/95848/players-jomsviking-always-at-rank-1)

@ubi-oxavo I left the quest for a few hours, and when I came back it was reset, so I tried to do it again from the beginning, and this time attackers were properly loaded and I was able to finally finish task.

I lit the lights, swam with boat to the other side, killed attackers, but still can't initiate conversation with blind viking. Also the quest marker went back to the first light for some reason. Good to know that the bug still exist half year after threads about it were closed.