FatsharkJulia

FatsharkJulia



18 Mar

Comment

Our Backend Engineer is looking in to this instead now.

He’s asked if you could potentially connect to a mobile hotspot (or any other connection for that matter) to see if the errors persist?

I appreciate this isn’t always an option.

Comment

A console log (not a crash report, confusing I know) should be produced for every session. :slight_smile:

  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

17 Mar

Comment

Nah, console logs please! Console logs are produced regardless of whether a crash occurs. :slight_smile:

  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
Comment

We’re looking in to this - but it would really help us out if you could upload the associated console logs.

Comment

We’re looking in to this - but it would really help us out if you could upload the associated console logs.

Comment

This will be resolved in patch 2.3.

Comment

Sorry, I see we must’ve missed your last post.

Could you please PM me your PSN ID? I can then pass this on to one of our Console Developers to look in to.


16 Mar

Comment

Unfortunately we appear to be in the midst of a connectivity hiccup - I’m looking in to it.

Comment

I’ll ask our QA department to check it out!


15 Mar

Comment

Hmmm! Timer begins within the Bell area, smash the chains up and drop down to where the Rat Ogre spawns but skip him - keep running, the achievement may not pop immediately.

Comment

If a report has been acknowledged, it’s in our database and awaiting resolution.

There is no need to repost crashes that have already been acknowledged. Crashes are a high priority by default, and I cannot make development work any quicker.


13 Mar

Comment

Could you try one more solution for me - a Selective Startup, if you haven’t already:

  1. Press the Windows key
  2. Type ‘msconfig’ and select ‘System Configuration’
  3. On the ‘General’ tab, select ‘Selective Startup’
  4. Deselect ‘Load startup Items’
  5. Reboot your PC
  6. Launch Vermintide 2 as normal, and attempt to replicate the issue

If the above is unsuccessful, I will then escalate this to our Network Engineer. It would help us out if you could include your most recent console logs, which 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

12 Mar

Comment

I’ve asked our Engine Developer to have a look at your crash reports, and will let you know once I’ve heard back.

Comment

Thank you for your report, I’ve popped this over to our QA department.


11 Mar