orbitalsalttrooperx1
Member
Yep I really hope for a patch soon.@Yoshi Performance issues across the board. Can we get an update or insight on the issue? thanks for all your hard work. Love the game!
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Yep I really hope for a patch soon.@Yoshi Performance issues across the board. Can we get an update or insight on the issue? thanks for all your hard work. Love the game!
I've had these issues for 2 weeks, and I think I'm kinda done trying to fix this. It's not worth it to go further as an end-user. This is just a summary of everything I've tried, so that other people can evaluate if they wish to potentially waste their time (or not).
It was worse before the tweaks, but the final numbers for me are:
~260 fps in hideout.
~500 fps in the loading screen after match is found.
~190 fps when turning 180 degrees when spawning into an empty NYC, and staring at the back wall of the spawn.
~100 fps when turning back around, and facing mid.
~80 in the zipline while riding towards mid.
~110 fps when afk at the top of mid-bridge, looking directly forward (towards enemy spawn).
~90 in early game teamfights.
<60 fps in late game.
<40 fps at worst. Can happen in late game duels with only 1 enemy player on the screen.
This is all while at 20%-50% CPU and GPU usage, 3.5GB/8GB VRAM, and at the best around 12GB/32GB RAM. Console is giving warnings of thread starvation.
Here's a list of everything I've tried. If something is missing, it's more likely I forgot adding it, than not having tried it.
- lower/higher values for every cvar not tagged as cheat. I used cvarlist and went through the whole list line-by-line.
- OptimizationLock / Piggy's config. Tuned down further, disabled ragdolls etc..
- several dozen iterations of trying config settings not used in the above (ie. increasing texture budget out of curiosity).
- every in-game setting.
- every launch option commonly found on the internet. All fps limiters both on/off.
- different process priority values & processor affinity combinations.
- different Win32PrioritySeparation values.
- clean install of GPU drivers. Deleted GPU caches.
- enabled mod support.
- made sure I'm not participating in Steam beta.
- disabled Steam overlay.
- used Performance Monitor to check nothing else is eating up processor time.
- double checked that other games run just fine.
- run as administrator.
- checked there are firewall exceptions in place for DL.
- graphics -> Deadlock -> made sure the game is using GPU (RTX 4060 8GB).
- different power plans.
- shortly tried Process Lasso.
- network adapter QoS on/off
What I've done already before even trying Deadlock
- disabled all garbage features of Windows (ie. notifications, Cortana).
- disabled all unnecessary features in Advanced System Settings.
- removed bloatware, no mice/kb software running, no discord overlay.
- regularily check core speeds in CPU-Z. Regularily check GPU clock speeds in NVIDIA app.
- core isolation off
- all unused audio devices disabled.
thanks kingI've had these issues for 2 weeks, and I think I'm kinda done trying to fix this. It's not worth it to go further as an end-user. This is just a summary of everything I've tried, so that other people can evaluate if they wish to potentially waste their time (or not).
It was worse before the tweaks, but the final numbers for me are:
~260 fps in hideout.
~500 fps in the loading screen after match is found.
~190 fps when turning 180 degrees when spawning into an empty NYC, and staring at the back wall of the spawn.
~100 fps when turning back around, and facing mid.
~80 in the zipline while riding towards mid.
~110 fps when afk at the top of mid-bridge, looking directly forward (towards enemy spawn).
~90 in early game teamfights.
<60 fps in late game.
<40 fps at worst. Can happen in late game duels with only 1 enemy player on the screen.
This is all while at 20%-50% CPU and GPU usage, 3.5GB/8GB VRAM, and at the best around 12GB/32GB RAM. Console is giving warnings of thread starvation.
Here's a list of everything I've tried. If something is missing, it's more likely I forgot adding it, than not having tried it.
- lower/higher values for every cvar not tagged as cheat. I used cvarlist and went through the whole list line-by-line.
- OptimizationLock / Piggy's config. Tuned down further, disabled ragdolls etc..
- several dozen iterations of trying config settings not used in the above (ie. increasing texture budget out of curiosity).
- every in-game setting.
- every launch option commonly found on the internet. All fps limiters both on/off.
- different process priority values & processor affinity combinations.
- different Win32PrioritySeparation values.
- clean install of GPU drivers. Deleted GPU caches.
- enabled mod support.
- made sure I'm not participating in Steam beta.
- disabled Steam overlay.
- used Performance Monitor to check nothing else is eating up processor time.
- double checked that other games run just fine.
- run as administrator.
- checked there are firewall exceptions in place for DL.
- graphics -> Deadlock -> made sure the game is using GPU (RTX 4060 8GB).
- different power plans.
- shortly tried Process Lasso.
- network adapter QoS on/off
What I've done already before even trying Deadlock
- disabled all garbage features of Windows (ie. notifications, Cortana).
- disabled all unnecessary features in Advanced System Settings.
- removed bloatware, no mice/kb software running, no discord overlay.
- regularily check core speeds in CPU-Z. Regularily check GPU clock speeds in NVIDIA app.
- core isolation off
- all unused audio devices disabled.
can you share whats your system specs?The game is unplayable now. AMD hardware, used to be smooth 120 fps. Now it's stuttering badly every 5s, not even exaggerating.
Tried turning off everything else, latest driver, vulkan/dx11, FSR on/off, everything low, nothing works. It's not even fps drops. It freezes for 3s every single time.