Connection issues in Star Conflict (extreme ping and packet losses)

Bug Report Section Launcher, game client and connection issues
#1

Bug report: Connection issues (Game is currently installed on Steam client)

 

Basic info:

Location: Slovenia, Ljubljana

Selected server location: Any region

Time zone: GMT+1

 

Logs:

 

Dxdiag:

 

Connection Tester tool:

 

Logs: (I ran this tool here)

 

 

It happened again: (first connection with the chat was terminated, then network error and unknown version in login screen)

 

Logs:

#2

This is happening with me since yesterday, and thought it’s my internet connection. It’s happening today as well.

#3

This is happening with me since yesterday, and thought it’s my internet connection. It’s happening today as well.

Do this.

#4

Do this.

 

Wait, that thing should be obsolete. It was done in November, meanwhile server’s address could have been changed. 

#5

Ok since I’m having same problems here (packet loss to Eu and Ru server), I’ve done few test and apparently there’s a problem in Eu with international routing (my Isp, Telecom, use “main routes” so when I have a problem it’s more likely a “global” issue).

Bad news: no one can do nothing about it.

Good news: it’s not Sc related and usually when happen like that it will be fixed in a matter of few hours or a couple of days at the worst case scenario. 

#6

If you have new server addresses, you should post them, sgdmitry.

#7

we have a dynamic nature of the servers location. Because of this i cant post ip addresses. 
If you feel laggy, you should pathping you current (or latest) server you’v just played. The IP addres of wich can be found in your latest game.log (the last record that starts with client: connected to )

of the info given, among all the good traces you can find the one wich clearly shows connectivity problems.:

Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Domen-PC.telemach.net [84.52.173.46] 
                                0/ 100 =  0%   |
  1  ---     100/ 100 =100%   100/ 100 =100%  10.51.128.1 
                                0/ 100 =  0%   |
  2  191ms    14/ 100 = 14%    14/ 100 = 14%  cmtsgw-gor.upctelemach.net [213.143.64.129] 
                                0/ 100 =  0%   |
  3    9ms    48/ 100 = 48%    48/ 100 = 48%  185.66.148.10.ipv4.telemach.net [185.66.148.10] 
                                0/ 100 =  0%   |
  4    9ms     0/ 100 =  0%     0/ 100 =  0%  185.66.148.231.ipv4.telemach.net [185.66.148.231] 
                               32/ 100 = 32%   |
  5   12ms    70/ 100 = 70%    38/ 100 = 38%  185.66.148.133.ipv4.telemach.net [185.66.148.133] 
                                0/ 100 =  0%   |
  6   12ms    72/ 100 = 72%    40/ 100 = 40%  185.66.148.217.ipv4.telemach.net [185.66.148.217] 
                                0/ 100 =  0%   |
  7   21ms    61/ 100 = 61%    29/ 100 = 29%  peer-AS31042.sbb.rs [82.117.193.217] 
                                0/ 100 =  0%   |
  8   27ms    32/ 100 = 32%     0/ 100 =  0%  de-cix1.RT.ACT.FKT.DE.retn.net [80.81.192.73] 
                               27/ 100 = 27%   |
  9   64ms    67/ 100 = 67%     8/ 100 =  8%  et730-6.RT.SL.SPB.RU.retn.net [87.245.232.141] 
                                0/ 100 =  0%   |
 10   64ms    68/ 100 = 68%     9/ 100 =  9%  GW-Selectel.retn.net [87.245.250.122] 
                                0/ 100 =  0%   |
 11   83ms    59/ 100 = 59%     0/ 100 =  0%  node11st-ru.star-conflict.com [95.213.156.197] 


Trace complete.

between 4 and 5 ;  8 and 9 hops you can see noticable packet losses on the link between.

As you can see, on the server itself (the last node on the route) and its channel there’re no problems