Rooms (Can you handle it?)
Moderators: Moderators, Mappers
-
- feels some chest pain
- Posts: 680
- Joined: Sun Aug 17, 2003 10:35 am
- In-game Name: iN Flunx
- Location: Trondheim
- Location: no
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 :-)
I like to play games, not watch them
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?
i use apr 1.20, cl_maxfps 90 and cl_maxpackets 0 , is bad?NRGizeR 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?