Q: I'm having connection / lag issues - help!?


#102

Are you on a planet/server local to you?


#103

The ping log showed your getting up to 2.5 second pings to that server which will be unplayable.

Reply from 54.88.128.84: bytes=32 time=126ms TTL=46
Reply from 54.88.128.84: bytes=32 time=311ms TTL=46
Reply from 54.88.128.84: bytes=32 time=2510ms TTL=46
Reply from 54.88.128.84: bytes=32 time=129ms TTL=46

and a packet loss
Ping statistics for 54.88.128.84:
Packets: Sent = 187, Received = 186, Lost = 1 (0% loss),

Worth rerunning the test to see if you get similar results.

Are you playing on wifi or a wired connection? Trying wired might help. Also is anything else stressing your connection (streaming etc).

And where are you based? The server is in eastern USA.


#104

Thanks everyone for help :slight_smile:
I found a culprit. It’s vpn client, not running, but just being loaded in background. Seems like it overrides standard network interface with some virtual custom implementation, so it catches traffic even when not connected. Closing it completely fixed everything, works now on Max settings.
Sorry for trouble :slight_smile:


#105

No worries! Glad you’re able to play now!


#106

ho ho ho - enjoy now - and there’s lot to :sunglasses:


#107

I’m experiencing terrible lag when I’m fighting a swarm of cuttletrunks/spitters or when I’m near a huge lava lake. I tested this out. I leave the swarm/lake area, my ping goes to normal. I go back near the swarm/lake, ping shoots up to 8000ms. :sweat_smile:


#108

It’s a secret weapon of high tier creatures. They attack you with lag high ping. :stuck_out_tongue_winking_eye:


#109

My bits as requested by @vdragon :

  1. Longer ping

#110

Your connection should be good enough to play the game smoothly.

Could you:

  1. Start Boundless.
  2. Turn on the debugging information with ‘.’.
  3. Share a screen shot once the first Sanctum portal pops open.
  4. Enter the world and let the game finish downloading all the chunks. (You can see this information on the right of the debugging information.)
  5. Play the game and capture a screen shot once the red connection warning appears.

#111

So I’ve made a discovery and I’m actually struggling to get the Slow Network warning message since realising this!

Lowering Chunk Download Rate makes things worse! As I’ve said previously and @james confirmed above, my connection is definitely fast enough to support boundless, my rubberbanding issue will be due to WiFi packet loss instead of bandwidth.

The issue in lowering Chunk Download Rate is that it drags out the amount of time it takes to download chunks, which leads to a generally increased number of packets (combined with the entity info packets). I’m finding that increasing Chunk Download Rate to Max shortens the amount of time it takes to download chunks drastically, and so the amount of packets flowing consistently back and forth is lowered, leaving more room for entity packets.

The result is less packet loss and less rubberbanding.


#112


#113

Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=71ms TTL=50
Reply from 54.88.128.84: bytes=32 time=52ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=101ms TTL=50
Reply from 54.88.128.84: bytes=32 time=56ms TTL=50
Reply from 54.88.128.84: bytes=32 time=52ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=52ms TTL=50
Reply from 54.88.128.84: bytes=32 time=51ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=69ms TTL=50
Reply from 54.88.128.84: bytes=32 time=76ms TTL=50
Reply from 54.88.128.84: bytes=32 time=52ms TTL=50
Reply from 54.88.128.84: bytes=32 time=50ms TTL=50
Reply from 54.88.128.84: bytes=32 time=52ms TTL=50
Reply from 54.88.128.84: bytes=32 time=54ms TTL=50
Reply from 54.88.128.84: bytes=32 time=80ms TTL=50
Reply from 54.88.128.84: bytes=32 time=89ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=54ms TTL=50
Reply from 54.88.128.84: bytes=32 time=52ms TTL=50
Reply from 54.88.128.84: bytes=32 time=102ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=50ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=50ms TTL=50
Reply from 54.88.128.84: bytes=32 time=50ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=58ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=59ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=50ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=51ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=50ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=47ms TTL=50
Reply from 54.88.128.84: bytes=32 time=51ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=67ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=50ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=58ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=51ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=50ms TTL=50
Reply from 54.88.128.84: bytes=32 time=53ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=51ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=96ms TTL=50
Reply from 54.88.128.84: bytes=32 time=53ms TTL=50
Reply from 54.88.128.84: bytes=32 time=60ms TTL=50
Reply from 54.88.128.84: bytes=32 time=58ms TTL=50
Reply from 54.88.128.84: bytes=32 time=59ms TTL=50
Reply from 54.88.128.84: bytes=32 time=51ms TTL=50
Reply from 54.88.128.84: bytes=32 time=75ms TTL=50
Reply from 54.88.128.84: bytes=32 time=56ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=56ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=93ms TTL=50
Reply from 54.88.128.84: bytes=32 time=50ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=91ms TTL=50
Reply from 54.88.128.84: bytes=32 time=52ms TTL=50
Reply from 54.88.128.84: bytes=32 time=50ms TTL=50
Reply from 54.88.128.84: bytes=32 time=52ms TTL=50
Reply from 54.88.128.84: bytes=32 time=81ms TTL=50
Reply from 54.88.128.84: bytes=32 time=54ms TTL=50
Reply from 54.88.128.84: bytes=32 time=52ms TTL=50
Reply from 54.88.128.84: bytes=32 time=52ms TTL=50
Reply from 54.88.128.84: bytes=32 time=67ms TTL=50
Reply from 54.88.128.84: bytes=32 time=76ms TTL=50
Reply from 54.88.128.84: bytes=32 time=51ms TTL=50
Reply from 54.88.128.84: bytes=32 time=52ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=59ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=54ms TTL=50
Reply from 54.88.128.84: bytes=32 time=104ms TTL=50
Reply from 54.88.128.84: bytes=32 time=50ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=47ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=102ms TTL=50
Reply from 54.88.128.84: bytes=32 time=58ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=55ms TTL=50
Reply from 54.88.128.84: bytes=32 time=55ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=50ms TTL=50
Reply from 54.88.128.84: bytes=32 time=54ms TTL=50
Reply from 54.88.128.84: bytes=32 time=50ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=54ms TTL=50
Reply from 54.88.128.84: bytes=32 time=54ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=76ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=53ms TTL=50
Reply from 54.88.128.84: bytes=32 time=55ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=53ms TTL=50
Reply from 54.88.128.84: bytes=32 time=66ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=50ms TTL=50
Reply from 54.88.128.84: bytes=32 time=49ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=50ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=51ms TTL=50
Reply from 54.88.128.84: bytes=32 time=56ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=50ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=48ms TTL=50
Reply from 54.88.128.84: bytes=32 time=59ms TTL=50
Reply from 54.88.128.84: bytes=32 time=53ms TTL=50


#114

I found that improving connection with wifi router makes a lot of improvement. As a first step I’d recommend trying out wired connection if possible.


#115

I am playing from Singapore (hence I chose Vecna as my server) and I experience alot of rubber banding issues between the times of 4pm-9pm GMT +8 on most days.

I play other MMOs like RIFT, ESO, DAOC, fine most of the time; unless huge seiges happen in DAOC but that is just render lag. And, I play with a cabled connection.


#116

Thanks for the details. We continue to work on the networking performance. Your ping times around the world are pretty high. (Unplayably high to Europe and N. America.)

For these other games can you let us know which servers you connect to?


#117

I play on the N American servers in these games. Pings ranges between 230-330, occasionally I get worse pings but that is when I start feeling the lag. Otherwise, I may not be able to play PvP well with those with lower pings, its still playable most of the time, even during peak hours. PvE is usually no problems at all, rarely rubberband at all. And, I am not considering render lag as latency lag here.

In Boundless I cannot connect to the American or European Servers usually, I can sometimes but most of the times not possible. And when I do I have to live with the rubberbanding.


#118

Hmm, something strange is going on then as the screenshot you shared of the Pings to the different North American Amazon server centres all have pings over 700ms.

What this means is that any message takes over 700ms to communicate even before the Boundless game server processing cost is included.

I’m not really sure why you’re getting 700ms pings to these centres and yet get a ~300ms to other game servers.

Could you re-run the Ping test?


#119

Here is the new screenshot


The pings I mentioned were the pings as reported via ingame tools. I get a similar effect in Boundless as well. At times when I get the red warnings of having slow connections ingame, the debug tool still reports only a maximum ping of around 300+ max. Normally, the tool shows me a min latency of 150+ and a max of 250+.


#120

@james Just wanted to thank you for being so attentive to this issue but I wanted you to know that I understand that sometimes there are things beyound both of our control as in server routing. I appreciate the thought that you’d also like to improve on your codes network performance. But, having said that, I hope that Some problems getting into game is a problem we can both help resolve. :slight_smile:


#121

Here are my screenshots.