Ping In Arena

[siuolly]

I recently started to try out arena on my KFM and found that its not playable.  Running around the world, the latency on the client.exe for port 10100 is around 85-100 ms.  However, once I enter arena (just in the lobby alone) the latency jumps to 300+ ms.  Anyone experiencing this?  

 

[Marro]

Yes many players are experiencing these Lag-Spikes in arena right now.
NCSoft has to fix this as soon as possible otherwise they will lose a lot of players.
Asked some dudes at my university (~1000 ppl there are playing BnS) at least ~350 of them have the same issue.

 

[Luc9ninee]

Same here, plenty of topics about this but still no answer they are either avoiding it because it's the minority and they are not trying to fix it or they are trying to fix it but aren't saying anything. either way something needs to be said because if this minority quits there will be a big impact on arena queues, and no one likes that. so probably a dead game if they don't fix it in the next month or so. mean while i will be leveling another character to 45 waiting for a fix because i'm stuck in 1800 rating, i can't go above that with 400ms in arena.

[Planetus]

[GreenDestiny]

Have guys tried using a program like Wtfast? I know it used to make a huge difference for me on Aion but I haven't felt the need to try it in this game yet. Often Internet routing to game servers is bad and it has nothing to do with the game itself.

[LittleBritches]

Yes the Arena lag fest is definitely a real issue and it is probably not on your end. Thousands of people have been complaining about it for a long time (since launch practically) and there still hasn't even been word on a fix or acknowledgement. Find a new game, that's what I'm doing until BDO comes out. Although their servers are gonna be in Cali so...fml I'm east coast :( 

[Xyda]

I am also getting 230+ ms in Arenas & Dungeons.

 

I have noticed that during loading screens in the Open World, I will spike to 230+ ms aswell.

[Ninfu]

For me its worked well thought i switched to use WTfast now because having skill lag / small lag caused me not to want this game and im only now doing money and running dungeons.

 

With WTfast atleast for me game works much better and i can get up to 30% improvement thought that what WTfast client tells me so it might be just hocuspocus but game itself feels more playable than before.

 

You can try wtfast for few days or something and it might fix your issue thought its not solution that players have to start using vpn for getting stable connection and spent more money to game.

[kuro1n]

I already tried, it doesn't help since my ping to the server is 20-30.

If you normally have a ping of 100 and in arena 300 then you can possibly reduce the amount of lag you get before but that doesn't scale with the arena problem. So say you can reduce your 100ping to 50ping then the arena will be 250.

[CappyTheOneAndOnly]

This need to be fixed asap, i can't play and find it enjoyable.. you're wasting my time, fun and premium. If you dont plan to fix this soon, i want a refund on my gold pack. With all thoes money you got, you should atleast be able to get people to do prober performance, GET GOOD SERVERS, and actually hire a support team, so you dont get welcomed by a *cricket*ing bot, when you try to report the issue, which puts you through a tons of bullshit, with no fking end or no improvement. Fix your game ncsoft....

[Provision]

I hope they find a fix for it asap, not only is it nearly impossible for me to win in Arena against equal skilled players(FM rely on good ping). It also make my skills go on cooldown while they never triggered. (had moments i press tab, it goes on cd but never triggered tab on the enemy). 

Issue is with the arena servers it seems, I do not experience above things in PvE even with 15+ people around me it all goes fluid. 

 

They should never promote the game for Esport in its current state, we just can't play at our best if the servers aren't stable / accesable. Also had 3x DC today during an arena match and it wasn't on my end.

Sad part is, NCSoft doesn't give any info about it, this really puts me thinking they don't care about communicating with us. They could at least say "we are investigating the issue". But we are left behind without any information.(Reason i also stopped my premium untill they fix those issue, if you want our support at least communicate with us)

[Xyda]

It isn't even listed as a known issue even though they were apparently aware of the problem last week.

 

https://forums.bladeandsoul.com/topic/146085-known-issues-updated-210-500pm-pst

 

It's clearly a issue on their side but I don't think they care enough to deal with it.

 

I think WE ARE *cricket*ED.

[Xyda]

Still waiting for a reponse....

[Jaelan]

I've  had this problem since the beginning too. My ISP was cablevision and uses old copper technology, and yesterday I switched to fibre optic FiOS and it lowered my ping by 7ms all around in EVERY game.. even BnS open world. But the arena still jumps to 250-330ms lol. It's obviously not on my end. I  have a friend who lives in the same area (NY) and he has the same issue. The least NCSoft could do is acknowledge the problem and give us the run-around so it could let us know they're aware of it and a fix might be possible. At this point I've uninstalled the game and I'm beginning to look elsewhere

[siuolly]

All I  am hoping is they come out and say we got your message and will look into it.  They remain silent and this is NOT even an issue on their list.

[Extent]

I have a thread up in General detailing the issue. Post in there if you want to contribute additional information.

 

The confusing part of this is that it occurs in exactly the same fashion in both the US and EU, so there is little chance of the server hardware itself being faulty.

This leads me to believe that there is an issue with the server software.

 

Now, if we have the same software as Korea does, only localized, you'd have to look for a difference between Korean internet infrastructure vs US/EU infrastructure (aside from the obvious geographical differences.) At the same time, it would need to be something consistent across many different ISPs.

 

So far, the only glaring difference I have been able to uncover is the adoption of IPv6.

IPv4 to IPv6 conversions typically do not cause an issue, however the way they handle fragmented packets is different.

IPv6 will not fragment a packet like IPv4 will, but will instead drop anything larger than the MTU altogether.

That could mean that BnS is attempting to send fragmented or oversize packets over what it expects to be IPv4 (and what may be IPv4 locally), but is instead dropping packets when it goes through major ISPs that have converted to IPv6.

This packet loss could appear similarly to in-game latency.

 

Keep in mind, I'm not overly familiar with network tech or protocols.

This is just the only thing I could come up with from my research.

Someone who knows more would have to determine whether this kind of issue would even be possible.
 

I'll most likely post this in the main thread as well if it needs a bump. Someone might be able to give me an answer.

[Jaelan]

I'm not an expert but from the experience I've had with packet loss, it's entirely possible to have a solid ping like 10-20ms but still have packet loss. This means, you're connection to the server is fast, however, if packets are dropping every 10 seconds or so, your inputs, skills or commands to the game won't reach through during that small amount of time the packet loss is experienced, which can be just as frustrating as bad ping. I could be wrong, but that's from my experience

[kuro1n]

2 hours ago, Jaelan said:

I'm not an expert but from the experience I've had with packet loss, it's entirely possible to have a solid ping like 10-20ms but still have packet loss. This means, you're connection to the server is fast, however, if packets are dropping every 10 seconds or so, your inputs, skills or commands to the game won't reach through during that small amount of time the packet loss is experienced, which can be just as frustrating as bad ping. I could be wrong, but that's from my experience

The problem is not packet loss, the problem is that the ping goes up. Why? Noone knows why (well except NCSoft).

[Jaelan]

1 minute ago, kuro1n said:

The problem is not packet loss, the problem is that the ping goes up. Why? Noone knows why (well except NCSoft).

 

I never said it was packet loss. I was explaining to the poster above me that packet loss and high ping might be a different issue based on my experience, which would imply that the issue we're having isn't packet loss due to 250ms spikes in arena.

[Zen023]

Same issue here arena is unplayable 

[kuro1n]

1 hour ago, Jaelan said:

 

I never said it was packet loss. I was explaining to the poster above me that packet loss and high ping might be a different issue based on my experience, which would imply that the issue we're having isn't packet loss due to 250ms spikes in arena.

I'm not having spikes, I am constant 250 ping.

[Jaelan]

2 minutes ago, kuro1n said:

I'm not having spikes, I am constant 250 ping.

Sigh.. Okay, "spike" then not "spikes". Spike from low ping to constant 250 upon entering arena is what i meant

[kuro1n]

Just now, Jaelan said:

Sigh.. Okay, "spike" then not "spikes". Spike from low ping to constant 250 upon entering arena is what i meant

Soooo high ping? :p

This is what spikes looks like, any other use is incorrect:

[Kensho1996]

Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=83ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=83ms TTL=118
Reply from 96.31.33.52: bytes=32 time=106ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=123ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=102ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=97ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=85ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=86ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=85ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=86ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=85ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=89ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=85ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=134ms TTL=118
Reply from 96.31.33.52: bytes=32 time=99ms TTL=118
Reply from 96.31.33.52: bytes=32 time=85ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=92ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=85ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=85ms TTL=118
Reply from 96.31.33.52: bytes=32 time=83ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=83ms TTL=118
Reply from 96.31.33.52: bytes=32 time=87ms TTL=118
Reply from 96.31.33.52: bytes=32 time=83ms TTL=118
Reply from 96.31.33.52: bytes=32 time=85ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=85ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=114ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=85ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
Reply from 96.31.33.52: bytes=32 time=84ms TTL=118
 

there is my ping test .. it stays constant but the speeds .. meh why i have given up

[Xyda]

They didn't mention anything about the issue on their stream. It's sad...