PDA

View Full Version : No Reset, Lag Issues



Claydough
10-02-2015, 07:12 PM
Why was the reset missed last night?

we are now plagued with lag issues because of it.

(PC,NA)

Crack
10-02-2015, 08:07 PM
Xbox NA is near unplayable as well.

Better have good walking shoes because its almost impossible to get a car to spawn in SV. lol

Cabulos
10-02-2015, 08:23 PM
Our then that was it.
Yesterday I noticed someone talking about not reset
and today I was playing and it was almost impossible, I thought it was my connection, but out of the game was okay just to play was lag, my vehicle very slow to appear
it has already been solved? some information?
somebody else noticed?

Crack
10-02-2015, 08:31 PM
Its possible they are doing rollbacks (account restorations) of the "exploited accounts", and cant be downed for resets during the process...

FistPumper
10-02-2015, 09:03 PM
It was posted by someone earlier today that they deleted a weapon that had been supremed by someone. He paid over a mill for it. So I hope they are rolling them back.

Hexthat
10-03-2015, 08:21 AM
Game is un-playable. I have to hold down trigger for 6-8 seconds before a det charge fires, this morning at 8:18am PDT.

Olaf
10-03-2015, 08:46 AM
Game is un-playable. I have to hold down trigger for 6-8 seconds before a det charge fires, this morning at 8:18am PDT.

Would not surprise me if just the supremes were removed, and any scrip gains from offering arkforge will remain.

Hexthat
10-03-2015, 09:18 AM
TOO much lag. I can't fire weapons for over 5 sec. 100% sure it's not my connection.


Xbox 360 NA hexthat
Defiance character: hexthat
Server: Xbox 360 NA
Location: Fresno, CA
Date format is dd/mm/aa
All times in PDT

Sat 10/03/2015
09:11 AM

Pinging 208.94.26.5 with 32 bytes of data:
Reply from 208.94.26.5: bytes=32 time=61ms TTL=56
Reply from 208.94.26.5: bytes=32 time=51ms TTL=56
Reply from 208.94.26.5: bytes=32 time=51ms TTL=56
Reply from 208.94.26.5: bytes=32 time=51ms TTL=56
Reply from 208.94.26.5: bytes=32 time=51ms TTL=56
Reply from 208.94.26.5: bytes=32 time=51ms TTL=56
Reply from 208.94.26.5: bytes=32 time=51ms TTL=56
Reply from 208.94.26.5: bytes=32 time=52ms TTL=56
Reply from 208.94.26.5: bytes=32 time=51ms TTL=56
Reply from 208.94.26.5: bytes=32 time=51ms TTL=56

Ping statistics for 208.94.26.5:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 61ms, Average = 51ms

Tracing route to 208.94.26.5 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 8 ms 9 ms 96.120.84.61
3 8 ms 8 ms 8 ms 162.151.83.113
4 14 ms 13 ms 13 ms 162.151.40.129
5 18 ms 16 ms 17 ms 68.86.94.165
6 23 ms 22 ms 23 ms 68.86.86.98
7 55 ms 55 ms 51 ms 68.86.85.141
8 52 ms 52 ms 52 ms 68.86.83.110
9 51 ms 52 ms 52 ms 66.208.216.210
10 51 ms 51 ms 51 ms 208.94.26.5

Trace complete.

Tracing route to 208.94.26.5 over a maximum of 30 hops

1 <1 ms <1 ms * 192.168.1.1
2 9 ms 8 ms 9 ms 96.120.84.61
3 9 ms 8 ms 8 ms 162.151.83.113
4 13 ms 13 ms 15 ms 162.151.40.129
5 17 ms 16 ms 16 ms 68.86.94.165
6 22 ms 22 ms 21 ms 68.86.86.98
7 53 ms 55 ms 53 ms 68.86.85.141
8 52 ms 52 ms 53 ms 68.86.83.110
9 51 ms 52 ms 51 ms 66.208.216.210
10 52 ms 51 ms 53 ms 208.94.26.5

Trace complete.

pew pew pew
10-03-2015, 10:43 AM
No lags for me today o.O