2 replies to this topic

[Rexxxxxxxxx]

Hi,

Still getting dropped back to mechlab during the middle of a match after about 7 or so minutes.
The error is related to a malformed packet.

I read about a solution in a cryengine group.

[color=#404040]"Problem solved![/color]
[color=#404040]I just added Script.SetTimer(250,function()[/color]
[color=#404040]to SpawnVehicleForForPlayer func [/color]"

Bottom of this page

https://www.cryengin...p?f=283&t=98771

Is it possible to implement this?

Thanks,
Rexxxxxxxxx

[Tarl Cabot]

I know that this at least your second thread, with the other one from June 2018. Majority of the malformed packet issues are from 2013. I don't hjave anything else to add.


https://mwomercs.com...ng-a-game-drop/

https://mwomercs.com...ost__p__2366169

StandingCow' on May 21, 2013 said:

Yea, I work for my ISP actually, and have examined my connection a few times, and could find no fault (modem levels are acceptable). I'm actually a network engineer myself, lol.

What makes this so difficult to troubleshoot is it is sporadic... but as I mentioned earlier in the thread... when I connect through my VPN, I have yet to have the issue happen, which makes me think it's something along the path... I will try setting up a constant ping to the last hop next time I play and hope the issue shows up.

IP from MWO system file: 70.42.29.74
Tracing route to 70.42.29.74 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 27 ms 21 ms 13 ms c-68-44-240-1.hsd1.nj.comcast.net [68.44.240.1]
3 11 ms 10 ms 12 ms te-9-2-ur01.hammonton.nj.panjde.comcast.net [68.85.76.29]
4 10 ms 10 ms 10 ms te-1-1-ur01.mayslanding.nj.panjde.comcast.net [68.86.210.42]
5 11 ms 10 ms 11 ms xe-6-0-0-0-ar03.absecon.nj.panjde.comcast.net [68.86.210.46]
6 15 ms 12 ms 15 ms ae-1-0-ar03.plainfield.nj.panjde.comcast.net [68.85.63.209]
7 17 ms 17 ms 18 ms pos-3-10-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.92.217]
8 16 ms 17 ms 16 ms be-12-pe04.ashburn.va.ibone.comcast.net [68.86.84.210]
9 40 ms 39 ms 39 ms INTERNAP.Gi1-0-11.asr1.YYZ1.gblx.net [64.214.196.26]
10 40 ms 39 ms 43 ms xe-3-3-0.tor10.ip4.tinet.net [141.136.110.9]

Ping statistics for 141.136.110.9: <- Last hop before ping is blocked
Packets: Sent = 243, Received = 239, Lost = 4 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 104ms, Average = 47ms

Gonna grab pingplotter and see which hop is where the loss is happening, and see if others with the packetloss are going through the same hop.

Edited by Tarl Cabot, 03 September 2018 - 02:33 PM.

[NARC BAIT]

going to take a stab in the dark, and say, no, there is no 'key' within the engine that you can set that will relate to that ...

normally I wouldnt consider increasing a timer to be the correct option anyway, because you would at best be delaying a problem, not actually fixing or bypassing it

and what they are talking about in that thread, relates to a different set of modifications to cryengine than what PGI has done ...

have you tried using a program like wireshark, to say, look for malformed packets ?