banilla
Member
Most recent game ID as an example: 79602939
Persistent issue with the source2 engine in which the compiler appears to get stuck in an infinite loop in which the readout is spammed with hundreds of lines per second reading "[Prediction] Prediction time ([value]) is less than sim time ([value])? Clamping offset"
The upstream jitter value will be a wall or a bunch of red spikes before just being completely empty. From what I can tell, this loop causes the outgoing data stream to become completely saturated. I also notice a huge bump in data being received when this occurs.
Note the increase in received data at about 35 seconds, then from about 40 to 55 seconds.
The entire game freezes in place. I am still able to move my camera around, but all input stops, and then I get booted back to the lobby and forced to reconnect. Sometimes the error will crash the entirety of the steam client. Rarer-yet the error will crash my entire computer. I assume that if I had lower-end hardware, I would likely be experiencing more wide-reaching crashes when it does happen. (I will try to get around to running a bot game with my process usage up to test this later)
The issue occurs inconsistently, with no readily discernible trigger. I had played many games over the last couple of days with none of this issue apparent whatsoever. Around 25 games with no issue. There were rare moments where upstream jitter got very turbulent for a moment here and there (I have been playing with my data usage persistent on my screen out of paranoia of this very problem), but those seemed to get resolved by the system without an issue.
The issue persists even after the April 30th update. This is AGONY. It is bad for me, it is bad for my team. In terms of gameplay, it is worse than just having someone leave, because at least when someone leaves their body just goes and hides in spawn. My character will be stuck standing wherever they are before the DC firmly boots me out or crashes my client, then an AI takes my character back to spawn.
However, I cannot simply abandon the match because I will catch an escalating ban. One that I have been struck with many times now, with the last one being 6 hours.
I would mark this as a critical issue. Not only does it make the game functionally unplayable; The also issue seems to have the potential to cascade into other programs due to it crashing the entire steam client or desktop.
What I have tried (in no particular order):
Using different versions of proton (10.0-4, Experimental, Hotfix, 11beta, GE-RTSp)
Updating my motherboard's bios
Ensuring No component on my computer is overclocked (I have never overclocked any of this hardware
Trying Different DOCP profiles (DOCP I, DOCP II)
Verifying the Game files' inegrity
Reinstalling the game
Uninstalling the game, deleting all game files, and then reinstalling the game
Disabling Vulkan Shader Pre-caching
Playing on Vulkan
Playing on DX11
Playing with graphics settings turned as low as possible
Restarting Steam
Restarting Computer
Restarting Router
Restarting Modem
Physically removing my WiFi Card from my computer and only being plugged in via ethernet
Nothing has worked. The issue persists, and comes back randomly, so I cannot even be sure it is gone when it is not an issue.
I thought it was just on Linux, but apparently it's an issue across all operating systems. I've seen it reported with CS2 & dota2 as well.
Examples of seemingly or explicitly related issues:
This has been around for months with no acknowledgement. Can someone from valve please address this? Just let us know you have seen it. Possibly advise us on further troubleshooting measures? You have literally thousands of voluntary play-testers here for exactly this kind of thing. Use us.
Persistent issue with the source2 engine in which the compiler appears to get stuck in an infinite loop in which the readout is spammed with hundreds of lines per second reading "[Prediction] Prediction time ([value]) is less than sim time ([value])? Clamping offset"
The upstream jitter value will be a wall or a bunch of red spikes before just being completely empty. From what I can tell, this loop causes the outgoing data stream to become completely saturated. I also notice a huge bump in data being received when this occurs.
Note the increase in received data at about 35 seconds, then from about 40 to 55 seconds.The entire game freezes in place. I am still able to move my camera around, but all input stops, and then I get booted back to the lobby and forced to reconnect. Sometimes the error will crash the entirety of the steam client. Rarer-yet the error will crash my entire computer. I assume that if I had lower-end hardware, I would likely be experiencing more wide-reaching crashes when it does happen. (I will try to get around to running a bot game with my process usage up to test this later)
The issue occurs inconsistently, with no readily discernible trigger. I had played many games over the last couple of days with none of this issue apparent whatsoever. Around 25 games with no issue. There were rare moments where upstream jitter got very turbulent for a moment here and there (I have been playing with my data usage persistent on my screen out of paranoia of this very problem), but those seemed to get resolved by the system without an issue.
The issue persists even after the April 30th update. This is AGONY. It is bad for me, it is bad for my team. In terms of gameplay, it is worse than just having someone leave, because at least when someone leaves their body just goes and hides in spawn. My character will be stuck standing wherever they are before the DC firmly boots me out or crashes my client, then an AI takes my character back to spawn.
However, I cannot simply abandon the match because I will catch an escalating ban. One that I have been struck with many times now, with the last one being 6 hours.
I would mark this as a critical issue. Not only does it make the game functionally unplayable; The also issue seems to have the potential to cascade into other programs due to it crashing the entire steam client or desktop.
What I have tried (in no particular order):
Using different versions of proton (10.0-4, Experimental, Hotfix, 11beta, GE-RTSp)
Updating my motherboard's bios
Ensuring No component on my computer is overclocked (I have never overclocked any of this hardware
Trying Different DOCP profiles (DOCP I, DOCP II)
Verifying the Game files' inegrity
Reinstalling the game
Uninstalling the game, deleting all game files, and then reinstalling the game
Disabling Vulkan Shader Pre-caching
Playing on Vulkan
Playing on DX11
Playing with graphics settings turned as low as possible
Restarting Steam
Restarting Computer
Restarting Router
Restarting Modem
Physically removing my WiFi Card from my computer and only being plugged in via ethernet
Nothing has worked. The issue persists, and comes back randomly, so I cannot even be sure it is gone when it is not an issue.
I thought it was just on Linux, but apparently it's an issue across all operating systems. I've seen it reported with CS2 & dota2 as well.
Examples of seemingly or explicitly related issues:
- https://forums.playdeadlock.com/thr...an-sim-time-38-225071-clamping-offset.113211/
- https://forums.playdeadlock.com/threads/game-crashes-multiple-times-per-game.122870/
- https://forums.playdeadlock.com/thr...38-225071-clamping-offset.113211/#post-244053
- https://github.com/ValveSoftware/csgo-osx-linux/issues/4282
This has been around for months with no acknowledgement. Can someone from valve please address this? Just let us know you have seen it. Possibly advise us on further troubleshooting measures? You have literally thousands of voluntary play-testers here for exactly this kind of thing. Use us.
