Edited by MacKerris, 04 April 2013 - 07:30 PM.
Teleporting
#21
Posted 04 April 2013 - 07:30 PM
#22
Posted 05 April 2013 - 02:15 AM
#23
Posted 05 April 2013 - 02:59 AM
#24
Posted 05 April 2013 - 09:59 AM
sometimes everybody moves ...i try to target someone with r..nothing happens..shoot someone...again nothing--> after some time (up to more than two minutes) i teleport somewhere on the map (one time from one base on alpine to the other)...
happens every match
p.s. ping, settings, everything else is still the same... ohh yeah: i can still see when someone get's killed (i suspect i can see the real movement/action, since whenever someone dies on my screen that little notification pops up)
#25
Posted 05 April 2013 - 01:50 PM
Count me in as a victim.
#26
Posted 05 April 2013 - 03:24 PM
#27
Posted 05 April 2013 - 03:33 PM
My traceroute [v0.80]
loki (0.0.0.0) Sat Apr 6 03:33:14 2013
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. 192.168.0.1 0.0% 1059 11.7 14.3 0.9 868.4 62.7
2. 80.90.116.*** 0.0% 1059 15.9 15.8 1.1 867.9 72.5
3. 212.1.241.5 0.1% 1059 19.3 16.6 1.3 830.9 71.5
4. 212.1.239.133 0.0% 1059 4.5 17.1 2.0 807.2 70.0
5. 85.26.162.64 0.0% 1059 15.4 21.3 2.7 834.8 68.7
6. 10.222.241.17 0.0% 1059 64.5 72.9 48.7 1654. 131.8
7. ae3.fra60.ip4.tinet.net 0.0% 1059 76.0 79.6 53.1 1595. 127.7
8. xe-2-1-0.tor10.ip4.tinet.net 25.1% 1059 193.6 214.2 187.8 1537. 103.3
9. internap-gw.ip4.tinet.net 27.8% 1059 165.2 191.7 162.4 1669. 134.9
10. border1.te7-1-bbnet1.tor001.pnap 26.9% 1059 178.9 204.0 177.3 1748. 117.5
11. 70.42.29.65 99.0% 1059 170.3 170.0 162.8 187.9 8.2
12. ???
Huge packetloss is a sure reason for this.
#28
Posted 05 April 2013 - 04:03 PM
PraetorRUS, on 05 April 2013 - 03:33 PM, said:
My traceroute [v0.80]
loki (0.0.0.0) Sat Apr 6 03:33:14 2013
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. 192.168.0.1 0.0% 1059 11.7 14.3 0.9 868.4 62.7
2. 80.90.116.*** 0.0% 1059 15.9 15.8 1.1 867.9 72.5
3. 212.1.241.5 0.1% 1059 19.3 16.6 1.3 830.9 71.5
4. 212.1.239.133 0.0% 1059 4.5 17.1 2.0 807.2 70.0
5. 85.26.162.64 0.0% 1059 15.4 21.3 2.7 834.8 68.7
6. 10.222.241.17 0.0% 1059 64.5 72.9 48.7 1654. 131.8
7. ae3.fra60.ip4.tinet.net 0.0% 1059 76.0 79.6 53.1 1595. 127.7
8. xe-2-1-0.tor10.ip4.tinet.net 25.1% 1059 193.6 214.2 187.8 1537. 103.3
9. internap-gw.ip4.tinet.net 27.8% 1059 165.2 191.7 162.4 1669. 134.9
10. border1.te7-1-bbnet1.tor001.pnap 26.9% 1059 178.9 204.0 177.3 1748. 117.5
11. 70.42.29.65 99.0% 1059 170.3 170.0 162.8 187.9 8.2
12. ???
Huge packetloss is a sure reason for this.
Could you please tell me how you did that? I know how to do a trace route. But I do not know how to measure the level of packet loss at various points along the way. Thank you
#29
Posted 05 April 2013 - 04:16 PM
up until approx 2 hours ago everything was fine. i was playing some games with my buddy and everything was nice and fluffy. then suddenly the client seemed to have problems, updating the mechs status at the mech bay, when starting a new match it took me 20 more seconds to start up my mech (animation, everyone was running around at this point, just me stiull starting up my mech) and horrendously bad rubberbanding and warping occured.
it went from just fine to unplayable within one match. i shut down mwo and started a speed and ping test, everything is just fine and as it should be. skype wasnt laggy at all, streaming works as it shouldm, just mwo is laggy as hell.
my average ping under normal conditions ist abot 110 to 120, very stable. now it ranges from 140 to 200 and up.
again, it did not happen to me from one patch (hotfix) to the other. it went from one game to the other in the middle of the fight.
very odd.
#30
Posted 05 April 2013 - 04:18 PM
#31
Posted 05 April 2013 - 04:27 PM
#32
Posted 05 April 2013 - 10:31 PM
and zero, on 05 April 2013 - 04:03 PM, said:
Could you please tell me how you did that? I know how to do a trace route. But I do not know how to measure the level of packet loss at various points along the way. Thank you
It's an output of 'mtr' program for linux.
For windows you can use default command line program 'pathping' (win7+, not sure about vista) for similar results. Just wait for the final output (it can take some minutes).
#33
Posted 06 April 2013 - 01:43 AM
#34
Posted 06 April 2013 - 08:30 AM
Also had several crashes right as i loaded into game with the error "Unexpected file size of 128 from a 0 byte file".
Also have serious delay on fireing my weapons, i aim, fire, and have to sit there and wait while holding my reticle over where i want the shot to go until it fires 2-5 seconds later.
I'm in NY, USA and i have 0 internet issues with any other game i play, it is only MWO.
#35
Posted 06 April 2013 - 09:05 AM
#36
Posted 06 April 2013 - 09:45 AM
new card is 650 ti boost with 2 gig ram
windows 7 OS 64 bit
3.1 ghz core I 3 second generation
10 gig ram ddr 3
ssd hard drive kingston with sata 6gbs connection to mother board
MSI motherboard
I am not sure why the first ten games were awesome. I was not indestructible in those games I was simply able to use terrain and fast speed to dart in out combat confusing the enemy.
Additionally I am seeing people who do not miss ever on the battlefield that needs to be looked into and fixed as well.
#37
Posted 06 April 2013 - 10:52 AM
#38
Posted 06 April 2013 - 04:32 PM
But the game is basically unplayable right now, though yesterday I was fine.
I suppose it could be server load at my ISP being a weekend and all, but seeing as others have been haveing the same issue at different times of the day, I'd say something else is going on
#39
Posted 06 April 2013 - 05:35 PM
#40
Posted 06 April 2013 - 06:59 PM
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users

























