Solved Decompiling demos/replays

[afi]

It is possible to decompile demos (.dm_26 files)? I know that something like that exists for quake 1 and quakeworld, but I didn't find anything for quake3-games :/ (If it's even possible )

[Scooper]

What exactly are you looking to get from them?

[afi]

Player information, data about entitys, etc

It's not really important at all, I just think it would be interesting

[eezstreet]

http://skuller-vidnoe.narod.ru/q3dspecs.htm

This should give you a pretty decent spec. In theory, the format shouldn't be changed between Q3<->JA, but stay on your toes, and note the difference in playerState/entityState between JA<->Q3. Also note that the sizes CAN be completely different from what the q_shared.h specifies, this is in netf_overrides.txt/psf_overrides.txt in ext_data.

[afi]

Thanks man!

[eezstreet]

No problem. You just piqued my interest in making killcams in JA though.

[afi]

I solved quite a few errors, but for some days I keep getting the "bad command byte" error. Does it have something to do with the bigger playerstate/entitystate in JKA? Or is there something wrong with the MSG_ReadBits function?

[eezstreet]

The playerstate/entitystate is bigger in JKA than in Q3, which might be causing the issue. Bad command byte could mean that the usercommands aren't getting sent properly perhaps (not sure)

[afi]

I never figured how to make it not crash. I'm just curious now... we got some cheat-problems in the ESL. Is it possible to get information about... let's say edited/hacked sabers from the demo. Or: Are there information in a demo that are not shown with /configstrings?

[afi]

I just had some free time and decided to give it a new try but still no success... does anyone have an idea why it won't work? I mean, Q3 and JKA are not THAT different <.< (And yes, I got the different playerstate/entitystate)

[TomArrow]

Is this still something you're interested in?