What's new

Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

Register Now!

[TF2] Tips for recording Demos

Useful?

  • Yes!

    Votes: 8 100.0%
  • No :(

    Votes: 0 0.0%

  • Total voters
    8

Gibus

Totally Ordinary
Joined
Jan 16, 2019
Messages
402
Steam
76561198304859311
First off, I was not sure where I should post this little thread, so I guess it'll be here until an admin moves it to the correct location.

Hello people! This is a short little thread where I will give my personal tips to recording demos!
Personally, I play a lot of Jailbreak, where almost every 3rd round there is some kind of rule breaker. I recommend that you record every game you play, no matter what gamemode it is. You never know if you might catch a cheater, and starting a recording would be too slow!
Because my tf2 is partially broken, meaning it will corrupt my demos past a certain point (a new round starting on JB) I needed to start a new recording for every new round. Since the manual way is pretty tedious, I found a script that will partially automate the process!
(BTW, for anyone that asks, no, ShadowPlay does not support my graphics card, and other recording software cause massive FPS drops.)

Firstly, you need to access your autoexec file in TF2's directory:
[steam directory]/steamapps/common/Team Fortress 2/tf/cfg
If there is no CFG file with the name autoexec, just make a file with the name and change the file extension to .CFG.

Then paste this script into it:
//demo recording tool
alias demorec "demorec1"
alias demorec1 "stop; record tmpdemo1; developer 1; echo Demo #1 recording on...; wait 100; developer 0; alias demorec demorec2"
alias demorec2 "stop; record tmpdemo2; developer 1; echo Demo #2 recording on...; wait 100; developer 0; alias demorec demorec3"
alias demorec3 "stop; record tmpdemo3; developer 1; echo Demo #3 recording on...; wait 100; developer 0; alias demorec demorec4"
alias demorec4 "stop; record tmpdemo4; developer 1; echo Demo #4 recording on...; wait 100; developer 0; alias demorec demorec5"
alias demorec5 "stop; record tmpdemo5; developer 1; echo Demo #5 recording on...; wait 100; developer 0; alias demorec demorec6"
alias demorec6 "stop; record tmpdemo6; developer 1; echo Demo #6 recording on...; wait 100; developer 0; alias demorec demorec7"
alias demorec7 "stop; record tmpdemo7; developer 1; echo Demo #7 recording on...; wait 100; developer 0; alias demorec demorec8"
alias demorec8 "stop; record tmpdemo8; developer 1; echo Demo #8 recording on...; wait 100; developer 0; alias demorec demorec9"
alias demorec9 "stop; record tmpdemo9; developer 1; echo Demo #9 recording on...; wait 100; developer 0; alias demorec demorec10"
alias demorec10 "stop; record tmpdemo10; developer 1; echo Demo #10 recording on...; wait 100; developer 0; alias demorec demorec11"
alias demorec11 "stop; record tmpdemo11; developer 1; echo Demo #11 recording on...; wait 100; developer 0; alias demorec demorec12"
alias demorec12 "stop; record tmpdemo12; developer 1; echo Demo #12 recording on...; wait 100; developer 0; alias demorec demorec13"
alias demorec13 "stop; record tmpdemo13; developer 1; echo Demo #13 recording on...; wait 100; developer 0; alias demorec demorec14"
alias demorec14 "stop; record tmpdemo14; developer 1; echo Demo #14 recording on...; wait 100; developer 0; alias demorec demorec15"
alias demorec15 "stop; record tmpdemo15; developer 1; echo Demo #15 recording on...; wait 100; developer 0; alias demorec demorec1"
bind "o" "demorec"
bind "p" "stop"

Pretty much what this script does is record a new demo when you press o, and stop the demo when you press p. If the round ends, just wait a bit then press o without stopping the recording, then the script will stop the current demo recording and start a new one!
The script will make 15 demos before it will start overwriting existing ones, but will reset the process whenever you launch TF2. This means once you finish TF2, delete the recordings and then next time you start up TF2, the demos will start with number 1.
The location for the demos is [steam directory]/steamapps/common/Team Fortress 2/tf.
Alternatively, you can right click on TF2 in steam, click properties, local files, then browse local files and open the TF folder.

Hopefully this is useful to you, as I've not had any issues with the script so far.
If you have any issues, just comment below and I'll try to assist!
(please note: the game will freeze for a second when the demo recording starts.)

Edits:
- added the directory for the demos
 
Last edited:

Warrak

Positively Inhumane
Joined
Oct 24, 2016
Messages
367
Steam
76561198331696426
How do I find the exact ticks(or time) to direct staff to the event of digression in the demo? Is there any pause, play, fastforward, and timeshown menu that I don't know about?
 

10000 Cold Knights

Sufficiently Lethal
Joined
Feb 20, 2019
Messages
128
Steam
76561197989301185
How do I find the exact ticks(or time) to direct staff to the event of digression in the demo? Is there any pause, play, fastforward, and timeshown menu that I don't know about?
I believe you are looking for Demoui and demoui2, sir. Typing either into console will give you a little pop-up that shows you the current tick and also lets you skip to specific ticks, as needed. Theres a lot of other stuff they can do, but I'm new to demos myself, so thats all I got ;p
 

Gibus

Totally Ordinary
Joined
Jan 16, 2019
Messages
402
Steam
76561198304859311
How do I find the exact ticks(or time) to direct staff to the event of digression in the demo? Is there any pause, play, fastforward, and timeshown menu that I don't know about?
I believe you are looking for Demoui and demoui2, sir. Typing either into console will give you a little pop-up that shows you the current tick and also lets you skip to specific ticks, as needed. Theres a lot of other stuff they can do, but I'm new to demos myself, so thats all I got ;p
Yep, DemoUI is the one I use, since you can jump to specific tick points, or use the slider to speed up the playback.
If you need something that was offscreen, as long as it's within close proximity, you can use the drive button, then use WASD to move the camera. It needs to be within the area, or else the action is not rendered in, meaning you got nothing. All this is actually useful for is when someone MFK or something behind your back. Then you can just move the camera and see the action.
 

Users Who Are Viewing This Thread (Total: 1, Members: 0, Guests: 1)

Who Read This Thread (Total Members: 11)

Top