The ongoing rubberbanding effect

jsimpson32 said:
Perhaps 40hz is the sweet spot?
Click to expand...

The difference between 30 and 40 is barely recognizable when playing. Its not worth it. 45 is a mild upgrade. 60+ is where its really seen and as you stated the server can handle it. Client side is a different matter though.
 
I think going to 45hz is a good idea. I didn't even consider it, but we started to hear about more problems a little after the servers switched to 60hz. I'll miss it, but I'm interested to see what happens.
 
jsimpson32 said:
Our servers are all on the same machine. So if there is a connection or machine issue it will be shared equally. The machine is in Chicago. I’m sure Bz is somewhere else.

There is Very little I can see to change on the server side. Again nothing for me to change or adjust in current running state.

All I can suggest is changing all servers to 45hz. I’m guessing your Client connections can’t handle 60hz or even 45hz.

Or back all down to 30hz. You guys goto realize it’s never going to be perfect unless we are all on a private network with the provider server.
Click to expand...

Im offended on behalf of my client. Lol but for real, the BZ server runs at 60Hz....so Im not sure that the issue either
 
Through my own, personal observations the lag is caused by routing issues. As to WHY there are routing issues, is beyond me. It's sometimes even 4-7 steps removed from the server.

Have you tried resetting the entire network stack?

You can put this in a new .bat file and it'll do it for you.
Code: 
@echo off
ipconfig /release
ipconfig /flushdns
nbtstat -R
nbtstat -RR
netsh int ipv4 reset
netsh int ipv6 reset
netsh int ip reset
netsh winsock reset
ipconfig /renew
pause

I, personally, call my batch file "fuckshitup.bat"
 
KarekCat said:
Through my own, personal observations the lag is caused by routing issues. As to WHY there are routing issues, is beyond me. It's sometimes even 4-7 steps removed from the server.

Have you tried resetting the entire network stack?

You can put this in a new .bat file and it'll do it for you.
Code: 
@echo off
ipconfig /release
ipconfig /flushdns
nbtstat -R
nbtstat -RR
netsh int ipv4 reset
netsh int ipv6 reset
netsh int ip reset
netsh winsock reset
ipconfig /renew
pause

I, personally, call my batch file "fuckshitup.bat"
Click to expand...

Would running this batch file help players too?
 
I noticed it after the server went to 60hz and it's the same time when others were complaining of the same thing. Also, recently moved to another city and the effects are still noticeable so I'm pretty sure it's server side and not personal home routers.

One way to see is to switch the server back to the original hz, whatever that was, and see if it's still an issue.
 
It was reduced to 45hz yesterday afternoon. In 2010 this was considered a high tick server but by today's standards it is not. If you are still experiencing beyond yesterday afternoon then its not server side.

I would say that moving to a new city and having a new cable modem and new pathways would be the first culprit I would blame.
 
whitefish21 said:
It was reduced to 45hz yesterday afternoon. In 2010 this was considered a high tick server but by today's standards it is not. If you are still experiencing beyond yesterday afternoon then its not server side.

I would say that moving to a new city and having a new cable modem and new pathways would be the first culprit I would blame.
Click to expand...

I didn't have the issue yesterday.
 
You must log in or register to reply here.

Who has viewed this thread (Total: 1) View details

Who has watched this thread (Total: 12) View details

Top Bottom