Heroes,

We’re aware the 3.4 release has had a negative impact on ping and even the stability of your connection for some.

To help us solve this, we would appreciate it if you could post in the comments below:

• A description of your connectivity-related woes
• Your most recent console log*
• Your region
• Your ‘Download Region’ in Steam (Steam ‘Settings’ ‘Downloads’)

Please include any other information you believe may be helpful for us.

*Your console logs can be located using the instructions below:

1. Press the Windows key + R
2. Enter %appdata% within the search input and select ‘OK’
3. Navigate to AppData\Roaming\Fatshark\Vermintide 2\console_logs

Thank you in advance, and apologies for the inconvenience.

Related FAQs:

[PC] How to Resolve SIGN-IN TIMEOUT - COULDNT_CONNECT - CONNECTION TIMEOUT - COULDNT_RESOLVE_HOST Errors

[PC] Experiencing Matchmaking Issues or Being Connected to Players in Other Regions?

[PC] Playing From Russia and Experiencing Connectivity Errors?

Playing From Turkey and Experiencing Connectivity Errors?

For issues that are not connection-related (such as crashes), please avoid commenting here and instead create a new post in the Technical Support category.

Description: I play Vermintide with a bunch of IRL friends who live in the same city as me, with whom I usually have around 40-70 ms of ping. Since this patch, said ping has more than doubled, now going for around 110-150 ms of ping (usually 140). This is including people who live in the same apartment as me.
Oddly enough, my ping when playing with people from far away, like friends in the US and such, has largely remained the same.
Region: Argentina, South America
Download Region in steam: Argentina.
Latest console log: console-2020-12-04-20.53.01-716cb574-ed47-4f1a-9cdc-b62a6a31971e.log (3.5 MB)

some extra console logs:
console-2020-11-20-20.56.25-8e1d3ae0-2faf-4aac-b216-8c4d14cfa451.log (3.7 MB) Playing with someone living with me + someone from my same city, with me as client
console-2020-12-03-19.46.52-31319d47-9cf7-46fa-96ce-f8deb518017f.log (1.9 MB) Me as host with a friend from the same city

Valve have made some changes, but they might only be noticeable on the BETA Steam client. We suggest anyone suffering with eggregious ping since 3.4 should try out the new settings on the BETA client.

https://steamcommunity.com/groups/SteamClientBeta/announcements/detail/2918859890092727304

The new client setting is in the “In-Game” section, at the bottom under “Steam Networking”.
Here’s the associated FAQ:

https://support.steampowered.com/kb/9929-UAFN-9329/

NEW INFO:

All players in the lobby must enable this for it to be effective.

@Fatshark_Hedge
I tried the Steam BETA client and tried all of the options in that networking setting but experienced no changes in ping, even after rebooting the game and steam with each setting change (Default, Friends Only, Always)
Dunno why but the setting isn’t helping. It’s either a different issue, or the game is somehow ignoring said steam setting.

NEW INFO:

All players in the lobby must enable this for it to be effective.

Could you all try to set the sharing setting in Steam / Settings / In-Game / Steam Networking to Always and try again?

Has it been any better (or worse) than on the main Steam branch (non-Beta) throughout any of these steps?

Have informed the developer handling this. Thank you all.

You would need to opt in to the Steam Beta branch.

image740×586 24.7 KB

FYI: our developers are aware the Steam Beta has been unsuccessful.

Unfortunately those handling this have been away since before Christmas until (I think) tomorrow.

Hopefully we’ll see some movement on this soon.

Sorry for the delay all. I’ve been hesitant to say anything until we had confirmation, and I wish I could say “this will be resolved by -insert date here-” but it’s no secret we’re having a particularly hard time solving this.

With that in mind, the plan is to patch next week with additional telemetry capture so our developers can identify where and how exactly these connections are breaking down. What we have in place at current isn’t quite enough to diagnose an issue this complex.

I (and Lev, and Hedge) will do all we can to support our developers in solving this and provide regular updates to the community explaining where we’re at on this issue. I know blanket PR apologies are of no use here, actions speak louder than words and whatnot, but we really do apologise that this has been an issue for so long.

Turns out the telemetry will need to be enabled manually in the user_settings.config. We’ll explain how on patch day, it’ll only take a minute! Otherwise, yes please play the hell out of it.

'Tis intentional, it’s not something we require right now!

Quick update to say the telemetry has produced some interesting data and we’re back in contact with Valve to discuss what can be done.

I’m chasing it up, will report back as soon as.

Still doing a lot of back-and-forth with Valve, unfortunately. Holding out hope for something worthwhile by the end of the week.

The developer handling this has tried chasing up Valve twice now I think. Still waiting, bleh. This issue is not impacting the release schedule for upcoming content.

Valve have made some changes on their end with the telemetry provided by us in recent weeks. This has resulted in a promising new update to the Steam beta client, which we hope will roll out to the public release soon (please note, for this to be widely effective it would need to be rolled out to the public as all players will need the same build of Steam to see the benefit).

Whilst we’re hesitant to scream from the rooftops, we do hold hope that this will solve at least some of the issues presented with the networking refactor that happened with the Outcast Engineer release.

Of course, it’s hard for us to confirm until such changes are played on by the masses. We will of course continue to monitor the comments and data we receive, so be sure to share your experiences with us when those changes hit the live environment.

I don’t think Steam are able to provide an ETA, but I’ll try my luck tomorrow.

@DoctorGrumble What you’re experiencing here isn’t quite the same as what others have in this post, in your case your account data in our backend is corrupted - it should now be resolved.

Steam client update live! Keep me posted!

I hear some of you are still experiencing issues which is very unfortunate. Please do double-check you have the latest updates for the Steam client installed via ‘Steam’ → ‘Check for Steam Client Updates…’. No need to switch to the Beta, it’s all live.

I completely agree with you, PS4 is a mess. We’ve resolved it internally and are in the process of running it through the QA process, with the aim of hotfixing.

Apologies, I realise I haven’t replied but I have seen all of your responses. Just trying to collate the information I’ve been receiving and look for patterns.

Please continue to include the information requested in the OP, I need it!:

Could you please help us out by listing:

• Your region
• Your ‘Download Region’ in Steam (Steam ‘Settings’ ‘Downloads’)

To any new posters - please double-check you have the latest update to the Steam client installed!

Is anybody able to produce a Wireshark log for us, please? [PC] How to Run Wireshark – Fatshark

(Please PM me the log as opposed to uploading it here!)

Actually - new post here, please comment!