-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unknown Message Types #58
Comments
Match ID: 1782181262 tick 57378, synthetic true, had 0 messages |
uploaded a new snapshot, which has all those... |
unknown embedded message of kind SOURCE2/510. Please report this in the correspo |
new snapshot uploaded |
What type of messages are these things? unknown embedded message of kind SOURCE2/62. Please report this in the correspon |
My guess is that @spheenik tried to remove as many of the messages from the generated Java classes as possible to reduce code size and speed up compile times. |
@howardchung: correct. @Decoud: |
@spheenik latest protobufs are always available at https://github.com/SteamDatabase/GameTracking/tree/master/Protobufs/dota |
+1 for GameTracking :) |
@manveru: thx! So, their netmessages say that it's CSVCMsg_HLTVStatus. I'll release a new protobuf snapshot tonight... |
new snapshot uploading as I type... |
SOURCE2/554 |
I think this is the new CombatLogDataHLTV. @spheenik added support for it last night, try updating your snapshot? |
Works fine, my bad. Should have checked for the update first. Will have to take a closer look at some of those combat log changes. |
kind 534 or 544 file name: frankfurt_major\1856290165_1750727379.dem file name: frankfurt_major\1858282173_1016472045.dem file name: frankfurt_major\1859146913_1174254792.dem file name: frankfurt_major\1860271085_922706473.dem file name: frankfurt_major\1861004655_314559210.dem file name: frankfurt_major\1861405896_2145933448.dem file name: frankfurt_major\1861422181_1394172680.dem |
Hi, thx for reporting! Deployed a new snapshot of clarity protobuf that has 534, The 544 is the new combatlog - I already included it a week ago. So it seems your snapshots are not up to date. |
Bullshit - 544 was new too - added. |
According to proto definition appears to be some kind of match metadata. Type is bytes so it's probably binary encoded in some way. |
I have a fix, but I cannot test it. |
Thx, will push a fix tonight. |
Fix is out. |
unknown embedded message of kind SOURCE2/558. Please report this in the corresponding issue: #58 (lower priority, I don't think this crashes the parser) |
I also got the same error as @howardchung
It seemed to have ran alright, no errors, though it does seem like it took longer to complete. |
added 558 (S2DotaGcCommon.CMsgDOTAMatch) which contains a lot of detailed information about the match. |
Can you help me with
|
added those 2 with this commit and pushed a new snapshot. |
I've been getting crashes lately with this code: unknown top level message of kind SOURCE2/1171. Please report this in the corresponding issue: #58
|
Detailing the above details here: faq I too am experiencing the above mentioned issue:
Using git repo: with replay ID: Let me know if I misunderstood anything 🙇 |
Thank you for starting the wiki! I did not know if we were allowed to do it. |
New protobufs have been released. Added My testing capability was limited, since downloading replays through the client seems buggy atm. (Opendota also does not work). Regarding the Wiki Thing: |
Oh, and, the protobufs contain several extra combatlog properties. If you want to use them, I released clarity 2.7.6. Pushed both artifacts to central five minutes ago, so might be an hour or so before you see them. |
@spheenik Please do! I'll follow your lead on the docs. Thanks spheenik! |
also |
Not sure how to be more helpful, but I got a I was trying to parse the first map of this game https://www.hltv.org/matches/2370928/liquid-vs-faze-iem-chengdu-2024 |
unknown top level message of kind CSGO_S2/16. Please report this in the corresponding issue: #58 |
Thank you guys, |
|
Got an error parsing
|
Thanks for reporting, as long as the parsing process didn't crash, it's fine. |
Hey Martin @spheenik! When you do plan to do it- Would it be possible for you to record your process? I'd like to learn and document the process in the FAQ so others can potentially contribute in the protobuf parsing. You don't need to explain everything step by step- just dropping specific keywords will be enough for me to do my own research to be able to do it myself. If this is inconvenient to do- no worries. I just want to express my gratitude for your work! Thank you! |
got the same error, but the parser crashes. I'm just trying to seek to "getLastTick" in order to get scoreboard |
CSGO_S2/76, CSGO_S2/141 and CSGO_S2/154 have been added in |
@ndorigatti I just tested your replay, and it does not crash here in |
Yeah it was not in that furia replay, was one of mine... I will try again, but don't know how to share that 300mb replay |
@ndorigatti I have a hunch that self recorded replays do not properly encode the last tick. |
Dota 2. Match ID: 7888568761 I get the following message: Clarity seems to be up to date: api("com.skadistats:clarity:3.1.1") |
@thurd fixed in |
2024-10-17T23:49:17.997-07:00 WARN 38708 --- [ clarity-runner] clarity.runner : unknown embedded message of kind DEADLOCK/353. Please report this in the corresponding issue: #58 |
Dota 2. Match
|
Deadlock match 30739042 downloaded from http://replay272.valve.net/1422450/30739042_2038137483.dem.bz2:
|
Deadlock match 25917978
|
@MaverickMSG Can I ask how you got that direct download link? |
@dellis23 you can generally work (in Dota 2 as well) from the metadata from the GC (i.e. something CMsgClientToGCGetMatchMetaDataResponse). In the example of
|
@Noxville Thanks! I assume GC is some sort of API I have to hit first for a given match ID? |
It's the game coordinator. It's how the game client talks to the server, using protobuf encoded messages. |
Thank you for reporting an unknown message type.
Please note: In case clarity detects an unknown message, it reports this with the warning, but will be able to skip over the message and successfully parse the replay. This means that if you have an exception, there is another problem, and I suggest you open a new issue.
The text was updated successfully, but these errors were encountered: