**Credit Goes To Frank Booth**
This guide by Frank Booth is an extremely detailed guide on how to record & replay demos. It also shows you different ways of viewing the demos as well as other options to replaying the video. When you get the chance, please read this guide for it will come in handy one day.
**Credit Goes To Frank Booth**
This guide by Frank Booth is an extremely detailed guide on how to record & replay demos. It also shows you different ways of viewing the demos as well as other options to replaying the video. When you get the chance, please read this guide for it will come in handy one day.
With all the hacking going on this guide would be really helpful to reduce bans that are not needed and help admins spot hacks better should they spec someone.
Demos: A guide to recording and viewing demos
Demos are required for ban requests involving hacking. We send them in and the advisors determine if there is a hack. For those that wish to look at their own demos or do not know how to make a demo i made this tutorial.
Keep this in mind. It takes practice and experience to find hacks. Sometimes there are obvious ones, sometimes the obvious is not a hack. If someone can host the demos i can provide three nice examples.
I will start with a summary of the necessary commands. Then we move to recording the demo and the aspects involved in that. Finally, the bulk of this guide, how to view demos. Finally, emailing demos, the reason we record them in the first place.
Command Summary
Main Commands
These are the commands that are essential in recording and viewing a demo. I will provide examples in the Viewing The Demo section bellow.
record Demo Name
stop
playdemo Demo Name
demoui , demoui2
demo_timescale 0-100
r_drawothermodels 2
mat_wireframe 2
sv_showimpacts 1,2,3
Auxiliary Commands
See the Console Commands for explanation on commands not covered.
demogototick
demo_recordcommands
demogototick
demolist
demopause
demoresume
demo_interpolateview
demos
demo_fastforwardfinalspeed
demo_fastforwardramptime
demo_fastforwardstartspeed
demo_pauseatservertick
demo_quitafterplayback
Recording The Demo
This is the most important aspect of demos. The demo contains the evidence required to issue a ban against a hacker. The demo needs to be recorded in spectator mode. It is equally important, in almost all cases, that the demo be recorded in First Person View. After going Spectator press the SPACE key to switch between views. In some games pressing the CTRL key brings up a graphical menu that allows you to choose view, and the player name as well.
Should the player you are spectating die you get automatically moved to another player. If you remain on the player you got moved to just right or left click to go back or forward to return to the player you were recording initially. Or use the graphical interface to pick their name again.
record Demo Namestop
To record a demo open console. Use the record command to start recording a demo. The demo should be about five minutes in length. That size is ideal both in time, as it records ample evidence, and in size, making it easy to be emailed.
Once you press enter you get a message in console to confirm a recording has begun. Exit the console and spectate the player in the manner described above.
When you are satisfied with the demo and are ready to finish it open console again and type stop. The demo is saved in you Steam directory.
Viewing The Demo
Demos can be watched in the game. When you load a demo it is like joining a server. It will take a moment to load.
playdemo Demo Name
To view the demo open console and use the playdemo command.
As soon as the demo has finished loading open console again. This is a good time to load all the necessary commands.
demoui , demoui2
Type demoui or demoui2. Exit the console. Depending on which one you use you get a pop up screen. Press pause immediately. Using the auxiliary commands can eliminate the need, to some extent, for using demoui.
With the demo paused open console again to enter the rest of the commands. I will list them bellow, along with examples of each. The finished result will be like the picture at the start of this tutorial.
demo_timescale 0-100
On the demoui panel you can adjust the speed of the demo. demo_timescale can also be used for the same purpose but you can specify a numerical speed instead of using the slider. This allows for much greater control. You can vary the value from 0, which is 0 %, to greater than 1, which is 100%. Therefore entering a value of .25 will play the demo at 25% the normal speed.
r_drawothermodels 2
r_drawothermodels 2 allows you to see players through walls and ground, in addition to other objects. This takes the textures off certain models and makes their mesh visible. This is useful when looking for wall hack, as the two examples bellow are from actual demos that resulted in bans for wall hacking.
mat_wireframe 2
To use mat_wireframe 2 you must have sv_cheats enabled. Type in console sv_cheats 1 to enabled them. Then type in mat_wireframe 2. It can be used in conjunction with r_drawothermodels.
sv_showimpacts 1,2,3
This command allows you to see where bullets hit. The value that should be used it 2, for client side. Open console and enter sv_showimpacts 2. This command allows you to see if someone is using an aimbot because their bullets will hit the same spot. If you look in the example bellow you see two thing. The red dots is where the bullets hit the soldier. The red wireframe is that of the soldier at the time of death.
Emailing the demo
While you record the demo and can look at it the other important aspect is getting it to those who have the authority to do something about it. Make sure you follow the instruction posted in every division Ban Request forum. The demo needs to be named correctly, and include the necessary information along with it. Equally important is to send it to the correct address. Sometimes. should the demo be too large another email address needs to be used. Plan ahead for this based on the size of your demo as to not delay a decision.
Examples
Place demos here to be downloaded and viewed.
These three are excellent examples. Click the links for the outcome in the ban requests. I suggest you view STRUKOMnomnomnom first then look at the request.
Wallhack - Jaxe[Fin]
Jaxe Demo
Wallhack - all i like to do is camp
all i like to do is camp Demo
No Hacks - STRUKOMnomnomnom
STRUKOMnomnomnom Demo
**Credit Goes To Frank Booth**
Last edited:
