AndRaxius
We will shortly be deploying a hotfix to the PTB to potentially address the Save Game Errors that some players were facing. Please update your PTB build when the update is available and let us know of any issues. Thank you.
Comments
-
As someone who's been playing since early 2018, I can safely say this is the worst state I've seen the game in.
-
If it's any help I have a 2070s and was experiencing rather large frametime spikes about once or twice a match, I fixed them by going into steam's launch settings and typing in "-preload -dx12", can't say for certain if it'll work for you but it's worth a shot. It is worth noting that quick little spikes in this game are…
-
That specific map set (as well as Crotus Prenn Asylum) have been disable temporarily due to several exploits and in-progress bug fixes.
-
The inverse is true for me. I switched from dx11 to dx12 to eliminate the massive frame drops I was experiencing (see the original post). Maybe it's a problem different from system to system, I suppose.
-
Another interesting thing of note is that when streaming the game over Discord with these launch tags, the streamed feed is frozen to the viewers, not sure why that's happening. I'll take it over having to deal with the stutters though.
-
Whelp, I hate to say this but I spoke too soon. After further testing the stuttering only ceases when using the Steam launch tags "-preload -dx12". That being said, it seems the stutter is caused by DirectX 11 for some reason.... I'm not exactly sure how, but is there a way to reinstall DirectX from scratch? I'm wondering…
-
Yes, I do keep my framerate locked to 120. The few times when the frametime goes over 8.3ms are negligible, and even when locking my frames to 60 the issue I was having still occurred. As far as I can tell that wasn't causing it.
-
I'm fairly certain I've fixed it. I went to Steam settings, then Shader Pre-Caching, and Disabled/Re-Enabled Shader Pre Caching. I didn't realize that Steam had it's own cache for shaders, as I had previously tried the same method with Nvidia's cache. After doing this I haven't encountered this issue after 3 games. I'll…
-
-Trapper needs some QoL with his traps, making logwood dye and the yellow bag would be a good start -Wraith's power is pretty good to me IMO, but making windstorm yellow would make him in a better spot -Plague needs some sort of nerf to her corrupt purge. As someone who plays exclusively killer I think her power is way too…
-
No reply, at least yet.
-
Welp, after about 2 weeks and repeated attempts to get people on my ticket to help out, still no luck.
-
Do they look like these by any chance? If so we're in the same wheelhouse it seems. I have a support ticket going right now, we'll see if anything comes of it.
-
Is there some sort of help desk I could email to find someone who can? If so that'd be really cool.
-
Network lag wouldn't show up on a frametime graph.
-
Neither of those DirectX tags function when appended to DBD, also I doubt it's raytracing since if it were I'd be seeing the memory clock going to 6801, but it sticks to 7.0GHz
-
No combinations worked, unfortunately
-
Yes, tried Ultra and Low, also the extra line didn't so anything. Given that the spike happens at seeming random times it doesn't seem to have to do with loading texture/assets as far as I can tell.
-
No luck, good try though.
-
Like I said before, I really don't think it has to do with downclocking. I've monitored a bit more and I've noticed a few instances where the CPU doesn't downclock at all. That being said yes I do have the Ryzen Balanced power plan selected. Selecting others has no visible effect. At this point I'll likely try a full…
-
Another quick piece of info, after a little bit more playtime I've noticed this also occurs in the lobby and one I even caught it during a loading screen. Seems it's not exclusive to when I'm in a match.
-
As a Blight main I really want that POV fix... I'm tired of feeling like a little scuttling creature.
-
Helpful
-
Just a quick update, not a whole lot. I tried reverting my GPU drivers and also changing my CPU power plan, no luck. Just eliminating variables until something sticks at this point.
-
I have a monitor for the voltage and the maximum amount doesn't exceed the amount I've set. It's likely not the CPU's fault. My current hypothesis is something to do with texture/asset loading, but I have yet to find RAM or VRAM data to prove it. Really weird, especially since otherwise the game runs completely well.
-
I keep my voltage locked so that shouldn't be a problem
-
Was it a manual OC or the automatic one in the BIOS? I know that generally speaking the clock shouldn't drop with a static but in my case mine will stay at 4.1ghz and then downclock back to 3.6ghz when there's little to no load, same with how my gpu downclocks to 1650mhz when I'm not using it. Plus I'm not sure if lowering…
-
It's not downclocking before, it's downclocking after. My cpu dynamically scales based on load (not sure if it's just an AMD thing), so my working hypothesis is that this is a result of the screen freezing and therefore the cpu briefly downclocks since the game is effectively idle during the spike. From what I can tell…
-
Only thing I've noticed when it occurs is my CPU downclocking back to 3.6ghz briefly, but I compared the times of the spikes to that of the cpu clock and it seems the drop is happening as a result rather than a cause. Other than that I haven't found anything that points to a specific resource aspect being the sole culprit.
-
Unfortunately it didn't work, still getting the same set of spikes.
-
It seems a bit drastic to allocate that much but I guess it doesn't hurt to give it a try...