Demo Problem :(

by AnnieMac • 7 May 2008, 12:44 • Journals
So, here we go:

If i'm watching a demo im getting some different error messages in the middle of a demo.

Its kicking me, or well, the demo is stopping with these kind of errors:

- Unknown Event
- Illegable Server Msg
- Cl_parse .... blabla :p

On some demo, its this error, on another one im getting kicked for a different one.

dunno what it could be, anyone got a solution?


thx
Comments
17
▼
b 7 May 2008, 13:45
Unknown Event
▼
joey 7 May 2008, 13:48
nice pushing down gifty's journal!
▼
AnnieMac 7 May 2008, 13:48
thought the same :|

EDiT: LoL, deleted!
Parent
▼
joey 7 May 2008, 13:50
omfg. :D
Parent
▼
b 7 May 2008, 14:03
Why btw?
Parent
▼
joey 7 May 2008, 14:40
maybe sol is moody today.
Parent
▼
slajdan 7 May 2008, 13:51
Demos can get corrupted, especialy if it is old dm83 ones, but I have never seen one of those messages when such a thing has happened. :-P
▼
Quazz 7 May 2008, 13:51
Make a new installation of ET to watch demos , sth is screwed up :P
▼
HellHammer 7 May 2008, 13:56
google the error you get
▼
w0nd3r 7 May 2008, 14:00
IVE GOT A SOLUTION BUT I WON'T TELL YOU OLOLOLOL
▼
artlove 7 May 2008, 14:43
HEY IM SUPOST TO SAY THIS D:<
Parent
▼
nrx 7 May 2008, 15:29
I'm getting the same error while trying to watch demos from 2005. : (

CL_ParsePacketEntities: end of message

It always occurs at some exact moment in the demo, it's not random - also gave one demo to a friend to try, but it crashes at the same moment as it does to me.

some semi-relevant thing found by google:
QuoteI get disconnected upon joining servers with the error message "CL_ParsePacketEntity: end of message". Any ideas of how to fix this?

Open console and type in:
/reconnect

ET has a bit of a bug that can cause the client to attempt to send commands to the server before the connection is setup; the net result of this bug is that the initial data the server sends will be decrypted properly. The incorrectly decrypted data will still be interpreted, and will result in messages like 'configstrings > MAX_CONFIGSTRING', 'CL_ParsePacketEntities: end of message', or 'CL_ParseGamestate: bad command byte'.

You can mitigate the problem by making a conscious effort to avoid pressing any keys or mouse buttons (including the wheel) that result in commands being sent to the server (e.g. weapnext, weapprev) between the 'Awaiting challenge...' message and the actual level-loading screen.


but nothing about getting those errors while watching a demo. There's probably no solution. =o((
Back to top