- Joined
- Mar 28, 2009
- Messages
- 806
I am seeing a lot of demos posted lately that are somewhat fairly obvious demos of non hackers.
If anyone wishes, PM me any time. I am willing sit down with anyone to show you the "basic tricks" in watching a demo so your submitting future demos will be better.
I am no means an expert, but I can show you the basics so your future submissions will not have, what I call the "not obvious hacking" demo.
Does this take a lot of time. YES, it takes a heck of a lot of time. Just think, there are only two persons in DoD:S division that can review submitted demos, and most time it is really only one person viewing your demo. So HELP HIM OUT.
I recommend you demo yourself, and view the demo of you making kills, and when you make the spectacular kill, see what it looks like so you have a basic understanding what it looks like in very slow speed. You will then have a basis of understanding when you are looking a someone else's demo.
==================================================
Basics of viewing a demo
----------
A: Recording a demo:
https://www.edge-gamers.com/forums/showthread.php?287714-Recording-a-demo-for-Day-of-Defeat-Source
Keep demo to 5 min or less.
Note: Use no spaces in the demo name as the demoui player will not recognized the file.
---------
B: demo gui,
where on you hard drive the demo is located,
"X:\Program Files (x86)\Steam\SteamApps\common\Day of Defeat Source\dod"
I created a desktop short cut for convenience.
--------
C: basics of the demo gui:
Start dods, call up console, type "demoui" and enter, the demo gui appears.
1. how to call up "load" an recorded demo. Click load, the default demo location is seen. Pick the demo you wish to view, and click open. demo should load and start playing.
2. speed up and slow down the demo (using slider bar, or you arrow keys)
NOTE: I use 1% to 2.5% speed to see the difference between a persons hand and computer aimbot, and recoil of normal person and aimbot.
3. replay (how to jump back in demo or to a specific location) (use "Goto" and tick#)
4. There is an "Edit" and "Smooth" buttons. This is much more technical for a different class.
You can read about those at: https://developer.valvesoftware.com/wiki/Demo_Recording_Tools
5. smoke and sound basics
Note: you have to go back far enough of the location in the demo to ensure proper viewing and hearing the sound correctly. (Flaw in demo player watching and seeing smoke if you jump to tick# smoke gernade is already creating smoke. Same with sound.)
6. Other basic console command tools for demo viewing:
sv_cheats 0/1 0-off 1-on (then reset of commands will work for demo viewing)
mat_wireframe 0/1/2
r_drawothermodels 2 - shows other models through walls
You need these to turn on wireframe/draw other models to view a player tracking other players behind walls/smoke.
--------
D: HELP HIM OUT. If not sure, submit the demo.
You made the demo, so you know where you think there might be something fishy.
It helps greatly if you post can be something like this:
I think this player is using an aimbot.
tick# 3138 it appears aimbot is snapping to target
tick# 4344 it appears aimbot is snapping to target
I think this player is using a wall/smoke hack.
tick# 5315 it appears person is tracking invisible players behind walls and kills them when they appear in the doorway.
tick# 1567 and 3245 person shoots and kills consistently through smoke.
NOTE: Please check the eGO statsme web page for that player. If the statistics do not show it is an obvious hacker (kills verses headshots), please ensure you closely review your demo with specifics prior to submission. Myself and Predator Lark have 19% headshot(HS) percentage, Flowey has a 21% HS percentage, and Boyle has a 23% HS percentage. Normally, a hacker using an aimbot is going to way outside this range percentage.
If anyone wishes, PM me any time. I am willing sit down with anyone to show you the "basic tricks" in watching a demo so your submitting future demos will be better.
I am no means an expert, but I can show you the basics so your future submissions will not have, what I call the "not obvious hacking" demo.
Does this take a lot of time. YES, it takes a heck of a lot of time. Just think, there are only two persons in DoD:S division that can review submitted demos, and most time it is really only one person viewing your demo. So HELP HIM OUT.
I recommend you demo yourself, and view the demo of you making kills, and when you make the spectacular kill, see what it looks like so you have a basic understanding what it looks like in very slow speed. You will then have a basis of understanding when you are looking a someone else's demo.
==================================================
Basics of viewing a demo
----------
A: Recording a demo:
https://www.edge-gamers.com/forums/showthread.php?287714-Recording-a-demo-for-Day-of-Defeat-Source
Keep demo to 5 min or less.
Note: Use no spaces in the demo name as the demoui player will not recognized the file.
---------
B: demo gui,
where on you hard drive the demo is located,
"X:\Program Files (x86)\Steam\SteamApps\common\Day of Defeat Source\dod"
I created a desktop short cut for convenience.
--------
C: basics of the demo gui:
Start dods, call up console, type "demoui" and enter, the demo gui appears.
1. how to call up "load" an recorded demo. Click load, the default demo location is seen. Pick the demo you wish to view, and click open. demo should load and start playing.
2. speed up and slow down the demo (using slider bar, or you arrow keys)
NOTE: I use 1% to 2.5% speed to see the difference between a persons hand and computer aimbot, and recoil of normal person and aimbot.
3. replay (how to jump back in demo or to a specific location) (use "Goto" and tick#)
4. There is an "Edit" and "Smooth" buttons. This is much more technical for a different class.
You can read about those at: https://developer.valvesoftware.com/wiki/Demo_Recording_Tools
5. smoke and sound basics
Note: you have to go back far enough of the location in the demo to ensure proper viewing and hearing the sound correctly. (Flaw in demo player watching and seeing smoke if you jump to tick# smoke gernade is already creating smoke. Same with sound.)
6. Other basic console command tools for demo viewing:
sv_cheats 0/1 0-off 1-on (then reset of commands will work for demo viewing)
mat_wireframe 0/1/2
r_drawothermodels 2 - shows other models through walls
You need these to turn on wireframe/draw other models to view a player tracking other players behind walls/smoke.
--------
D: HELP HIM OUT. If not sure, submit the demo.
You made the demo, so you know where you think there might be something fishy.
It helps greatly if you post can be something like this:
I think this player is using an aimbot.
tick# 3138 it appears aimbot is snapping to target
tick# 4344 it appears aimbot is snapping to target
I think this player is using a wall/smoke hack.
tick# 5315 it appears person is tracking invisible players behind walls and kills them when they appear in the doorway.
tick# 1567 and 3245 person shoots and kills consistently through smoke.
NOTE: Please check the eGO statsme web page for that player. If the statistics do not show it is an obvious hacker (kills verses headshots), please ensure you closely review your demo with specifics prior to submission. Myself and Predator Lark have 19% headshot(HS) percentage, Flowey has a 21% HS percentage, and Boyle has a 23% HS percentage. Normally, a hacker using an aimbot is going to way outside this range percentage.
Last edited:
