FatsharkJulia

Thank you for asking! There’s only Hedge and I in community roles at current, I’m sure this will increase at a later date.

My day varies a lot to Hedge’s day as I’m more Customer Support-oriented. I spend most of my day responding to queries from players who are having problems with Vermintide 2 (which could be anything really) and raising issues our players have reported to development, via our internal database.

Feedback is handled by Hedge and development, it’s not something I’m really involved with as there’s simply not enough hours in the day.

I’ve never really thought about how much reading we do throughout the day. It is a lot, but I think we’ve adapted to a point where we’re almost robotic with it.

As for what my average workday is like… I have multiple bases to cover, with the Support Portal being my priority as we adver...

This looks to be a caching issue - we need to look in to this. Could you please:

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

Then, make a copy of the ‘image_cache’ directory, zip it up and PM it to me please!

Please see your PMs.

This isn’t a Technical Support matter.

Hmmm, okay, is there anything potentially unconventional about his set-up or connection that you can think of?

Would he be able to connect to a VPN to see if the same error occurs?

Indeed players not using mods can also experience this issue, but it’s always worth disabling any mods so it can be ruled out as a potential culprit.

Apologies for the extended delay, we’re still looking in to this.

Hmmm, I see. Try logging out and back in, clearing your cache, etc.

You appear to already have access - see here.

Forum access will be open shortly before the second phase of the Winds of Magic Beta starts, so later today.

Sorry to hear this. Unfortunately we don’t have any solid solutions for the COULDNT_RESOLVE_HOST error at current as we’re still in the process narrowing down the causes.

The solutions listed here may help.

The initial crash is an issue on our end, although you appear to be the only person to have ever experienced it so you’ve been particularly unlucky here. I’ve raised it with development nonetheless.

As for the second crash, unfortunately it’s not entirely clear as to what could be causing this. It would be helpful if you could continue to send us crash reports.

Unfortunately the log is cropped at the end and lacking the crash data we need to see. Should this occur again, could you please send us the contents of the crash report window? What we really need to see is the long ‘GUID’ string.

I suspect this is an issue on our end which has been patched in Internal Test, I appreciate it’s an inconvenience but it may simply be a case of waiting on Internal Test to be pushed live.

I can certainly see a correlation with your crashes and Steam Authentication.

We need to be able to reproduce this on our end, so I’ve asked our Engine Developer as to how we should proceed.

Unfortunately we’re not able to recommend any solutions, as it’s something we need to look in to. Sincerest apologies for the inconvenience.

In this situation I would recommend that your buddy reaches out to Easy Anti-Cheat directly using the link here, and includes a copy of the problematic DLL. They will be best suited to assist in this case.

The RECV_ERROR is usually a result of using the Internet Protocol Version ‘IPv6’, which I appreciate isn’t the case for him.

Is he using a VPN, or anything else that could be interfering with his connection?

Sorry to hear this, I’ve raised your report with our Console Developers.

Oh, I’ve upped your permissions level so you should be able to PM me now.

My apologies @starkwaizer, the person I need to speak to is on vacation until Monday. I hope to have an update for you next week.