Pop me a PM and we can sort that out for you.
Could you please upload the console log associated with this session?:
- Press the Windows key + R
- Enter %appdata% within the search input and select ‘OK’
- Navigate to AppData\Roaming\Fatshark\Vermintide 2\console_logs
Timestamps within the log names should help identify which is needed.
Thank you!
This appears to be unrelated to the previous crashes, try lowering your ‘Worker Thread’ count within the launcher’s ‘Settings’ menu down to 6 and see if there’s any improvement.
I must ask - have you tried re-launching Vermintide 2?
Apologies for the delayed response. Would you be able to provide several additional console logs, please? (Assuming this is still an issue for you)
We’re working on it, I’ll see if we can speed it up.
Sorry about your crashes - I’ve passed your console logs on to our Backend Engineer for review.
You’re very welcome, I’m pleased to hear that!
This appears to be a memory-related crash.
Could you please ensure your ‘Virtual Memory’ is set to ‘Automatically manage paging file size for all drives’ by:
- Navigate to Control Panel > System and Security
- Select ‘System’
- Select ‘Advanced system settings’
- Under the ‘Advanced’ tab, select the ‘Settings’ button underneath ‘Performance’
- Select the ‘Advanced’ tab
- Select the ‘Change’ button underneath ‘Virtual memory’
- Ensure the ‘Automatically manage paging file size for all drives’ checkbox is marked
- Restart your PC
Any particular Difficulty you’ve noticed this on?
I appreciate the unexplained drops in performance are tiresome.
I think, the most notable obstruction our developers and QA have encountered is being unable to replicate these issues internally.
It would really me out if you could add your information here:
I will send out a reminder internally that performance-related complaints are still rampant.
Read moreI must ask, have you tried restarting your PC since the crashes started?
All posts are closed automatically after a week, to prevent them being necro’d. Once an update has been received, I either respond to and re-open the original post or send a PM.
Your crash is still in our database, awaiting inspection by a developer.
Sorry I don’t have an update for you at this time.
Is it more like FPS lag, or network lag?
Sorry about this, I’ve sent a reminder to the developer looking in to this.
Good to know. Thank you.
I suspect this has something to do with the foundation/scripts/util/error.lua:22: Can't freeze unit of breed nil
crash, which we’re working on.
(I should add that the other crashes here appear to be more localised, I suspect due to the higher-than-average ‘Worker Thread’ count).
Try putting it way lower, like down to 6.
This is an issue in our code - it’s on our radar. Sorry about that.
Read more