FatsharkLev

FatsharkLev


23 May

Comment

Sorry about that. This one is on our radar - thank you for the report!


11 May

Comment

This should be resolved now - can you please try launching again?

Comment

We’re aware and investigating the Backend Error being displayed on launch.

Apologies for the inconvenience!


10 May

Comment

Sorry to hear that! :frowning:

Let us know if the issue persists after switching your GPU.

Comment

Hm okay :frowning:

If you’re having issues around the launcher stage, I recommend trying steps here:

Read more
Comment

Possibly! Conflicting drivers and outdated/old drivers can occasionally cause some issues.

Have you been able to change your default GPU and resolve the crash?


09 May

Comment

Hi @dimo14

Sorry to hear that.

It may be useful to perform a Selective Startup. This can help diagnose whether a background application is resulting in your issue. This can be performed by:

  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

If the crashes no longer occur after having performed the Selective Startup, try re-introducing your programs one-by-one to determine which is causing your issue.

Let me know how you get on!

Comment

Hi @Braggart

Based on the information in the logs, it appears your default GPU is set as Microsoft Basic Render Driver - this is resulting in your crashes in Vermintide 2, as your default GPU cannot handle the demand.

Do you have another GPU that is not being detected?

Please see below for solutions for this problem:

  • Ensure your monitors are plugged in to the dedicated (as opposed to the integrated) GPU ports on the back of your PC
  • Perform a clean re-installation of your GPU drivers using the appropriate instructions below:
    • For AMD GPUs: ...
Read more

05 May

Comment

I can’t provide an exact ETA, but we have a fix internally, so this should be resolved in our next patch! Apologies for the inconvenience in the meantime.


03 May

Comment

Thanks! I’ve added this to our database for investigation.

Comment

Hi @GiuEliNo

Sorry about that :frowning: we’ll look into this - to help us, can you please provide us with your console log from the session that this issue occurred?

To do so:

  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
  4. Locate the console log that corresponds with the session in which the issue occurred, by looking at the timestamps in the log names
  5. Upload the appropriate console log to us

Thank you in advance!


28 Apr

Comment

They are the result of another change, but we didn’t intend to nerf or buff either of these. We’re on the case!


26 Apr

Comment

Of course! Feel free to shoot me a message :slight_smile:


25 Apr

Comment

Hi @RedBeardedGiant,

The logs do indicate a GPU-related crash. I recommend running through potential solutions here:

Read more
Comment

I’ve queried this with one of our Gameplay Developers, and it’s intended for weapons with shields to have a shorter range than the weapons alone.


22 Apr

Comment

Hi @Kitten,

What is your ‘Sound Quality’ and ‘Sound Channel Configuration’ setting under the Audio tab in Settings set to?

If you happen to catch a video of this occurring that would also be helpful to see.

Thank you!


19 Apr

Comment

Hi @ziyiqingyu,

Can you please provide us with your Steam profile URL (e.g. https://steamcommunity.com/id/FatsharkLev/) so we can take a look at this for you?

Thanks!


14 Apr

Comment

Thanks @Xadramare , we’ll take a look!


11 Apr

Comment

Hi @Kitten,

What is your upload speed? and do you have any issues if somebody else hosts?

Comment

Hi @Xadramare,

Can you please provide your console log from the session this issue occurred?

To do so:

  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
  4. Locate the console log that corresponds with the session in which the issue occurred, by looking at the timestamps in the log names
  5. Upload the appropriate console log to us

Thank you in advance!