To build the PSO’s we need to know both the mesh data and the shaders, and in our engine thisis decoupled and thus needs to be built in runtime. So in some sense we can control this by coupling meshes and shaders but this reduce the flexibility when building games.

In darktide we have done several improvements to fix this. We built alot of the pso’s directly in the launcher by figuring out what meshes and shaders we use. (note im not a expert in this field).

I can check with my colleague how hard it would be to move some of this changes.

also from scimming through the logs it sounds like this is the issue. Like too high report rate, perhaps the windows queue quits very busy. However I will forward this to our QA so they can try reproduce the behaviour inhouse.

This also includes any kind of program that hooks into our app, like overlays.

my guess is that it’s HW related or perhaps external software interfering with the game, in some kind of setup that we have not tested locally, which means we have not seen this issue internally.

sadly the crash dump is related to one of the logs above (which is incomplete) but looks like it’s a script crash and not related to the application freezes.

to clarify if i set cap to 120 i got same print, if i set to 30 the id will be 1 instead

looks like it tries set cap to 120, 3 is the internal id for it.

Couldn’t repro locally so if there was an issue it has likely been fixed since then. Note that the beta was running older content than I’m testing

is the frame cap set to 3?

Please add any crashify link related to crashes, since we can’t otherwise investigate it, since it’s very likely we can’t repro it on our end.

I might not followed this completly.

Is the issue that the CPU is using 100% or that the FPS is low. Regarding why performance has decreased I can’t answer that at all but I might explain why 100% might be reasonable for one core.

But regarding 100% uthilization I would assume this is expected when you are CPU bottlenecked. Which VT2 oftens is due to heavy CPU usage.

The model is that we have 2 main threads, game and render thread that are the heavy lifters. We then have worker threads. If one of the main threads is the bottlneck it will likely be working ~100% of the time unless you cap the frame rate. if you would be GPU bottlenecked, these 2 threads would be idle in the end of a frame and thus not be working 100% of the time.

do you have a *.dmp file with matching name? ( 4c8009bb-47a2-4192-b169-70adcccdb6ee)

this has been fixed in our dev branch.

It’s unrelated to discord (the dump you gave atleast)

The issue with issues like this, is that we rarely can reproduce similar behaviour even if there is for sure situations where we have memory corruptions etc which would cause crashes that you have. Sometimes when it’s this re-occuring it can be everything from HW issues to some external program interfering (3d party record like fraps etc or anti-virus).

We have some upcomming fixes, it’s just hard to say if they fixes the issues you posted.

Regarding the network, it’s out of my expertise but I know they are working hard in fixing the issues repored there.

unfortunately it is still hard to see what the issue is.

The crashes looks quite different, so I can’t make a conclusion from it. How often do the game crash for you?

please attach crashify link or (since you said you dont get a crash report) full log and crashdump. crashdumps are found in the crashdump directory beside the log directory

We can’t lookup the crashes without the full crash report (that is in the log), but those are missing most info which is why we need the dump to actual look into what state certain variables are in.

is any of these logs from the actual crash? make sure the time stamps of the file matches with your session.

I can’t find the crash from the logs or guid, so there isnt much I can do from this info.

I think the report can be a issue with C# variant what adapter 0 is not matching the engines adapter 0.

please assign a crashify link or a crashdump, since I can’t investigate it otherwise.

I’ve added more info in the crash so we can see the cause, im sorry for the inconvenience.

thank you.

Hopefully we can patch this crash soon!

if not crashify link is provided, you can manually upload

C:\Users\Brian\AppData\Roaming\fatshark\Vermintide 2\crash_dumps\crash_dump-2020-11-21-19.13.10-fcac55ef-3876-418b-b11e-2efa8469e314.dmp

please add the crashify link you get when it’s crashing, since I can’t see that cause of the crash without it.

I can only see were you crash but not the cause of the crash atm.

it’s a crash in the nvidia driver, try a clean re-install of it and see if that helps.