Russian Match Servers Unplayable

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

22:19:02.030 WARNING| client: packet loss last second 5.4%

22:19:02.045 WARNING| client: packet loss last second 6.0%

22:19:02.060 WARNING| client: packet loss last second 6.6%

22:19:02.074 WARNING| client: packet loss last second 7.2%

22:19:02.088 WARNING| client: packet loss last second 10.0%

22:19:02.102 WARNING| client: packet loss last second 10.7%

22:19:02.116 WARNING| client: packet loss last second 11.4%

22:19:02.130 WARNING| client: packet loss last second 12.0%

22:19:02.144 WARNING| client: packet loss last second 12.7%

22:19:02.158 WARNING| client: packet loss last second 13.3%

22:19:02.172 WARNING| client: packet loss last second 14.0%

22:19:02.186 WARNING| client: packet loss last second 16.6%

22:19:02.200 WARNING| client: packet loss last second 17.3%

22:19:02.214 WARNING| client: packet loss last second 17.9%

22:19:02.228 WARNING| client: packet loss last second 19.0%

22:19:02.242 WARNING| client: packet loss last second 19.6%

22:19:02.255 WARNING| client: packet loss last second 20.1%

22:19:02.270 WARNING| client: packet loss last second 21.3%

22:19:02.283 WARNING| client: packet loss last second 24.9%

22:19:02.297 WARNING| client: packet loss last second 25.4%

22:19:02.311 WARNING| client: packet loss last second 26.6%

22:19:02.325 WARNING| client: packet loss last second 27.3%

22:19:02.339 WARNING| client: packet loss last second 27.9%

22:19:02.353 WARNING| client: packet loss last second 28.5%

22:19:02.379 WARNING| client: packet loss last second 29.1%

22:19:02.394 WARNING| client: packet loss last second 37.6%

22:19:02.408 WARNING| client: packet loss last second 38.2%

22:19:02.422 WARNING| client: packet loss last second 38.8%

22:19:02.436 WARNING| client: packet loss last second 39.4%

22:19:02.449 WARNING| client: packet loss last second 40.0%

22:19:02.462 WARNING| client: packet loss last second 40.5%

22:19:02.476 WARNING| client: packet loss last second 41.1%

22:19:02.489 WARNING| client: packet loss last second 50.4%

22:19:02.502 WARNING| client: packet loss last second 51.0%

22:19:02.529 WARNING| client: packet loss last second 51.5%

22:19:02.597 WARNING| client: packet loss last second 71.5%

22:19:02.610 WARNING| client: packet loss last second 72.0%

22:19:02.623 WARNING| client: packet loss last second 72.4%

22:19:02.636 WARNING| client: packet loss last second 72.8%

22:19:02.650 WARNING| client: packet loss last second 73.2%

22:19:02.663 WARNING| client: packet loss last second 73.5%

22:19:02.677 WARNING| client: packet loss last second 74.2%

22:19:02.702 WARNING| client: packet loss last second 74.6%

22:19:02.716 WARNING| client: packet loss last second 100.0%

22:19:03.467 WARNING| client: packet loss last second 38.7%

22:19:03.493 WARNING| client: packet loss last second 38.1%

22:19:03.528 WARNING| client: packet loss last second 37.5%

22:19:03.540 WARNING| client: packet loss last second 36.4%

22:19:03.565 WARNING| client: packet loss last second 35.9%

22:19:03.601 WARNING| client: packet loss last second 35.3%

22:19:03.624 WARNING| client: packet loss last second 35.2%

22:19:03.637 WARNING| client: packet loss last second 33.9%

22:19:03.649 WARNING| client: packet loss last second 33.8%

22:19:03.661 WARNING| client: packet loss last second 33.7%

22:19:03.672 WARNING| client: packet loss last second 33.1%

22:19:03.685 WARNING| client: packet loss last second 33.0%

22:19:03.697 WARNING| client: packet loss last second 32.9%

22:19:03.709 WARNING| client: packet loss last second 32.4%

22:19:03.721 WARNING| client: packet loss last second 32.3%

22:19:03.733 WARNING| client: packet loss last second 32.2%

22:19:03.745 WARNING| client: packet loss last second 30.3%

22:19:03.756 WARNING| client: packet loss last second 30.2%

22:19:03.768 WARNING| client: packet loss last second 30.1%

22:19:03.781 WARNING| client: packet loss last second 29.6%

22:19:03.792 WARNING| client: packet loss last second 29.6%

22:19:03.804 WARNING| client: packet loss last second 29.5%

22:19:03.815 WARNING| client: packet loss last second 29.0%

22:19:03.827 WARNING| client: packet loss last second 28.9%

22:19:03.839 WARNING| client: packet loss last second 28.9%

22:19:03.850 WARNING| client: packet loss last second 26.8%

22:19:03.863 WARNING| client: packet loss last second 26.8%

22:19:03.886 WARNING| client: packet loss last second 26.5%

22:19:03.919 WARNING| client: packet loss last second 26.2%

22:19:03.954 WARNING| client: packet loss last second 24.6%

22:19:03.989 WARNING| client: packet loss last second 24.4%

22:19:04.021 WARNING| client: packet loss last second 24.1%

22:19:04.056 WARNING| client: packet loss last second 23.9%

22:19:04.067 WARNING| client: packet loss last second 22.6%

22:19:04.080 WARNING| client: packet loss last second 22.5%

22:19:04.091 WARNING| client: packet loss last second 22.3%

22:19:04.135 WARNING| client: packet loss last second 22.2%

22:19:04.169 WARNING| client: packet loss last second 21.3%

22:19:04.179 WARNING| client: packet loss last second 21.1%

22:19:04.203 WARNING| client: packet loss last second 21.3%

22:19:04.214 WARNING| client: packet loss last second 21.1%

22:19:04.259 WARNING| client: packet loss last second 21.0%

22:19:04.268 WARNING| client: packet loss last second 20.3%

22:19:04.302 WARNING| client: packet loss last second 20.1%

22:19:04.313 WARNING| client: packet loss last second 19.9%

22:19:04.324 WARNING| client: packet loss last second 19.8%

22:19:04.346 WARNING| client: packet loss last second 19.6%

22:19:04.358 WARNING| client: packet loss last second 19.8%

22:19:04.380 WARNING| client: packet loss last second 19.5%

22:19:04.414 WARNING| client: packet loss last second 19.3%

22:19:04.448 WARNING| client: packet loss last second 19.1%\

 

It been getting progressively worse. I cannot even fly Fighters now as it will wobble as badly as Interceptors. That specific game - couldn’t activate modules, target lock + teleportation issues.

 

You can blame latency all you want but truth is, it’s server performance. I can play fine on US servers with higher ping at upwards of 400ms. But on Russian server with lower ping times - it’s hell.

 

Politely requesting some kind of help with this as I have bought certain ships that cannot be flown whenever matchmaker decides to throw me into certain servers.

[log16aug.txt](< base_url >/applications/core/interface/file/attachment.php?id=6544)

#2

They stated that they are aware of the problem on the russian forums and working on it. I’ve had similar problems with US servers over last two days - can’t even dodge frigate fire while orbiting them because it feels like you’re flying in soup due to lag.

#3

I’ve got packet loss logged for all three servers, but typically it’s the Russian one for me as well.

I don’t play anymore when concurrent match/player numbers are high, it’s no fun.

#4

Just for future reference when someone visits this topic, as the following might be helpful to some users. Note that this post doesn’t necessarily just apply to Star Conflict or this specific user/situation.

 

–

 

Packet Loss is quite different from lag (latency) - and generally speaking (depending on the severity) has a more dramatic impact on your gaming experience.

 

Where latency or lag is the delay between the transmission and receipt of data to and from a server, packet loss indicates the number of packets of data which fail to reach their destination altogether. Latency is expressed in milliseconds and is often referred to as your ‘ping’. Ping is strongly affected by geographic location and the quality of your internet connection, as data needs to travel back and forth from your computer to the server.

 

Packet loss is expressed as a percentage, and (roughly) reflects the percent of data which fails to reach the destination. This can be either incoming or outgoing data, and packet loss can be caused on either side.

 

There are a number of factors which can contribute towards packet loss, but generally speaking this comes down to network connectivity issues somewhere between you and the server, or hardware problems on either end.

 

Packets loss such as Kine is experiencing indicates that there is a problem, either on his end or the server’s end or even somewhere in between. There are a few steps you can perform to help diagnose this.

 

  1. Traceroute

Start-Run, type cmd and hit enter. This opens dos prompt.

 

Type:

 

tracert <IP>

 

(replace <IP> with the IP address of the server you wish to trace)

 

This will show you a visual list of all ‘hops’ between your computer and the server and can identify if there are possible problems anywhere in between. Note that this contains your IP address and location information, so if you intend to paste this information somewhere in public, you might wish to anonymise the first few hops.

 

  1. Pingtest.net

 

This website is great for testing connectivity. Select a server which is geographically close to the server you think you are having issues with (Russia, Moscow - for example)

 

Please be careful not to accidentally click banners - the actual test loads in a Java applet within the page, but there is an advertisement banner right above it.

 

This will test your ping, your packet loss and any jitter on your connection. If you find that you are having issues with multiple servers in that region, then you identified that there is a problem closer to home - rather than with the game server you are playing on.

 

  1. Speedtest.net

 

Similar to the above, except it specifically tests your connection speed. Are you on a 100mbit connection but receiving a speed closer to 10mbit? Time to ring your ISP and do a little shouting :slight_smile:

 

–

 

Note that it is my current understanding that there are some hardware/server issues - though I cannot say so with certainty until I get home and can verify with people who definitely know for sure. The above is more for future reference for users experiencing connectivity issues and wish to diagnose themselves prior to making a post.

#5

Why even bother playing on Russian servers, then?

#6

Just for future reference when someone visits this topic, as the following might be helpful to some users. Note that this post doesn’t necessarily just apply to Star Conflict or this specific user/situation.

 

–

 

Packet Loss is quite different from lag (latency) - and generally speaking (depending on the severity) as a more dramatic impact on your gaming experience.

 

Where latency or lag is the delay between the transmission and receipt of data to and from a server, packet loss indicates the number of packets of data which fail to reach their destination altogether. Latency is expressed in milliseconds and is often referred to as your ‘ping’. Ping is strongly affected by geographic location and the quality of your interest connection, as data needs to travel back and forth from your computer to the server.

 

Packet loss is expressed as a percentage, and (roughly) reflects the percent of data which fails to reach the destination. This can be either incoming or outgoing data, and packet loss can be caused on either side.

 

There are a number of factors which can contribute towards packet loss, but generally speaking this comes down to network connectivity issues somewhere between you and the server, or hardware problems on either end.

 

Packets loss such as Kine is experiencing indicates that there is a problem, either on his end or the server’s end or even somewhere in between. There are a few steps you can perform to help diagnose this.

 

  1. Traceroute

Start-Run, type cmd and hit enter. This opens dos prompt.

 

Type:

 

tracert

 

(replace <IP> with the IP address of the server you wish to trace)

 

This will show you a visual list of all ‘hops’ between your computer and the server and can identify if there are possible problems anywhere in between. Note that this contains your IP address and location information, so if you intend to paste this information somewhere in public, you might wish to anonymise the first few hops.

 

  1. Pingtest.net

 

This website is great for testing connectivity. Select a server which is geographically close to the server you think you are having issues with (Russia, Moscow - for example)

 

Please be careful not to accidentally click banners - the actual test loads in a Java applet within the page, but there is an advertisement banner right above it.

 

This will test your ping, your packet loss and any jitter on your connection. If you find that you are having issues with multiple servers in that region, then you identified that there is a problem closer to home - rather than with the game server you are playing on.

 

  1. Speedtest.net

 

Similar to the above, except it specifically tests your connection speed. Are you on a 100mbit connection but receiving a speed closer to 10mbit? Time to ring your ISP and do a little shouting :slight_smile:

 

–

 

Note that it is my current understanding that there are some hardware/server issues - though I cannot say so with certainty until I get home and can verify with people who definitely know for sure. The above is more for future reference for users experiencing connectivity issues and wish to diagnose themselves prior to making a post.

As an IT Guy … I thank you for your Public Service announcement on the difference between packet loss and latency !!!

#7
  1. When I first reported it day after 0.8.1 someone on the team dusted it off as latency issue

 

  1. I went through the usual connection test: pingplotter, con-test, etc and identified the node before reaching Gaijin’s host as the culprit (100% loss)

 

  1. IP’s changed before and after 0.8.1

 

  1. Read somewhere, can’t remember link saying they upgraded hardware during that time. I believe they changed hosts

 

  1. Prior to that there were ZERO network issues. Server was still in Russia back then

 

  1. After 0.8.1 issues began surfacing

 

  1. post 0.9 packet loss started registering on all other Servers including USA at a lesser extent

 

  1. and most minboggling …

 

Why would network issues affect ship animation ? I’m not an engineer so if someone could explain it…

 

If this was a different game where I had an Orc in the center of my screen instead of a ship and the game lagged

 

A. It would not start dancing around without user input under poor network conditions

B. It would not have trouble moving in the direction I asked it to

C. Other users might have issues identifying exactly where I am

D. Server side prediction will calc hit/miss for us

E. All is well

 

Thing with SCon and me atm is that upon spawning my ship will rotate about a fixed point even without me providing any input whatsoever

 

I initially thought inertia had something to do with it because if I applied forward thrust the wobble would lessen before eventually going away and only came back when I changed vectors. Even adding Collision Compensators that affect turn speeds amplified the wobble.

 

Post 0.9 it’s showing new and more odd behaviours ie. getting worse.

 

I don’t get it.

 

 

[edit]

2 parties could do something about it

 

a. me - contacting ISP or DNS provider and try to move around the problem node

b. Gaijin

 

my ISP dont care enough and all the other free and paid DNS services I can use still goes through that little f’ker

 

hence - me politely asking if Dev could do something about it on their end

and reports from other players who are also saying they’re being affected in someway would compel generosity in this matter.

 

OKhL5yd.png

#8

When I start seeing ships skip back an forth like you hit the reverse and forward button as I am looking through the Sniper Scope…or BETTER yet days of VCR tapes you keep seeing the tape go back and forth to me I take it as I am there are issues on the server.

As I am looking through the Sniper Scope and all of a sudden while I have my sights on a POOR SOUL… next thing I am looking up into SPACE or worse completely turned around. I take it as I am having latency issues.

#9

Packet Loss is quite different from lag (latency) - and generally speaking (depending on the severity) has a more dramatic impact on your gaming experience.

Latency is only one form of lag. From a player’s point of view everything that’s not a smooth gameplay experience is referred to as lag. Packet loss leads to freezes or jerky movement and thus is another source of lag.

 

Why even bother playing on Russian servers, then?

It’s not like we have a choice…