PrimitiveStalker 4 / 2,154 Report Post Posted July 15, 2018 Hello guys, unfortunately again it's me not able to join the EU-BHOP-server. Console says: Netchannel: failed reading message 2 from 79.137.121.134:27015. Killer replay stuck waiting for tick message for 0.75s, requesting update Killer replay stuck waiting for tick message for 1.50s, requesting update and so on... Skimmed trough google and it appears to be a bug with the Killer replay who can be both client and server-side. Checked client-side by turning off killerreplay which SHOULD fix it but it doesn't. So if you could look into this issue it would be great! Greetings Share this post Link to post Share on other sites More sharing options...
Snowy 837 / 11,431 Report Post Posted July 15, 2018 @PrimitiveStalker I've gone ahead and udpated the SourceMod on the server, I'm able to join it. Though i'm not entirely sure about you, might want to try it out Share this post Link to post Share on other sites More sharing options...
Rena 2,779 / 34,029 Report Post Posted July 15, 2018 I was having this issue as well. Share this post Link to post Share on other sites More sharing options... Achievements
Snowy 837 / 11,431 Report Post Posted July 15, 2018 @Misaki, are you able to join now? Share this post Link to post Share on other sites More sharing options...
Malal 145 / 0 Report Post Posted July 15, 2018 spec_replay_enable 0 should fix the second error, might need to disable (or enable) GOTV You can disable killer replay on the client side to fix it Forgot the command but it might be cl_disablefreezecam "1" Share this post Link to post Share on other sites More sharing options...
rapperdan 2,323 / 0 Report Post Posted July 15, 2018 Edited July 15, 2018 by rapperdan I pinged off of a server one time here is what happened. Connecting to public(104.153.105.207:27015) ... 19394.241: Sending connect to public address 104.153.105.207:27015 via UDP Retrying public(104.153.105.207:27015) ... 19396.248: Sending connect to public address 104.153.105.207:27015 via UDP Retrying public(104.153.105.207:27015) ... 19398.249: Sending connect to public address 104.153.105.207:27015 via UDP Retrying public(104.153.105.207:27015) ... 19400.256: Sending connect to public address 104.153.105.207:27015 via UDP Retrying public(104.153.105.207:27015) ... 19402.258: Sending connect to public address 104.153.105.207:27015 via UDP Retrying public(104.153.105.207:27015) ... 19404.266: Sending connect to public address 104.153.105.207:27015 via UDP Retrying public(104.153.105.207:27015) ... 19406.268: Sending connect to public address 104.153.105.207:27015 via UDP Retrying public(104.153.105.207:27015) ... 19408.272: Sending connect to public address 104.153.105.207:27015 via UDP Retrying public(104.153.105.207:27015) ... 19410.273: Sending connect to public address 104.153.105.207:27015 via UDP Retrying public(104.153.105.207:27015) ... 19412.274: Sending connect to public address 104.153.105.207:27015 via UDP Retrying public(104.153.105.207:27015) ... 19414.276: Sending connect to public address 104.153.105.207:27015 via UDP Retrying public(104.153.105.207:27015) ... 19416.277: Sending connect to public address 104.153.105.207:27015 via UDP Retrying public(104.153.105.207:27015) ... 19418.281: Sending connect to public address 104.153.105.207:27015 via UDP Retrying public(104.153.105.207:27015) ... 19420.290: Sending connect to public address 104.153.105.207:27015 via UDP Retrying public(104.153.105.207:27015) ... 19422.297: Sending connect to public address 104.153.105.207:27015 via UDP Retrying public(104.153.105.207:27015) ... 19424.304: Sending connect to public address 104.153.105.207:27015 via UDP Retrying public(104.153.105.207:27015) ... 19426.305: Sending connect to public address 104.153.105.207:27015 via UDP Retrying public(104.153.105.207:27015) ... 19428.309: Sending connect to public address 104.153.105.207:27015 via UDP Retrying public(104.153.105.207:27015) ... 19430.316: Sending connect to public address 104.153.105.207:27015 via UDP Retrying public(104.153.105.207:27015) ... 19432.324: Sending connect to public address 104.153.105.207:27015 via UDP Retrying public(104.153.105.207:27015) ... 19434.330: Sending connect to public address 104.153.105.207:27015 via UDP Retrying public(104.153.105.207:27015) ... 19436.338: Sending connect to public address 104.153.105.207:27015 via UDP Retrying public(104.153.105.207:27015) ... 19438.340: Sending connect to public address 104.153.105.207:27015 via UDP Retrying public(104.153.105.207:27015) ... 19440.341: Sending connect to public address 104.153.105.207:27015 via UDP Retrying public(104.153.105.207:27015) ... 19442.349: Sending connect to public address 104.153.105.207:27015 via UDP Retrying public(104.153.105.207:27015) ... 19444.355: Sending connect to public address 104.153.105.207:27015 via UDP Retrying public(104.153.105.207:27015) ... 19446.359: Sending connect to public address 104.153.105.207:27015 via UDP Retrying public(104.153.105.207:27015) ... 19448.365: Sending connect to public address 104.153.105.207:27015 via UDP Retrying public(104.153.105.207:27015) ... 19450.367: Sending connect to public address 104.153.105.207:27015 via UDP Retrying public(104.153.105.207:27015) ... 19452.372: Sending connect to public address 104.153.105.207:27015 via UDP Connection failed after 30 retries. ClientModeCSNormal::OnEvent OnEngineDisconnectReason { reason Connection failed after 30 retries. } also if you guys are running the hltv plugin last time I saw that in use is when people used the demo command in console and crashed servers. fyi this is the US bhop server which I guess should be addressed aswell also you guys should list your servers better https://gflclan.com/index.php?app=gflcore anyways the EU server is up and the use of demos does not crash anything so have a blast take care fam <3 Edited July 15, 2018 by rapperdan The best server in GFL better then MilkMans TTT server will ever be Share this post Link to post Share on other sites More sharing options... Achievements 3
Roy 10,832 / 0 Report Post Posted July 15, 2018 @rapperdan We no longer have a CS:GO US BHop server. I have updated the server list as well. Thanks. Share this post Link to post Share on other sites More sharing options...
rapperdan 2,323 / 0 Report Post Posted July 15, 2018 Edited July 15, 2018 by rapperdan 2 minutes ago, Roy said: @rapperdan We no longer have a CS:GO US BHop server. I have updated the server list as well. Thanks. thanks bb wanna smash sometime? nj meet up fam <3 jersey bois unite. Edited July 15, 2018 by rapperdan The best server in GFL better then MilkMans TTT server will ever be Share this post Link to post Share on other sites More sharing options... Achievements 3