Edit- We will be reverting this, so prestige levels will be restored to show as they were.
Correct, it didn’t make it in this time, but should be included in 4.2 which is coming sooner than you might think.
@I2ain could you please upload your most recent console logs? It would be very helpful.
Your console logs can be located in the Vermintide 2 AppData directory using the instructions below:
Thanks in advance!
@NewType could you please upload your most recent console logs? It would be very helpful.
Your console logs can be located in the Vermintide 2 AppData directory using the instructions below:
Thanks in advance!
No need for now!
Hotfix 4.1.1
Welcome to Patch 4.1! This updates comes with a slew of fixes and a couple of tweaks.
Critically it also includes additional telemetry capture so we can identify where and how lobbies are being affected by th...
Read moreOriginally posted by Bombthrowah:Huzzah! thanks for confirming :)Originally posted by Fatshark Lev: The weekly was missing (oops) but it should be fixed now. Is this not the case for you Bombthrowah? Could you check again please?It's fixed, thank you!
That’s all I need! Thank you, we’re looking in to it.
So, Error 1110
is another that is usually related to downtime/disruption with our service provider. If you were able to restart the game and resume without issue, then it’s likely to have been an unfortunate blip in the connection. Sorry about that!
Sorry for the delayed response @lSkillsl, that appears to be ok.
To confirm, are you still currently encountering this server error when attempting to play?
Hey @Yoda,
If you played on your own Steam profile using library sharing, then your progression should be intact if you purchase your own Vermintide 2 license for the same profile you played on through family sharing.
I assume right now you and your son already have different levels of progression, but just aren’t able to play at the same time?
Ok, so I’ve come across other similar player reports occurring during the Twins weekly event. I’ve flagged this internally for a deeper look. Thanks again for the report!
Hi @Bristly ,
Thanks for the report!
It appears to be a non-descript Access Violation
crash, which could be an unlucky one-off in this situation. Let us know if you come across this again, though.
Hi @DoctorEB1,
Looking at your console logs, your default GPU set is Intel(R) UHD Graphics 630
which is likely resulting in these crashes as it cannot handle the demand.
Do you have another GPU that it should be detecting?
If so, you can follow these steps: