FatsharkLev

No worries, I’ve updated this in our database. Thank you!

@Complexspeggle, I’ve checked this internally and I’ve been told that the rewards for these challenges are Shillings, and the skins mentioned are obtained by opening chests.

Are your challenges displaying different rewards? Could you please provide a screenshot if so, as this may be a bug.

Hi @krusader666,

Sorry to hear that!

Please can you try the following:

• Repair our Easy Anti-Cheat service.

This can be repaired using the EasyAntiCheat_Setup executable located in the Vermintide 2 ‘installers’ directory. The path to this directory on your PC will be similar to this:
C:\Program Files (x86)\Steam\steamapps\common\Warhammer Vermintide 2\installers\EasyAntiCheat

• Verify Game File Integrity (again), I do appreciate you mention having tried this already

Failing that, it may be worth it to try cleanly reinstalling Vermintide 2.

Let me kn...

Hi @shadowrygger,

Sorry about that - this specific crash can occur when trying to use a premium career on ‘Modded’ realm before first loading the character on ‘Official’ realm.

We’re working on a permanent fix for this, but for now please load into the Official realm as Warrior Priest, and then switch back to Modded.

We’ll check it out, thanks for the report.

As for Hukon’s Sundering, this should work with the Engineer, but requires 50% gun charge use.

Thanks @ZinStonehead! We’ll take a look.

@nevermay We’ve checked your account in the backend and nothing appears to be amiss (and we also found no backend issues for other players that reported a similar issue).

The only thing I can suggest is to try the PlayStation Support troubleshooting steps here:
https://www.playstation.com/en-g...

Hi @armyantsrule,

Veteran weapon illusions are included on weapons obtained from chests/vaults. However, when upgrading a weapon to veteran tier it is not possible to get them with illusions.

You’ve mentioned upgrading other weapons and these having skins, but this shouldn’t be possible

We’ve received some other similar reports, and we’re looking into it.

Apologies as I don’t have an immediate solution, but I’ll update you when I hear something!

Hi @Complexspeggle,

Can you please let me know your Steam Profile URL (or Gamertag / PSN name) so we can take a look at this for you.

Thanks!

Hi @ZinStonehead

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

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!

Thank you for the detailed report

I’ve queried this with one of our Gameplay Developers and have been told it’s very likely an oversight. I’ve raised this in our database and we’ll take a look!

Sorry to hear that. If you can provide a crash report, or your console log from the session(s) you crashed we can take a look

@CitizenKhaine we’ve removed the illusion applied by mistake, and this should now be reverted back to the default for you

Hi @CitizenKhaine

Please message me with your Steam profile URL and we’ll take a looksee

We’re aware of this crash - I’ve given this a nudge in our database. Thank you for the report @Harridas!

Hi @Aaxiom,

The logs indicate some of your game files have become corrupted.

I recommend running through potential solutions for this here:

This crash is on our radar - we’re on it!

Apologies for any inconvenience.

Hi @jlo317

We’ll take a look - can you please provide your console log from the session this happened?

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!

This crash should be resolved in our upcoming hotfix. Apologies for the inconvenience in the meantime!