Posted: Thu Nov 30, 2006 6:14 am
It's quite easy really, just use ^J mod..
Man, gotta try it out when I get home.
It sounds rly cool.
Page 3 of 3
Posted: Thu Nov 30, 2006 6:18 am
Posted: Thu Dec 07, 2006 6:57 pm
Posted: Fri Dec 08, 2006 2:18 am
Don´t brag with your conback.
HEHE
I´ve experienced that error several times on lan. But never found what caused it.
HEHE
I´ve experienced that error several times on lan. But never found what caused it.
Posted: Fri Dec 08, 2006 4:29 pm
lolzLotus wrote:Don´t brag with your conback.
HEHE
I´ve experienced that error several times on lan. But never found what caused it.
i want see this map
Posted: Fri Dec 08, 2006 5:16 pm
Strange. No idea what that error message means or what it's caused by for that matter.
Try setting MAX_MSGLEN > 1406
I'm not home for the weekend so I can't check if that's a valid command.
Nice to see that people are still discovering this map. It's frustrating but (hopefully) mostly fun :-)
Try setting MAX_MSGLEN > 1406
I'm not home for the weekend so I can't check if that's a valid command.
Nice to see that people are still discovering this map. It's frustrating but (hopefully) mostly fun :-)
Posted: Fri Dec 08, 2006 6:28 pm
MAX_MSGLEN is referring to the max size of a packet, usually caused by too much "information" (mostly entities information) in one packetFlunx wrote:Strange. No idea what that error message means or what it's caused by for that matter.
Try setting MAX_MSGLEN > 1406
I'm not home for the weekend so I can't check if that's a valid command.
Nice to see that people are still discovering this map. It's frustrating but (hopefully) mostly fun :-)
Not 100% sure about this, but iirc, this should be it. Caused by too many entities in a map, or too open layout. I think this could potentially also be caused by certain cl_maxpackets & cl_maxfps combinations, as these put "many packets into one" which would increase the size of the individual packets... maybe r1ch could shed some light over this?
Posted: Fri Dec 08, 2006 7:09 pm
i use apr 1.20, cl_maxfps 90 and cl_maxpackets 0NRGizeR wrote:MAX_MSGLEN is referring to the max size of a packet, usually caused by too much "information" (mostly entities information) in one packetFlunx wrote:Strange. No idea what that error message means or what it's caused by for that matter.
Try setting MAX_MSGLEN > 1406
I'm not home for the weekend so I can't check if that's a valid command.
Nice to see that people are still discovering this map. It's frustrating but (hopefully) mostly fun :-)
Not 100% sure about this, but iirc, this should be it. Caused by too many entities in a map, or too open layout. I think this could potentially also be caused by certain cl_maxpackets & cl_maxfps combinations, as these put "many packets into one" which would increase the size of the individual packets... maybe r1ch could shed some light over this?
, is bad? 