ARC Problems NOT Happening to Me...hmmm...

AltmarriLeo - Archosaur

As the title says, I've not had the LAAAGGG issues, and the like with the ARC interface as others have had, but then I'm less than 8Km/5Miles from a major Comcast.net hub, and have Windows 7 Ultimate on an AMD Quad-Core with 8 Gigabytes of memory, and a 2Gig 3d graphics card, all bought for RELATIVELY cheap from a local vendor. Although my system's the middle of what's currently mid-range, as far as desktops are concerned, both cost-of-parts-and-performance-wise, even my old system worked reasonably well with the ARC interface, with little to no problems overall. But that's just what's been going on with me, so it may be other factors that have made ARC a TOTAL PITA for so many of the rest of yous, I dunno...

DEMHEALSMAN - Dreamweaver

1. Lag with internet has nothing to do with your hardware besides your network interface card, which should work pretty fine nowadays.
2. Being close to a HUB still does not ensure a stable connection to a service miles away, it has to connect through multiple hubs, if 1 of them has a problem, lag and/or dc's happen.

It's unlikely that Arc is the cause of the lag, and Sylen is probably going to copy pasta the following to this thread, so i'll hijack that fun from him:

SylenThunder - Sanctuary wrote: »

Originally Posted by SylenThunder - Sanctuary View Post
People hate me for posting this over and over, but damnit, there's just nothing better to say until you bother to provide more information. And seriously, there's a much better chance that the issue is either on your end, or somewhere between you and the servers. Unfortunately, that can't be determined until you give us something to work with.

Common reasons that you can't connect to the servers, experience disconnects, or just have lag in general...

1. You don't have the three .exe files for the client set to run as administrator.
2. You don't have the game directory set as an exception in your antivirus/security software. (Especially with Norton360 or MSE)
3. Your network adapter driver is out of date and needs to be refreshed.
4. Your local area network settings are improperly configured.
5. You have more than one firewall and don't realize it. (Common with some modems.)
6. Your firewall settings are too strict. (Very common withNorton360, ZoneAlarm, and Commodo firewall.)
7. Your router is configured improperly. (Or it's just a cheap router that can't handle the traffic you're putting on it.)
8. you have a bad network cable.
9. You're using a wireless network connection. (Which leads to another huge list of possible issues.)
10. You have a lot of traffic on your local network that is bogging your router/modem down.
11. There's a fault in your router.
12. There's a fault in your modem.
13, You have a bad phone cord plugged into your modem.
14. There's an issue with your house wiring.
15. There's an issue with your outside wiring.
16. A squirrel chewed on your phone/cable line at the pole and it's raining. (I have personally had this happen.)
17. A switch/router at the CO for your ISP is having an issue.
18. One of the many hubs between you and PWI is having an issue. (Most common)
19. There is heavy sunspot activity. (Has happened within the past two years)
20. There's a regional router outage. (This has happened more than a few times. More often occurs with trunk lines crossing large bodies of water)

That's just a few. Sometimes, the easiest fix is something like shutting down your Modem/Router/PC for three minutes and then bringing them back up. Unfortunately, all you've done is complain about having high latency. You haven't done anything that might lead someone who can help you, to be able to help you resolve the issue you're having.
The more details you give, the better I can narrow it down and tell you what the issue is.

At an absolute minimum I would need a copy of a traceroute to the server, and detailed information about how your local network is configured. In some cases, even a published Speccy log.

You don't have to be a tech wiz to provide any of this information either. You just need to be able to click the links I provided and to read and comprehend/follow instructions. I can understand you're frustrated, but sitting and complaining about a connection, without actually ever attempting to fix it, or provide information for those that can help you fix it, it probably one of the stupidest things you can do. If you feel offended by this statement, then you really need to take a closer look at reality.

SylenThunder - Twilight Temple

AltmarriLeo - Archosaur wrote: »

As the title says, I've not had the LAAAGGG issues, and the like with the ARC interface as others have had, but then I'm less than 8Km/5Miles from a major Comcast.net hub, and have Windows 7 Ultimate on an AMD Quad-Core with 8 Gigabytes of memory, and a 2Gig 3d graphics card, all bought for RELATIVELY cheap from a local vendor. Although my system's the middle of what's currently mid-range, as far as desktops are concerned, both cost-of-parts-and-performance-wise, even my old system worked reasonably well with the ARC interface, with little to no problems overall. But that's just what's been going on with me, so it may be other factors that have made ARC a TOTAL PITA for so many of the rest of yous, I dunno...

1. Your system specs are pretty close to mine, and none of that has anything to do with latencey.

2. I've seen people that are fewer than 8 hops from the servers have serious lag issues because of a bad router in the connection stream.

3. I don't give a **** if you've got the ultimate system and a 1GB direct fiber connection in your house. The bad router at that third hop out is going to kill your connection, regardless.
Hell, just last week I had a guy complaining about everything being slow. He's got a 100MB fiber connection. Too bad his wifi connection from his PC to the modem was hitting 286ms on the low side. Solution, quit using Wifi.

4. You want help, provide the requested information.

DEMHEALSMAN - Dreamweaver wrote: »

1. Lag with internet has nothing to do with your hardware besides your network interface card, which should work pretty fine nowadays.
2. Being close to a HUB still does not ensure a stable connection to a service miles away, it has to connect through multiple hubs, if 1 of them has a problem, lag and/or dc's happen.

It's unlikely that Arc is the cause of the lag, and Sylen is probably going to copy pasta the following to this thread, so i'll hijack that fun from him:

Thanks for that, I was probably asleep. =P

Also, agreed that Arc doesn't cause lag. If it does, you should have upgraded your PC 8 years ago, so don't complain about the software.