Frametime stuttering/lag after Old Gods update

Used everything but citadel_hud_visible 0 and got these errors pretty fast in explore NYC.
[SV CommandQueue] [Tick 5397]['saltx' empty starved x1=15.6ms ping=0ms] LATE Recv usercmd 5213. Margin: 4.1ms net +-1 queue =-11.5 total
Bullet Hit Mismatch: client hit entity#2717/npc_trooper_neutral, server hit #0/worldent
[SV CommandQueue] [Tick 5963]['saltx' empty starved x3=46.9ms ping=0ms] LATE Recv usercmd 5775. Margin: 13.7ms net +-3 queue =-33.1 total
[SV CommandQueue] [Tick 5963]['saltx' empty starved x3=46.9ms ping=0ms] LATE Recv usercmd 5776. Margin: 13.3ms net +-2 queue =-18.0 total
[SV CommandQueue] [Tick 5963]['saltx' empty starved x3=46.9ms ping=0ms] LATE Recv usercmd 5777. Margin: 12.9ms net +-1 queue = -2.7 total
Excessive frame time of 100.51ms clamped. Acting as if the frame only took 100.00ms. (Last amnesty was 'ConsoleVisible', 1.95s ago)
Framerate spike report
FrameTotal: 100.53ms, tolerance: 10.05ms
excl ms excl % incl ms group
-------- ------- -------- --------------
97.32ms 96.82% 97.45ms Prediction
1.95ms 1.94% 2.59ms Client Rendering
0.58ms 0.58% 0.58ms PanoramaUI
0.15ms 0.14% 0.17ms ClientSimulateFrame
0.12ms 0.12% 97.58ms Client Input/Output
0.09ms 0.09% 100.53ms Unaccounted
0.06ms 0.06% 0.06ms EventFrameBoundary_t
0.06ms 0.06% 0.06ms Animation
0.05ms 0.05% 0.05ms Interpolation
0.04ms 0.04% 0.04ms CalcAnimationState
0.02ms 0.02% 1.32ms Frame Boundary
[SV CommandQueue] [Tick 6845]['saltx' empty starved x2=31.2ms ping=0ms] LATE Recv usercmd 6656. Margin: 9.5ms net +-2 queue =-21.8 total
[SV CommandQueue] [Tick 6845]['saltx' empty starved x2=31.2ms ping=0ms] LATE Recv usercmd 6657. Margin: 9.0ms net +-1 queue = -6.6 total
Bullet Hit Mismatch: client hit entity#2717/npc_trooper_neutral, server hit #0/worldent
Bullet Hit Mismatch: client hit entity#2717/npc_trooper_neutral, server hit #0/worldent

Also tried with citadel_hud_visible_0 which basically makes the game very hard to play and performance is the same.

Currently playing with streched mode instead of dlss and it runs a bit better but the stutters are there every match. Doesn't matter if its a standard game or if I am exploring NYC.
 
Used everything but citadel_hud_visible 0 and got these errors pretty fast in explore NYC.


Also tried with citadel_hud_visible_0 which basically makes the game very hard to play and performance is the same.

Currently playing with streched mode instead of dlss and it runs a bit better but the stutters are there every match. Doesn't matter if its a standard game or if I am exploring NYC.
Damn. Respect to the devs grappling with these demons, ain't no picnic!

Only other thing I could suggest is 1) disable MCE on the ASUS mobo / set cpu to intel defaults - test again. And potentially 2) e-core scheduling based off the log.

Set Windows Power Mode -> Best Performance
Disable e-cores in BIOS, Reboot
Test multiplayer. If fixed -> confirmed schedule issue

Which nvidia driver are you on?
 
I tried over four different drivers and currently I am on the newest one. I wrote in the first post in the thread that I already have tried disabling E-cores manually and via ProcessLasso.

I have tried different settings in my BIOS. Such as default mode, disabling XMP etc. I am also on high perf mode since ages so that doesn't help here.
 
I tried over four different drivers and currently I am on the newest one. I wrote in the first post in the thread that I already have tried disabling E-cores manually and via ProcessLasso.

I have tried different settings in my BIOS. Such as default mode, disabling XMP etc. I am also on high perf mode since ages so that doesn't help here.
Which one? The latest one (595.59) got recalled due to it causing fan issues (can lead to overheating). Doubt it's related to Deadlock's stutters but good idea to downgrade in any case.
 
Back
Top