[dedsexi]

ok didnt work for nomadtanto, his latency shot back upto 10k almost immediately.

It doesnt make sense how somethings work for some people but not for others, I wonder if this is why funcom are taking so long.

I dont understand why they have enough time and staff to make a post saying they are going to unsticky it but not enough time/staff to let people know whats happening with it or possible causes or solutions.

I wasnt completely sure at first but it seriously is bad customer service, I think even them saying they are stuck on what could be causing it at the moment but are trying to figure it out would be enough for most people. At this point I dont blame people with this issue for cancelling till it is solved.

[dedsexi]

Originally Posted by AndrosHanarak Do I type this just like you just typed it in the command prompt in Vista? Will try this when I get home from work. Just want to be sure.

yeah, just make sure u right click on the CMD icon and choose "run as administrator"

[Bandonroxor]

1. Location: Australia

2. ISP: SpinNet / Comcen

3. Server: Bloodspire

4. What you were doing at the time of the spike: Been like this since release, some days its good, some days it's not. Can be doing anything from buffing to attacking a mob

5. Estimate of the time it happened at: Anywhere between 1 sec to 10 hours of gameplay, also happens at anytime, whether its during the day to peak at night time.

6. How long does it last: Ranges anywhere from 30 secs till... well when I die and give up all hope for the hopeless server

7. Specs of your Computer:

Intel X6950 @ 4.32Ghz
4 GB DDR3
2 x Asus 8800GTS 640MB (Not SLI, just 4 monitors)
Intel DX38BT
Vista Ultimate 64bit

8. Router: Billion BiPAC 7402R2. I have tried it with many different routers though, ranging from Netgear to D-Link

I have also tried the Vista netsh command, but that seems to do nothing. Also redirected all my traffic through my Linux box as I did with WoW, but also does nothing to help the 10000ms+ latency.

As it stands I am begging to think that buying this game was a waste of time and may go back to boxing on WoW.

[lpeditor]

Originally Posted by pdeaudney Lag right now, only in day mode. ADSL 8mbit (Australia). Night mode ping 220ms - 260ms Day mode 330ms - 9999ms PC e4800 2GB DDR2 800 2x 8800GT SLI Vista64 And running "netsh interface tcp set global autotuning=disabled" on the command prompt as administrator has fixed my lag problem in day mode.

I just tried this, but it didn't make any difference for me sadly. What's weird is the problem is erratic. I played the game fine for 3 hours or so when I first installed it. Now I can barely play for longer than 2 or 3 minutes before latency shoots up.

[ataveras]

Originally Posted by Xeldt Unstickying this - adding a link to it in the revised Solutions to Commonly Reported Tech Issues thread.

LOL .... EXCELENT!
FUCOM is Funny!.

30 page post and continue ignoring us.

OMG sorry we scale to the next level of support.
Solutions to Commonly Reported Tech Issues
But without solution. gratz.

[kamutef]

This might be the worst problem i have ever come across in a video game, and Funcom won't even do anything about it.

Just makes me laugh and cry at the same time.

[Hiloxia]

Well I had a good 30 minutes or so to play in Acheron Ruins--as soon as I zoned though . . . (used the teleport to the Inn) . .. . back to 10000ish ms lag. Relogged 5 times. Nothing.

I tried netstat -n in case it gives any diagnostic info:

(Just left the 208. . . . as I think they are FC?

Active Connections

Proto Local Address Foreign Address State


TCP 192.168.1.2:2180 208.82.194.140:7042 FIN_WAIT_2
TCP 192.168.1.2:2367 208.82.194.140:7042 FIN_WAIT_2
TCP 192.168.1.2:3132 208.82.194.140:7042 ESTABLISHED
TCP 192.168.1.2:3133 208.82.194.8:7042 ESTABLISHED
TCP 192.168.1.2:3134 208.82.194.8:7012 ESTABLISHED

Not sure whether this tells us anything?

[Hiloxia]

Okay I am no network whiz, but after closing off AoC:


Active Connections

Proto Local Address Foreign Address State
TCP 192.168.1.2:2180 208.82.194.140:7042 FIN_WAIT_2
TCP 192.168.1.2:2367 208.82.194.140:7042 FIN_WAIT_2


These remain open . . . .?

[Mr4q]

Problem has got worse, it's not happening during early hours...as in right now.

Previously only been happening during the evening.

[pdeaudney]

ok the autuning did make a difference for a while. However now it just went bad again. wtf....