Jump to content

Lags


Sebast1an

Recommended Posts

Heyo,

recently on ETL1 my ping has been 70-90 whereas normally it used to be 50-60. On top of this some maps just lag more than before - I've noticed it quite well on Erdenberg as that map lags a lot these days compared to before (lag as in spikes in lagometer, fps is usually fine). On my end nothing has changed in the last year so I guess this could be related to server setting changes somehow? I tried ETL2 and ETLC, with bots, and on both servers my ping was 48.

Only server change I can recall that could have an effect is /rate was forced to 35000 instead of 25000 some time ago. Not sure if it could have this kind of effect though. I've tried all sort of tweaks to my cfg without much success but I hope some of you may have some new suggestions to try. :) Cheers.

I'm rocking a whopping 24/1 Mbps connection which hasn't changed in a while. Let me know if you need to know some other specs. Also here's my config:

Spoiler

bind mouse4 kill
bind SPACE "+moveup; forcetapout"

seta sensitivity "1.04"
seta rate "45000"
seta com_maxfps "125"
seta snaps "20"
seta cl_packetdup "1"

seta cl_maxpackets "125"
 
seta com_hunkMegs "256"
seta com_zonemegs "64"
seta com_soundmegs "32"

seta r_ignorehwgamma                 "1"
seta cg_centertime                "1"
seta cg_crosshairhealth             "0"
seta cg_crosshaircoloralt             "red"
seta cg_crosshaircolor                 "cyan"
seta cg_crosshairsize                 "55"         
seta cg_crosshairpulse                 "0"
seta cg_crosshairalphaalt             "1.0"
seta cg_crosshairalpha                 "1.0"
seta cg_crosshairy                 "0"
seta cg_crosshairx                 "0"
seta cg_drawcrosshairhealth             "1"  
seta cg_drawcrosshairpickups             "1"
seta cg_drawcrosshairnames             "1"
seta cg_drawcrosshair                 "5"
seta cg_drawCrosshairNames                      "1001"
seta cg_drawCrosshairPickups                     "1"
seta cg_crosshairPulse                          "0"

seta m_filter "0"        //mouse smoothing off
seta cl_mouseAccel "0"        //mouse acceleration off

seta r_displayrefresh "0"
seta r_roundimagesdown "1"
seta r_fullbright "0"
seta pmove_fixed "1"
set r_intensity "1"
seta r_subdivisions "100"                   
seta r_lodbias "0"                          
seta r_colorbits "0"                         
seta r_depthbits "0"                         
seta r_picmip "0"    
seta r_picmip2     "0"                //texture quality - 0 is highest, 3 is lowest                       
seta r_mode "-1"                              
seta r_texturebits "1"                       
seta r_ext_compressed_textures "0"           
seta r_dynamiclight "0"                      
seta r_fastSky "0"                          
seta r_inGameVideo "0"                       
seta r_texturemode GL_LINEAR_MIPMAP_LINEAR  
seta r_detailtextures "0"                    
seta r_flares "0"                            
seta r_finish "0"                            
seta r_ignoreFastPath "0"                   
seta r_lodCurveError "0"                   
seta r_primitives "2"                       
seta r_swapInterval "0"                      
seta r_vertexLight "0"                      
seta r_overBrightBits "0.9"                   
seta r_mapoverbrightbits "3"                 
seta r_gamma "2.5"                          
seta r_subdivisions "1"        
seta r_customwidth "1920"
seta r_customheight "1080"   
seta r_ext_texture_filter_anisotropic     "8"                //sharpness of tilted textures - high
seta r_ext_multisample            "4"                //anti-aliasing - max        
seta ui_r_subdivisions "1"
seta ui_r_lodbias "0"  
seta ui_r_colorbits "32"
seta ui_r_depthbits "24"
seta ui_r_picmip "0"
seta ui_r_mode "6"
seta ui_r_texturebits "32"
seta ui_r_ext_compressed_textures "0"
seta ui_r_dynamiclight "0"
seta ui_r_texturemode GL_LINEAR_MIPMAP_LINEAR
seta ui_r_detailtextures "1"
seta cg_atmosphericEffects "0"   
seta cg_visualEffects        "0"         //toggles black smoke, airplanes, impact sparks and debris           
seta cg_simpleItems "0"                      
seta cg_shadows "0"                          
seta cg_brassTime "0"                        
seta cg_hudAlpha "2.0"                       
seta cg_wolfparticles "0"                   
seta cg_gibs "0"                            
seta cg_shadows "0"                         
seta cg_marktime "0"                        
seta cg_coronas "0"                          
seta cg_coronafardist "0"                    
seta cg_showblood "0"                       
seta cg_bloodDamageBlend "0"               
seta cg_bloodFlash "0"                       
seta cg_bloodTime "0"
seta cg_blinktime "0"        //blackout effect when taking damage?                      
seta cg_drawWeaponIconFlash "1"              
seta cg_drawGun "1"                          
seta cg_drawfps "1"                         
seta b_muzzleflash "0"
seta cg_weaponcycledelay "0"
seta cg_autoaction "0"
seta cg_drawtime "0"
seta cg_tracers "3"        //only see the bullet tracers of other players!
seta cl_activatelean "0"        //No leaning when trying to move around while holding down the activate key

seta cg_predictItems "1"
seta g_antilag "1"

seta cl_wwwDownload "1"

seta cl_allowDownload "1"

seta s_khz "44"  
seta s_doppler            "1"
seta s_separation        "0.5"
seta s_musicvolume        "0"
seta s_wavonly            "1"
seta s_defaultsound        "0.1"
seta s_mixPreStep        "0.05"
seta s_mixahead            "0.2"         

bind "f1" "vote yes"
bind "f2" "vote no"
bind "f3" "ready"

seta cg_bobroll "0.000"    
seta cg_bobpitch "0.000"   
seta cg_bobup "0.000"     
seta cg_runroll "0.000"    
seta cg_runpitch "0.000"   
seta cg_autoReload "0"
seta cl_doubletapDelay "0"
seta com_introplayed "0"
seta cg_bobbing 0

seta m_side                                     "0.25"
seta m_yaw                                      "0.020"
seta m_forward                                  "0.25"

vid_restart

 

Edited by Sebast1an
Added the cl_maxpackets value that was missing from the cfg for some reason
Link to comment
Share on other sites

  • Founders
9 hours ago, Sebast1an said:

Thank you Mini, I think it's a good idea to try regardless just so we know it's not about that.

Just tested it on ETL1 with bots, thinking it might have something to do with the amount of people. But unfortunately that makes no difference.

I am on nights until wed will try it then.

Link to comment
Share on other sites

8 hours ago, Zyxpix said:

This is a routing problem I think and you should contact your ISP

ETLegacy main is in France

ETLegacy 2 is in Germany

A routing problem sounds very logical to me, thank you. I did tracert on both ETL1 and ETL2 and these were the results:

ETL1:

tracert  37.187.79.49

Tracing route to ns3367630.ip-37-187-79.eu [37.187.79.49]
over a maximum of 30 hops:

  1     6 ms     5 ms     5 ms  *myipremoved*
  2     *        8 ms     7 ms  141.208.186.161
  3     8 ms     9 ms     8 ms  141.208.186.162
  4     8 ms     8 ms     9 ms  141.208.186.163
  5    11 ms    10 ms    10 ms  141.208.195.149
  6    12 ms    11 ms    11 ms  62.115.143.50
  7     *        *        *     Request timed out.
  8    37 ms    37 ms    38 ms  ffm-bb1-link.ip.twelve99.net [62.115.143.29]
  9    38 ms    38 ms    37 ms  ffm-b11-link.ip.twelve99.net [62.115.124.117]
 10    40 ms    40 ms    41 ms  be100-163.fra-5-a9.de.eu [178.33.100.250]
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14    52 ms    52 ms    51 ms  be105.gra-g2-nc5.fr.eu [91.121.131.18]
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18    53 ms    53 ms    52 ms  ns3367630.ip-37-187-79.eu [37.187.79.49]

Trace complete.

 

ETL2:

tracert 46.4.80.110

Tracing route to static.110.80.4.46.clients.your-server.de [46.4.80.110]
over a maximum of 30 hops:

  1     6 ms     5 ms     5 ms  *myipremoved*
  2     8 ms     7 ms     7 ms  141.208.186.161
  3     8 ms     7 ms     8 ms  141.208.186.162
  4     8 ms     8 ms     8 ms  141.208.186.163
  5     *       11 ms    11 ms  141.208.195.149
  6    11 ms    11 ms    11 ms  62.115.143.50
  7    37 ms    38 ms    38 ms  s-bb2-link.ip.twelve99.net [62.115.123.202]
  8    36 ms    35 ms    36 ms  ffm-bb2-link.ip.twelve99.net [62.115.138.105]
  9    38 ms    38 ms    37 ms  ffm-b5-link.ip.twelve99.net [62.115.114.91]
 10    47 ms    42 ms    42 ms  hetzner-ic326013-ffm-b5.ip.twelve99-cust.net [213.248.70.3]
 11   193 ms     *       47 ms  core23.fsn1.hetzner.com [213.239.224.249]
 12    43 ms    43 ms    45 ms  ex9k1.dc5.fsn1.hetzner.com [213.239.229.122]
 13    43 ms    43 ms    44 ms  static.110.80.4.46.clients.your-server.de [46.4.80.110]

Trace complete.

 

Could those "request timed out" messages on ETL1 be the cause of the problem?

Link to comment
Share on other sites

On 9/5/2021 at 5:20 PM, Sebast1an said:

Could those "request timed out" messages on ETL1 be the cause of the problem?

No, I have the same thing :

Détermination de l’itinéraire vers ns3367630.ip-37-187-79.eu [37.187.79.49]
avec un maximum de 30 sauts :

  1    <1 ms    <1 ms    <1 ms  mymodem [192.168.1.1]
  2     5 ms     5 ms     5 ms  10.24.1.51
  3     *        *        *     Délai d’attente de la demande dépassé.
  4     5 ms     5 ms     5 ms  ae-60-100.ibrstr5.isp.proximus.be [91.183.241.168]
  5     *        *        5 ms  lag-30-1000.ibrmar5.isp.proximus.be [91.183.246.125]
  6     *        *        *     Délai d’attente de la demande dépassé.
  7     *        *        *     Délai d’attente de la demande dépassé.
  8     *        *        *     Délai d’attente de la demande dépassé.
  9     *        *        *     Délai d’attente de la demande dépassé.
 10     *        *        *     Délai d’attente de la demande dépassé.
 11     *        *        *     Délai d’attente de la demande dépassé.
 12     9 ms     8 ms     8 ms  ns3367630.ip-37-187-79.eu [37.187.79.49]

Itinéraire déterminé.

It just means that ICMP request are blocked, nothing more.

Link to comment
Share on other sites

On 9/5/2021 at 4:20 PM, Sebast1an said:

37 ms    37 ms    38 ms  ffm-bb1-link.ip.twelve99.net [62.115.143.29]

So, yeah, it looks like your problems start when you hit Telia's network. This doesn't surprise me, I've had issues in my work with them and they are singularly unhelpful.

 

On 9/5/2021 at 4:20 PM, Sebast1an said:

10    47 ms    42 ms    42 ms  hetzner-ic326013-ffm-b5.ip.twelve99-cust.net [213.248.70.3]
 11   193 ms     *       47 ms  core23.fsn1.hetzner.com [213.239.224.249]

This might be a blip or a problem peering between Telia (backbone) and Hetzner (the host). Given that you get +20ms to both servers when you hit Telia too, I would say that Telia is having peering problems.

As an end user there's very little you can do, just let your ISP know that there seem to be issues with Telia.

 

 

Link to comment
Share on other sites

On 9/5/2021 at 4:10 AM, Sebast1an said:

On top of this some maps just lag more than before - I've noticed it quite well on Erdenberg as that map lags a lot these days compared to before (lag as in spikes in lagometer, fps is usually fine)

Some maps lag way worse than others from my experience and Erdenberg is absolutely the worst culprit. It's impossible for me to get a stable 200ms ping there. I have also noticed that the latency spikes are aggravated the more players there are. My theory has been that it's due to two things:

1. Bandwidth bottleneck somewhere in the network path. Bandwidth saturation produces knock-on effects like elevated or unstable latencies.
2. Map geometry is not well sectioned (or has leaks) so you end up with far more server traffic than necessary to update invisible players.

(2) is maybe testable by recording a demo and playing back using r_showNormals 1.

From the EU, network bottlenecks really shouldn't be a problem. To check this, you could maybe run Speedtest (https://www.speedtest.net/) from your computer and picking the ISP the main ETL1 server is on.

One misconception behind network issues is that the problem lies on one end or the other i.e. the ISP or the game server in this case. In reality, it very much depends on the routing between the two endpoints and the problematic node on the path could belong to an intermediary.

As far as client tweaks is concerned, there is the setting of packet duplication to off (cl_packetDup 0), reducing snaps, reducing rate and reducing cl_maxPackets. Except for cl_packetDup, the ETL1 server is unfortunately too restrictive for any of the above to work. I have always wondered if it would be better to set a range of acceptable snap and rate values rather than fixing it to 40 and 35000 respectively.

On a sidenote: regarding traceroutes (or tracert on Windows), you have to be careful with interpretation.

1. Most service providers will ask you to provide traces in both directions because the forward and reverse paths may not be the same.

2. It is alright for intermediate nodes to not respond to traces. Pings and Traceroutes use a different protocol (ICMP) and are considered 'control traffic' instead of 'data traffic' and switches/routers prioritize forwarding data. The right way to interpret Traceroute results is to look at the trace in reverse, beginning from the destination. Note down the latency and losses, then work backwards to the earlier nodes to observe the progression.

Edited by StiffWrists
Fix mistakes
  • Like 1
Link to comment
Share on other sites

I increased all those megs too, problems persisted. I did notice that ET is using much more resources than it used to. Not that this should be a problem in 2021. My wooden computer however is actually starting to have issues running the game. :biggrin:

Link to comment
Share on other sites

On 9/14/2021 at 2:13 PM, lost said:

For me on non standard map like enderberg the problem was with com_hunkmegs and com_soundmegs, values were to low, when i adjusted them everything started to working perfect

Which values do you use for hunkmegs, soundmegs and zonemegs?

Link to comment
Share on other sites

I'm basically right about something wrong with Erdenberg. Every area is 'visible' no matter where you are. In the screenshots attached, you can see that both radars are drawn despite how far and how obscured they are from the Allied first spawn. Data for practically every player in the map will be transmitted no matter where they are, generating a lot of unnecessary traffic.

Compare it with Supply Depot, where most of the hidden areas are dropped from processing.

Is there an updated version of this map that fixes this issue?

2021-09-17-022005-erdenberg_t1.jpg

2021-09-17-022516-supply.jpg

Link to comment
Share on other sites

  • 2 weeks later...

Hello

From yesterday something strange happened on the main server. I had all the time ping around 50 and right now periodically it is jumping to about 80 and lowering again to 50. This is not problem with my connection because I checked it. I checked if this happening on the other server and i dont have any problem on other servers from TM. It does not depend on the number of players. It is happening all the time right now. Can someone restart server or something?

  • Haha 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...