Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 37
  1. #21
    You said your server NetServermaxTickrate=30 and the default=20. My question is why is the default set to 20? Kinda too low. I think you can bring it up a bit without causing issues to other players. PT ProTheory server is using 45.45 with 45.00 default. But that's only a 1v1 server. Tribal Ti uses a low 39.87 with 40.00 default. Seems like anything under 40.00 causes a dragging slow feel. Combowhore on the other hand has alot of people playing and they use 44.84 with 45 max. No wonder everyone plays good there because it feels more fluid and smooth. A well known Euro server called UTzone.de uses 44.85 with 45.00 max. What im saying is that most of these good servers set their tickrate in the average of 44/45.00. You said you set it to 50 which is too high. So maybe you should test 43/44.00....it might be a better balanced server tickrate in comparison to others. In the end of the day you will do what you want. But i've checked these other servers and i can tell that anything under 40.00 will drag you slow in movement. Testing it in 1 map not gonna kill anyone...

  2. #22
    As Born pointed out a lot has to do with distance to the server and the route your little packets take back and forth from it. When I moved from Detroit to Minnesota I thought perhaps my ping/ latency, and gameplay in general would improve because I was moving closer to the servers. That definitely was not the case as I found out my connection takes a more convoluted route through some crappier nodes. As for server differences, compared to our server, the Ti server feels painfully lethargic and slow. Movement is dulled, and shots always seemed delayed. I much prefer our servers even with all of the problems caused by the inept server admins we have running this joint (j/k Min!...Don't buy me a new computer!). So play the game, support the HTM servers, and have fun. Isn't that why we're all here?
    There are two rules in life:

    1.) Never give out all the information.

  3. #23
    Quote Originally Posted by DesTineD View Post
    You said your server NetServermaxTickrate=30 and the default=20. My question is why is the default set to 20? Kinda too low.
    Destined, the servers are at tickrate=30. Default is what a brand new UT2004 server has when you start it up, we inept admins call that "default" because ..... well if you don't know what default means I can't help you there.

    I have tested tickrates from 20 to 75 many many times. There are varying member connections and we have 14 man servers that fill up often. 30 was the best balance I could find. We already have issues some nights with the tickrate set at 30 and a full server, 40 would have everyone warping around the map.

    There is also more to do with the game feel than just tickrate, tickrate fools you into thinking you have a lower ping and it helps you hit because it gives you additional data so you can hit the player easier. Like I said "high tickrate = no skillz". Play with your netspeed, it will help you far more than me touching the tickrate.

    Run a tracert and see if you have any bad hops in your connection. You do know you are connecting to a server in Dallas right?

  4. #24
    Also keep in mind that higher your video frame rate, the more false artifacts you may see, meaning if you client video frame rate is way above the "realistic" update rate, then you will see more "unreg's" and other weird stuff because your UT client is showing you more frames of possibly bad data.

    Some of this goes back to previous conversations that folks just can't seem to accept... The game is taking place on the SERVER NOT YOUR PC. Your PC is showing you *PREDICTIONS* based on data that is 100-500ms old. You do not see the opponent LIVE, you see them 1/4 to 1/2 a second in the past. Tick rate will affect the update rate, but will enhance the advantage of low vs high ping. Minion is right on about tick rate overall.

    Contrary to what many think, high tick rate does not affect your actual ping, it effects the servers' CALCULATED ping, which as I said before may not be the real Internet ping.

    Another piece to this is overall Internet latency which has been increasing for about 1-2 years now steadily. The Internet is overtaxed with streaming video and things will only get worse. If someone has a real problem with fluctuating ping, you better get used to it, or go back to playing board games on family game night.

    If I'm playing and anyone wants a reverse tracert, from the server to you to look for bad hops, I will do so, just ask. I did it for timbo and foo last night and found that had a common bad hop internal to comcast, nothing to do with the server or COLO, adding 23ms to the return trip.


    -Born
    Last edited by Born; 5 Days Ago at 10:06 PM.

  5. #25
    Now, changing the game speed a little might be worth a an experiment, 1 to 1.05 maybe... But it would alter the timing of the whole thing, a little speedier...

    -Born

  6. #26
    can you run a tracert to me too?

  7. #27
    Quote Originally Posted by Born View Post
    Now, changing the game speed a little might be worth a an experiment, 1 to 1.05 maybe... But it would alter the timing of the whole thing, a little speedier...

    -Born
    I used to run the server at 125% when we first began. I like faster game speed, we can give it a try.


    Quote Originally Posted by DesTineD View Post
    can you run a tracert to me too?
    I will need your IP address, but yes I can run a tracert from the server to you.

  8. #28
    Destined,

    This is the difference between a server with a tickrate=20 and a server with tickrate=40. As I was saying before the server sends more data (player positions) as the tickrate increases. But because we have so many players on our server the additional data load going from each client to the server and back causes lag and "warping" because the server connection gets overloaded as do clients with limited connections. A higher tickrate is great for a 1v1 server, but not 7v7.


  9. #29
    ok PM the ip to you.

  10. #30
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.


    C:\Users\XXXXXXXX>tracert 108.29.49.187


    Tracing route to 108.29.49.187 over a maximum of 30 hops


    1 2 ms <1 ms <1 ms 72.249.10.33
    2 <1 ms <1 ms <1 ms 206.123.64.21
    3 <1 ms <1 ms <1 ms 8.9.232.73
    4 18 ms <1 ms <1 ms Verizon-level3-2x10g.dallas3.level3.net [4.68.62
    .166]
    5 41 ms 41 ms 41 ms ae203-0.NYCMNY-VFTTP-335.verizon-gni.net [130.81
    .218.185]
    6 42 ms 43 ms 41 ms pool-108-29-49-187.nycmny.fios.verizon.net [108.
    29.49.187]


    Trace complete.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •