great
great
is it resolved for you?
it’s a sound issue that too many sound events are triggered. We have a fix for the crash in our development. I will check with sound regarding this issue.
any way, I’ve done a couple of fixes for a few scenarious were we ended up with wrong resolution.
This will come with next patch I would guess. I hope this fixes your issues.
We have done some changes regarding alt+tab with WoM release
I have a repro for one case when this happens. I will solve that one and then see if that resolves your issue.
In my case I use Nvidia DSR to supersample the game.
ALT + ENTER is expected to be undefined behaviour atm but not ALT + TAB since we control the resolution manually during ALT+TAB but not ALT+ENTER (windows, drivers etc decide for that case).
Is anything of you setup that stands out? Are you running with super sampling (using nvidia settings), multiple screen etc?
I’ve tested this quite alot and never recieved anything else than the previous resolution.
could you upload a log from a “slow” startup? they are in %appdata%\Fatshark\Vermintide 2\console_logs
you can match your playsession with the timestamp on the file
There could be information in this that tells us if it’s a step within the vermintide.exe that takes longer time than expected.