Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: Eagleclaw on February 14, 2010, 01:03:40 PM
-
I will enter any of the arenas and this is really weird... here are the options my computer gives me.
1. Fly for a while, lose UDP session and switch to TCP... fly for a few more minutes.... get booted without warning.
2. Immediately lose UDP session, don't switch to TCP and get booted in less than 2 minutes from entering arena.
3. Immediately lose UDP, immediately switch to TCP, stay good for about an hour, get booted w/out warning.
4. Not find Host at all after getting booted so you cannot enter any arena
5. Fly for a while, get booted, no sign or anything, good frame rate, no glitching, no "lost such and such."
Any help would be greatly appreciated. If you would like a DXDIAG output, tell me.
-
First of all, probably should have posted this in technical help.
More than likely they'll want to see a pingplotter. pingplotter.com (http://pingplotter.com) That allows you to save a report and show it here.
You can go to pingtest.net (http://pingtest.net) for a quick check to see if you have any packet loss.
What kind of connection are you using?
-
well, don't shudder, but a wireless one, very reliable connection for most of it's life. Problems only started about 3 months ago and had worked fine before then. Always seems to happen more after updating and rebooting the computer.
-
Try pingtest.net (http://pingtest.net) real quick and see what your packet loss percentage is.
-
Results indicate -13% packet loss
66ms and Jitter is 5 ms. Overall grade: C
-
Repeated test shows -4% packet loss, ping is 67 ms, jitter is 6 ms, overall grade is an A
-
Results indicate -13% packet loss
66ms and Jitter is 5 ms. Overall grade: C
You'll get more help now that you're in Technical Support but 13% packet loss is not good. If you are able, you may want to try to hooking up a hard line between your router and computer and run the test a couple times (right after you loose connection is best). That can help determine if the problem is between you and the router, or something further along.
-
13% loss was only in my first test.
The following had 4% loss, and the next three tests had 0% loss.
-
Yeah, there is going to be fluctuation, I don't know how bad it has to be before AH kicked you out but if you spike up it might.
Now this part I'm not sure about, but AH is going to be sending a lot more information, and that may provide for more chance of packet loss. There is obviously an issue somewhere. Wait till tomorrow morning and hopefully Skuzzy will take a look. I've had a similar issue before and he asked for a pingplotter, but there are certain settings he'll want it on to best read it, hopefully he can help more.
-
Tha kind of packet loss is nuts. You need to run a Ping Plot and see where it is happening and get your ISP involved.
If this is a wireless connection, then all bets are off.
-
do I have to buy pingplotter or what?
-
www.pingplotter.com and they have a free version of their software at the bottom of their downloads page.
-
ty Skuzzy
-
Target Name: www.hitechcreations.com
IP: 70.85.193.18
Date/Time: 2/15/2010 9:22:54 AM to 2/15/2010 9:24:24 AM
1 1 ms N/A 1 ms 0 ms 1 ms 1 ms 1 ms 1 ms [192.168.0.1]
2 12 ms N/A 9 ms 16 ms 10 ms 12 ms 10 ms 16 ms cpe-76-177-124-1.natcky.res.rr.com [76.177.124.1]
3 99 ms N/A 6 ms 10 ms 8 ms 10 ms 9 ms 9 ms ge-0-0-0.vrslky-mx41.natcky.rr.com [65.28.198.217]
4 7 ms N/A 8 ms 10 ms 7 ms 7 ms 10 ms 7 ms ae-11.hdbgky-mx41.natcky.rr.com [65.28.199.109]
5 9 ms N/A 20 ms 9 ms 11 ms 11 ms 10 ms 11 ms ae-1.grtwky-mx41.natcky.rr.com [65.28.198.186]
6 14 ms N/A 15 ms 14 ms 13 ms 13 ms 12 ms 14 ms ae-1.irtnoh-mx41.natall.rr.com [65.28.198.190]
7 14 ms N/A 13 ms 11 ms 14 ms 15 ms 30 ms 15 ms ge-3-0-0.irtnoh-rtr1.natall.rr.com [65.28.198.145]
8 42 ms N/A 40 ms 39 ms 38 ms 39 ms 39 ms 41 ms so-1-1-0-atlaga-rtr1.peakview.rr.com [76.92.94.5]
9 40 ms N/A 39 ms 38 ms 41 ms 39 ms 41 ms 40 ms ge-2-3-0.cr0.atl20.tbone.rr.com [66.109.6.172]
10 35 ms N/A 36 ms 39 ms 37 ms 38 ms 38 ms 53 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
11 42 ms N/A 36 ms 35 ms 36 ms 34 ms 34 ms 38 ms TenGigabitEthernet9-2.ar1.ATL2.gblx.net [64.212.108.69]
12 49 ms N/A 50 ms 50 ms 49 ms 49 ms 51 ms 51 ms The-Planet.TenGigabitEthernet2-3.ar2.HOU1.gblx.net [64.214.196.58]
13 57 ms N/A 58 ms 62 ms 58 ms 57 ms 60 ms 58 ms et5-4.ibr03.dllstx3.theplanet.com [70.87.253.49]
14 58 ms N/A 61 ms 58 ms 60 ms 58 ms 58 ms 58 ms te3-5.dsr01.dllstx3.theplanet.com [70.87.253.86]
15 * N/A * * * * * * [-]
16 82 ms N/A 62 ms 84 ms 79 ms 68 ms 66 ms 59 ms po1.car03.dllstx5.theplanet.c om [70.87.254.18]
17 59 ms N/A 60 ms 58 ms 59 ms 56 ms 60 ms 60 ms 12.c1.5546.static.theplanet.c om [70.85.193.18]
Ping statistics for www.hitechcreations.com
Packets: Sent = 7, Received = 7, Lost = 0 (0.0%)
Round Trip Times: Minimum = 56ms, Maximum = 60ms, Average = 58ms
-
Except that is our WEB server and authentication server. You need to run it to 206.16.60.38 (one of the game servers).
-
Target Name: N/A
IP: 206.16.60.38
Date/Time: 2/15/2010 12:10:01 PM
1 1 ms 1 ms [192.168.0.1]
2 7 ms 9 ms cpe-76-177-124-1.natcky.res.rr.com [76.177.124.1]
3 12 ms 7 ms ge-0-0-0.vrslky-mx41.natcky.rr.com [65.28.198.217]
4 12 ms 14 ms ae-11.hdbgky-mx41.natcky.rr.com [65.28.199.109]
5 11 ms 8 ms ae-1.grtwky-mx41.natcky.rr.com [65.28.198.186]
6 13 ms 12 ms ae-1.irtnoh-mx41.natall.rr.com [65.28.198.190]
7 18 ms 16 ms ge-3-0-0.irtnoh-rtr1.natall.rr.com [65.28.198.145]
8 59 ms 39 ms so-1-1-0-atlaga-rtr1.peakview.rr.com [76.92.94.5]
9 39 ms 44 ms ge-2-3-0.cr0.atl20.tbone.rr.com [66.109.6.172]
10 35 ms 35 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
11 43 ms 35 ms xe-7-2-0.edge4.Atlanta2.Level3.net [4.59.12.33]
12 44 ms 39 ms ae-18-51.car2.Atlanta4.Level3.net [4.68.103.13]
13 58 ms 35 ms [192.205.35.217]
14 73 ms 59 ms cr1.attga.ip.att.net [12.122.82.98]
15 64 ms 60 ms cr2.dlstx.ip.att.net [12.122.28.174]
16 56 ms 54 ms gar23.dlstx.ip.att.net [12.122.138.157]
17 62 ms 63 ms 12-122-254-154.attens.net [12.122.254.154]
18 55 ms 58 ms mdf001c7613r0004-gig-10-1.dal1.attens.net [63.241.193.18]
19 72 ms 55 ms [206.16.60.38]
Ping statistics for 206.16.60.38
Packets: Sent = 2, Received = 2, Lost = 0 (0.0%)
Round Trip Times: Minimum = 55ms, Maximum = 72ms, Average = 63ms
-
That looks pretty good, but you should let it run for a few minutes.
-
Target Name: N/A
IP: 206.16.60.38
Date/Time: 2/15/2010 12:59:02 PM
1 2 ms 1 ms 1 ms 1 ms 1 ms [192.168.0.1]
2 8 ms 7 ms 72 ms 78 ms 14 ms cpe-76-177-124-1.natcky.res.rr.com [76.177.124.1]
3 10 ms 6 ms 139 ms 79 ms 7 ms ge-0-0-0.vrslky-mx41.natcky.rr.com [65.28.198.217]
4 38 ms 10 ms 142 ms 81 ms 6 ms ae-11.hdbgky-mx41.natcky.rr.com [65.28.199.109]
5 12 ms 33 ms 150 ms 84 ms 9 ms ae-1.grtwky-mx41.natcky.rr.com [65.28.198.186]
6 18 ms 13 ms 119 ms 84 ms 11 ms ae-1.irtnoh-mx41.natall.rr.com [65.28.198.190]
7 22 ms 13 ms 169 ms 82 ms 13 ms ge-3-0-0.irtnoh-rtr1.natall.rr.com [65.28.198.145]
8 44 ms 40 ms 141 ms 83 ms 40 ms so-1-1-0-atlaga-rtr1.peakview.rr.com [76.92.94.5]
9 42 ms 71 ms 121 ms 83 ms 39 ms ge-2-3-0.cr0.atl20.tbone.rr.com [66.109.6.172]
10 38 ms 34 ms 91 ms 84 ms 34 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
11 66 ms 35 ms 251 ms 83 ms 36 ms xe-7-2-0.edge4.Atlanta2.Level3.net [4.59.12.33]
12 91 ms 38 ms 220 ms 83 ms 39 ms ae-18-51.car2.Atlanta4.Level3.net [4.68.103.13]
13 74 ms 36 ms 241 ms 84 ms 151 ms [192.205.35.217]
14 89 ms 58 ms 292 ms 131 ms 116 ms cr1.attga.ip.att.net [12.122.82.98]
15 62 ms 83 ms 264 ms 132 ms 119 ms cr2.dlstx.ip.att.net [12.122.28.174]
16 59 ms 64 ms 268 ms 102 ms 121 ms gar23.dlstx.ip.att.net [12.122.138.157]
17 62 ms 59 ms 223 ms 100 ms 123 ms 12-122-254-154.attens.net [12.122.254.154]
18 64 ms 55 ms 258 ms 70 ms 134 ms mdf001c7613r0004-gig-10-1.dal1.attens.net [63.241.193.18]
19 67 ms 101 ms 266 ms 59 ms 134 ms [206.16.60.38]
Ping statistics for 206.16.60.38
Packets: Sent = 5, Received = 5, Lost = 0 (0.0%)
Round Trip Times: Minimum = 59ms, Maximum = 266ms, Average = 125ms
-
Here is one I had running at the time I was booted.
Target Name: N/A
IP: 206.16.60.38
Date/Time: 2/15/2010 2:29:47 PM
1 1 ms 2 ms * 0 ms [192.168.0.1]
2 18 ms 10 ms * 52 ms cpe-76-177-124-1.natcky.res.rr.com [76.177.124.1]
3 16 ms 8 ms * 29 ms ge-0-0-0.vrslky-mx41.natcky.rr.com [65.28.198.217]
4 7 ms 8 ms * 23 ms ae-11.hdbgky-mx41.natcky.rr.com [65.28.199.109]
5 12 ms 11 ms * 12 ms ae-1.grtwky-mx41.natcky.rr.com [65.28.198.186]
6 36 ms 14 ms * 56 ms ae-1.irtnoh-mx41.natall.rr.com [65.28.198.190]
7 12 ms 13 ms * 35 ms ge-3-0-0.irtnoh-rtr1.natall.rr.com [65.28.198.145]
8 45 ms 39 ms * 40 ms so-1-1-0-atlaga-rtr1.peakview.rr.com [76.92.94.5]
9 46 ms 38 ms * 59 ms ge-2-3-0.cr0.atl20.tbone.rr.com [66.109.6.172]
10 34 ms 38 ms * 64 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
11 35 ms 35 ms * 41 ms xe-7-2-0.edge4.Atlanta2.Level3.net [4.59.12.33]
12 43 ms 42 ms * 41 ms ae-18-51.car2.Atlanta4.Level3.net [4.68.103.13]
13 37 ms 37 ms * 144 ms [192.205.35.217]
14 81 ms 57 ms * 93 ms cr1.attga.ip.att.net [12.122.82.98]
15 69 ms 57 ms * 55 ms cr2.dlstx.ip.att.net [12.122.28.174]
16 59 ms 55 ms * 57 ms gar23.dlstx.ip.att.net [12.122.138.157]
17 62 ms 62 ms * 60 ms 12-122-254-154.attens.net [12.122.254.154]
18 63 ms 56 ms * 58 ms mdf001c7613r0004-gig-10-1.dal1.attens.net [63.241.193.18]
19 68 ms 59 ms * 57 ms [206.16.60.38]
Ping statistics for 206.16.60.38
Packets: Sent = 4, Received = 3, Lost = 1 (25.0%)
Round Trip Times: Minimum = 57ms, Maximum = 68ms, Average = 61ms
-
Good, bad or neutral? ^
-
Good, bad or neutral?
Sort of tough to say as these plots have very few packets sent. What you need to do it start pingplot and let it run with no finite amount of pings.
Let it run in the background and fly Aces High. If you then get booted stop the ping plot and use those results.
In other words, you really need a larger sample.
-
Target Name: N/A
IP: 206.16.60.38
Date/Time: 2/15/2010 10:58:14 PM to 2/15/2010 10:59:44 PM
1 2 ms 2 ms 1 ms 1 ms * 1 ms 1 ms [192.168.0.1]
2 10 ms 11 ms 9 ms 9 ms * 36 ms 79 ms cpe-76-177-124-1.natcky.res.rr.com [76.177.124.1]
3 9 ms 10 ms 10 ms 9 ms * 10 ms 52 ms ge-0-0-0.vrslky-mx41.natcky.rr.com [65.28.198.217]
4 11 ms 9 ms 10 ms 10 ms * 32 ms 22 ms ae-11.hdbgky-mx41.natcky.rr.com [65.28.199.109]
5 13 ms 41 ms 10 ms 11 ms * 8 ms 9 ms ae-1.grtwky-mx41.natcky.rr.com [65.28.198.186]
6 15 ms 15 ms 44 ms 13 ms * 28 ms 13 ms ae-1.irtnoh-mx41.natall.rr.com [65.28.198.190]
7 17 ms 13 ms 16 ms 13 ms * 17 ms 13 ms ge-3-0-0.irtnoh-rtr1.natall.rr.com [65.28.198.145]
8 38 ms 39 ms 77 ms 38 ms * 41 ms 41 ms so-1-1-0-atlaga-rtr1.peakview.rr.com [76.92.94.5]
9 40 ms 40 ms 51 ms 40 ms * 39 ms 53 ms ge-2-3-0.cr0.atl20.tbone.rr.com [66.109.6.172]
10 42 ms 37 ms 38 ms 38 ms * 37 ms 34 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
11 35 ms 37 ms 37 ms 39 ms * 34 ms 37 ms xe-7-2-0.edge4.Atlanta2.Level3.net [4.59.12.33]
12 38 ms 41 ms 42 ms 40 ms * 39 ms 51 ms ae-18-51.car2.Atlanta4.Level3.net [4.68.103.13]
13 155 ms 37 ms 35 ms 35 ms * 35 ms 38 ms [192.205.35.213]
14 161 ms 58 ms 62 ms 61 ms * 58 ms 57 ms cr1.attga.ip.att.net [12.122.82.98]
15 160 ms 60 ms 57 ms 62 ms * 98 ms 58 ms cr2.dlstx.ip.att.net [12.122.28.174]
16 148 ms 57 ms 57 ms 59 ms * 68 ms 56 ms gar23.dlstx.ip.att.net [12.122.138.157]
17 121 ms 62 ms 63 ms 61 ms * 61 ms 62 ms 12-122-254-154.attens.net [12.122.254.154]
18 88 ms 57 ms 126 ms 59 ms * 58 ms 56 ms mdf001c7613r0004-gig-10-1.dal1.attens.net [63.241.193.18]
19 70 ms 59 ms 103 ms 57 ms * 62 ms 62 ms [206.16.60.38]
Ping statistics for 206.16.60.38
Packets: Sent = 7, Received = 6, Lost = 1 (14.3%)
Round Trip Times: Minimum = 57ms, Maximum = 103ms, Average = 68ms
I opened Aces high and got booted pretty much immediately with this one.
-
I don't know how long they want you to run this, but the most packets you've sent so far is 7. That other website I referred you too had 250 packets sent.
Run it longer.
-
I am, I just posted this one because I got booted, another one is on the way.
-
Target Name: N/A
IP: 206.16.60.38
Date/Time: 2/15/2010 11:45:07 PM to 2/15/2010 11:47:22 PM
1 1 ms 1 ms 1 ms 1 ms 1 ms 2 ms 1 ms 2 ms 1 ms 2 ms [192.168.0.1]
2 11 ms 9 ms 8 ms 9 ms 8 ms 13 ms 7 ms 9 ms 11 ms 10 ms cpe-76-177-124-1.natcky.res.rr.com [76.177.124.1]
3 9 ms 9 ms 12 ms 6 ms 39 ms 6 ms 7 ms 15 ms 95 ms 7 ms ge-0-0-0.vrslky-mx41.natcky.rr.com [65.28.198.217]
4 7 ms 43 ms 7 ms 41 ms 12 ms 10 ms 8 ms 8 ms 37 ms 8 ms ae-11.hdbgky-mx41.natcky.rr.com [65.28.199.109]
5 10 ms 10 ms 10 ms 9 ms 8 ms 8 ms 9 ms 10 ms 26 ms 12 ms ae-1.grtwky-mx41.natcky.rr.com [65.28.198.186]
6 12 ms 12 ms 12 ms 65 ms 12 ms 13 ms 26 ms 12 ms 13 ms 13 ms ae-1.irtnoh-mx41.natall.rr.com [65.28.198.190]
7 13 ms 16 ms 14 ms 14 ms 15 ms 21 ms 14 ms 13 ms 13 ms 12 ms ge-3-0-0.irtnoh-rtr1.natall.rr.com [65.28.198.145]
8 41 ms 39 ms 39 ms 42 ms 40 ms 39 ms 40 ms 40 ms 41 ms 40 ms so-1-1-0-atlaga-rtr1.peakview.rr.com [76.92.94.5]
9 38 ms 41 ms 40 ms 39 ms 41 ms 42 ms 43 ms 41 ms 40 ms 41 ms ge-2-3-0.cr0.atl20.tbone.rr.com [66.109.6.172]
10 34 ms 70 ms 37 ms 39 ms 41 ms 44 ms 34 ms 91 ms 35 ms 34 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
11 37 ms 40 ms 39 ms 106 ms 80 ms 39 ms 36 ms 39 ms 37 ms 35 ms xe-7-2-0.edge4.Atlanta2.Level3.net [4.59.12.33]
12 38 ms 37 ms 39 ms 41 ms 38 ms 87 ms 39 ms 36 ms 39 ms 42 ms ae-18-51.car2.Atlanta4.Level3.net [4.68.103.13]
13 35 ms 41 ms 35 ms 42 ms 40 ms 41 ms 37 ms 40 ms 39 ms 36 ms [192.205.35.213]
14 60 ms 61 ms 58 ms 55 ms 56 ms 62 ms 59 ms 57 ms 62 ms 86 ms cr1.attga.ip.att.net [12.122.82.98]
15 56 ms 60 ms 56 ms 56 ms 56 ms 63 ms 62 ms 57 ms 56 ms 62 ms cr2.dlstx.ip.att.net [12.122.28.174]
16 55 ms 59 ms 54 ms 59 ms 61 ms 62 ms 56 ms 62 ms 82 ms 56 ms gar23.dlstx.ip.att.net [12.122.138.157]
17 60 ms 57 ms 60 ms 62 ms 56 ms 57 ms 59 ms 59 ms 60 ms 62 ms 12-122-254-154.attens.net [12.122.254.154]
18 60 ms 62 ms 58 ms 59 ms 64 ms 60 ms 74 ms 59 ms 57 ms 56 ms mdf001c7613r0004-gig-10-1.dal1.attens.net [63.241.193.18]
19 58 ms 56 ms 66 ms 60 ms 56 ms 63 ms 68 ms 56 ms 62 ms 61 ms [206.16.60.38]
Ping statistics for 206.16.60.38
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 56ms, Maximum = 68ms, Average = 60ms
-
Not the expert here, but I believe that you can tell pingplotter a certain # samples to include and trace delay. Make the # of samples high and the delay in seconds low. (50 sample; 2.5 second delay)
See how that works.
-
Target Name: N/A
IP: 206.16.60.38
Date/Time: 2/16/2010 9:21:28 AM to 2/16/2010 9:47:46 AM
Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 629 25 4.0 0 1519 10 [192.168.0.1]
2 629 25 4.0 6 1490 28 cpe-76-177-124-1.natcky.res.rr.com [76.177.124.1]
3 629 25 4.0 6 1459 25 ge-0-0-0.vrslky-mx41.natcky.rr.com [65.28.198.217]
4 629 25 4.0 6 1428 27 ae-11.hdbgky-mx41.natcky.rr.com [65.28.199.109]
5 629 25 4.0 7 1396 26 ae-1.grtwky-mx41.natcky.rr.com [65.28.198.186]
6 628 25 4.0 10 1367 31 ae-1.irtnoh-mx41.natall.rr.com [65.28.198.190]
7 628 25 4.0 11 1336 28 ge-3-0-0.irtnoh-rtr1.natall.rr.com [65.28.198.145]
8 628 25 4.0 38 1305 54 so-1-1-0-atlaga-rtr1.peakview.rr.com [76.92.94.5]
9 628 26 4.1 37 1274 54 ge-2-3-0.cr0.atl20.tbone.rr.com [66.109.6.172]
10 628 26 4.1 34 1243 53 ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
11 628 28 4.5 33 1212 53 xe-7-2-0.edge4.Atlanta2.Level3.net [4.59.12.33]
12 628 28 4.5 34 1182 62 ae-18-51.car2.Atlanta4.Level3.net [4.68.103.13]
13 628 33 5.3 34 1151 59 [192.205.35.217]
14 628 28 4.5 54 1120 72 cr1.attga.ip.att.net [12.122.82.98]
15 628 30 4.8 55 1089 72 cr2.dlstx.ip.att.net [12.122.28.174]
16 628 34 5.4 54 1043 72 gar23.dlstx.ip.att.net [12.122.138.157]
17 628 32 5.1 55 1015 74 12-122-254-154.attens.net [12.122.254.154]
18 628 33 5.3 56 984 72 mdf001c7613r0004-gig-10-1.dal1.attens.net [63.241.193.18]
19 628 33 5.3 55 953 69 [206.16.60.38]
Packets sent:10 Packets received: 7 Packets lost: 3 = 30.0%
Sorry if you dont like it but it just wont do any higher than 10 packets, left this running for an hour at least
-
Woah, that is one ugly trace and it all starts right at your computer. Are you running some other network software at the same time? Is this a wireless connection?
-
Unfortunately Skuzzy, yes, it is wireless, no other option. And no other software I know of runs at the same time... Unless you count Winamp, but it is only a tool bar. Aside from that I sometimes have the internet on at the same time but I've mostly always done that.
-
I uninstalled winamp toolbar, never did anything. :noid
-
Problem still persists, can anybody help?
-
We still haven't seen a good set of data:
(http://i666.photobucket.com/albums/vv23/Jayhawk1/Pingplotter.jpg)
That's bottom line, Statistics, needs to be higher than 10. Mine is showing 50, I honestly don't know what a good number is but more than 10.
I don't know what a good trace delay is, maybe someone else can help you there.
Have you tried resetting your router? Odds are that the problem is between your wireless router and your computer.
-
You already got an answer, wireless sucks! Unfortunately there isn't much you can do to help it, or fix it.
Wireless works ok for web browsing and eve some games, but a flight sim style game has a ton of information that has to be update reliably and very often. With planes flying at 350 mph how much space do you think you cover each second? That data has to be run to your computer and back a bunch of times every minute to place each plane. Picture a furball!
Wireless is too restrictive and just can't keep up with the info so you get packet loss which turns into warps. Running a cable isn't that big a deal. Second story, throw it out a window, down the hall only run it out when you fly but run it down the hallway floor.
-
Could it be interference? I mean the problem didn't start for a while and before the problem it worked excellent.
-
it might, but it's always going to be a "hit or miss" kind of thing.
-
It is the nature of the beast. That is just the way it is with wireless connections. Everything, including the Sun, effects wireless connections.
-
Duly noted, thanks guys, my bro is coming by tomorrow to help me try to run a cable <S>