demos

[OliveiraptV]

i like to know how to do show stumps and how commands work when i seeing the demo ths

[Shoresy]

You will have to be a little more specific @OliveiraptV

 

Like how we are able to enable it to show people through the walls? 

And how to do timestamps? 

 

[OliveiraptV]

yes  ths

Edited August 10 by OliveiraptV

[Shoresy]

With timestamps just simply take note of the timeclock at which point you find suspicious. 

 

For instance, if player locks onto target and you think that moment is the capture point of detecting a hack. Just note the time. When we say time what we mean is the in game timer, like Objective timer. Not what time it is or what time it was. Simply because the viewer may not be in the same timezone. So be sure to use "time" as a reference to the objective timer, or map timer I should say. (I would suggest marking times roughly a couple seconds or so before the activity you want observed) 

 

For the viewing players through walls, you would simply do /r_shownormals 1 (you can play around with the values, each is different 1, 2, 3 so on) 0 is to put back to normal. 

 

You can also do things such as /timescale .5 to slow the demo down by half. 1 is normal speed so as you can imagine, 2 would be twice as fast. 

 

There is a lot of commands out there that can help when viewing a demo but these are the most commonly used ones. 

[Betinho]

To know how to use a demo here is a brief summary:

 

To see for example a supposed cheater you can use the following:

 

1) timescale: this is used to see the demo faster or slower than normal (the normal is /timescale 1)
If you want to see something that seemed suspicious to you, the best thing is to see the demo a little slower (sometimes you miss things by going at normal speed), I usually put it in the middle /timescale 0.5 , but you can use whatever speed you like. It also serves to speed up a demo in which you can search for a part of the end of the demo, so you want to fast forward the demo, you can do it like this /timescale 5 or whatever you want.

2) shownormals: this shows you with white dots the players, so you have as a reference how they are moving behind walls, tanks, or whatever.
You can use /r_shownormals 1 to activate it and then /r_shownormals 0 to deactivate it.

screenshot in the demo: used to show an image inside the demo. With F11 you take a screenshot, and you can keep taking screenshots if something seems suspicious to you (for example with /r_shownormals 1 activated, today I just did that and it shows how things happen that seem suspicious to you with the images in the demo)

I think there are more commands, which I forgot or they are not very useful haha, but these three are essential for the evidence of cheaters.

 

Note: I think everyone knows how to record, with /record, what I see that they always forget in the demos is to use /statsdump . This command records all the scores inside the demo. If everyone were to use this in a supposed case of cheating, it's one more variable that helps you corroborate if someone might be cheating or not (example: someone with humanized aim, might be having 50, 60% acurracy and perhaps a lot of headshots, kills, etc. Well all these numbers will appear recorded in the demo (remember, /statsdump is like /scores, but /scores is not recorded in the demo and /statsdump is)

 

Regards

[-=HipKat=-]

13 hours ago, Betinho said:

Note: I think everyone knows how to record, with /record, what I see that they always forget in the demos is to use /statsdump . This command records all the scores inside the demo. If everyone were to use this in a supposed case of cheating, it's one more variable that helps you corroborate if someone might be cheating or not (example: someone with humanized aim, might be having 50, 60% acurracy and perhaps a lot of headshots, kills, etc. Well all these numbers will appear recorded in the demo (remember, /statsdump is like /scores, but /scores is not recorded in the demo and /statsdump is)

 

Regards

The best way to record is just record everything and then clean that Demo folder out about once a month

 

Add this to your CFG to record every map from start to finish. If you quit a map in the middle without manually stopping the recording, the demo will not save.

 

set demoon "autorecord; set nextdemo vstr demooff; echo ^2Recording ^7demo"
set demooff "stoprecord; set nextdemo vstr demoon; echo ^7Recording ^1stopped"
set nextdemo "vstr demoon"

 

Plus I added these to my CFG

 

bind F9 "record"
bind F10 "stoprecord"
bind F11 "screenshotjpeg"

bind F12 "vstr nextdemo"