Urgat
Part of the furniture
- Joined
- Dec 29, 2003
- Messages
- 662
Hi
After a number of help form submitions, GOA finally suggested that it was my connection that was causing the FPS drops in ORVR and keep sieges.
this came from me supplying them a tracert...
Tracing route to patcher.war-europe.com [80.12.101.250]
over a maximum of 30 hops:
1 31 ms 35 ms 35 ms 217.47.109.122
2 32 ms 35 ms 35 ms 217.47.109.161
3 30 ms 35 ms 35 ms 217.47.158.174
4 33 ms 35 ms 35 ms 212.140.206.13
5 35 ms 35 ms 35 ms 217.41.173.65
6 30 ms 35 ms 35 ms 217.41.173.114
7 40 ms 35 ms 35 ms 217.41.173.42
8 36 ms 35 ms 35 ms 217.47.204.241
9 38 ms 35 ms 35 ms core1-pos12-1.manchester.ukcore.bt.net (194.72.2.241]
10 52 ms * 46 ms core1-pos0-1-0-0.ilford.ukcore.bt.net [62.6.204.249]
11 42 ms 35 ms 35 ms transit2-gig8/0/0.ilford.ukcore.bt.net [194.74.77.178]
12 43 ms 35 ms 35 ms t2c2-ge14-0-0.uk-ilf.eu.bt.net [166.49.168.121]
13 45 ms 35 ms 35 ms t2c1-p3-2.uk-lon1.eu.bt.net [166.49.164.93]
14 35 ms 35 ms 35 ms t2a4-ge2-0.uk-lon1.eu.bt.net [166.49.135.52]
15 40 ms 35 ms 35 ms 166-49-211-138.eu.bt.net [166.49.211.138]
16 * * * Request timed out.
17 * * * Request timed out.
18 41 ms 47 ms 47 ms 193.253.67.14
19 44 ms 47 ms 47 ms 80.12.101.250
Trace complete.
according to them the issue is the two timeouts, When i asked why i could PVE at 50+ FPS constantly, they said it was becaue the sheer number of players on screen in ORVR puts a strain on the connection, and that doesnt happen in PVE...
WTF?
I was led to believe that only the destination hop matters really, and that the timeouts are probably just routers that are set to reject the packet type that tracert uses...
After a number of help form submitions, GOA finally suggested that it was my connection that was causing the FPS drops in ORVR and keep sieges.
this came from me supplying them a tracert...
Tracing route to patcher.war-europe.com [80.12.101.250]
over a maximum of 30 hops:
1 31 ms 35 ms 35 ms 217.47.109.122
2 32 ms 35 ms 35 ms 217.47.109.161
3 30 ms 35 ms 35 ms 217.47.158.174
4 33 ms 35 ms 35 ms 212.140.206.13
5 35 ms 35 ms 35 ms 217.41.173.65
6 30 ms 35 ms 35 ms 217.41.173.114
7 40 ms 35 ms 35 ms 217.41.173.42
8 36 ms 35 ms 35 ms 217.47.204.241
9 38 ms 35 ms 35 ms core1-pos12-1.manchester.ukcore.bt.net (194.72.2.241]
10 52 ms * 46 ms core1-pos0-1-0-0.ilford.ukcore.bt.net [62.6.204.249]
11 42 ms 35 ms 35 ms transit2-gig8/0/0.ilford.ukcore.bt.net [194.74.77.178]
12 43 ms 35 ms 35 ms t2c2-ge14-0-0.uk-ilf.eu.bt.net [166.49.168.121]
13 45 ms 35 ms 35 ms t2c1-p3-2.uk-lon1.eu.bt.net [166.49.164.93]
14 35 ms 35 ms 35 ms t2a4-ge2-0.uk-lon1.eu.bt.net [166.49.135.52]
15 40 ms 35 ms 35 ms 166-49-211-138.eu.bt.net [166.49.211.138]
16 * * * Request timed out.
17 * * * Request timed out.
18 41 ms 47 ms 47 ms 193.253.67.14
19 44 ms 47 ms 47 ms 80.12.101.250
Trace complete.
according to them the issue is the two timeouts, When i asked why i could PVE at 50+ FPS constantly, they said it was becaue the sheer number of players on screen in ORVR puts a strain on the connection, and that doesnt happen in PVE...
WTF?
I was led to believe that only the destination hop matters really, and that the timeouts are probably just routers that are set to reject the packet type that tracert uses...
