Overview[edit | edit source]
A demo in City of Heroes is an in-game recording made via the /demorecord Slash Command. The demo feature allows you to make recordings of your gameplay and use the game engine to play back those recordings. The recordings created this way are not actual video documents, but simply text files with a record of all the commands, models, effects, and animations that tell the game engine how to render the recorded demos. Because the demo files are just text files, demo recordings can be edited with any text editor, or with player-made tools specifically designed to manipulate demo files. This gives you the ability to modify demo recordings (or even create them from scratch) to make custom "movies" for playback via the game engine, allowing situations and events which may not exist during actual play. The demo playback can then be captured with a video capture tool and then further edited to customize your film, and to share it with others.
How To Record A Demo[edit | edit source]
To begin a demo recording, type the following on the chat command line:
Where "demo_name" is the name of the file you wish to save the demo name as. Do not use quotation marks in the actual name. The demo name should be all one word and should not contain any punctuation (hyphens and underscores are acceptable, spaces should be avoided). For example:
To stop the demo recording, type the following on the chat command line:
Please note that the demo will also automatically cease recording if you zone, such as when exiting a mission. If you have recorded a very large demo (either lengthy or one featuring a lot of in-game activity), the game may pause very briefly when issuing the /demostop command. It may therefore be advisable to wait until after the big boss fight to stop your demo recording.
The recorded demo will be saved to your City of Heroes directory in the "client_demos" folder. The demo recording file will have a suffix of "cohdemo". In the example used above, the "coolinvasiondemo1" file would be found as follows:
\city of heroes\client_demos\coolinvasiondemo1.cohdemo
Playing Back A Demo[edit | edit source]
Recorded demos can be played back multiple ways. Two of the more common methods are either to create a shortcut to the cityofheroes.exe application and modify it to launch a demo or to use a player-made application specifically to play back demos.
Playback Via A Windows Shortcut[edit | edit source]
Method 1[edit | edit source]
To play back a specific recorded demo via a Windows shortcut, use the following steps:
- Locate your City of Heroes directory and make a shortcut to cityofheroes.exe on your desktop (or wherever you prefer).
- Right click on the shortcut and select Properties.
- Within the Target box you will see the command line: "C:\Program Files\City of Heroes\CityOfHeroes.exe" (the directory path may be different if you did not install City of Heroes in the default directory).
- At the end of this line, add a space, followed by -demoplay your_demo_name (where your_demo_name is the name you gave the demo).
- For example: "C:\Program Files\City of Heroes\CityOfHeroes.exe" -demoplay coolinvasiondemo1
- Exit Properties.
- Double-click the shortcut you just created. This should launch the game client into demo playback mode and play the demo you specified.
Note that when playing back a demo via this method, the demo you specify in the shortcut properties must be in your client_demos folder.
Method 2[edit | edit source]
Similar to above, however if you leave off the your_demo_name in your shortcut, you can drag and drop any *.cohdemo file onto it and that particular demo will play without need to specify the file name in the shortcut. However, it is imperative that -demoplay is the last parameter if more are provided.
Playback Via A Demo Launcher[edit | edit source]
An alternative to playing back a demo via a shortcut to the game client is to use an application specifically designed to play back a demo (the application still does this via the game client but handles all of the operations required for demo playback automatically). Many people find this less cumbersome than launching via a modified shortcut or other method. Another advantage of using a demo launcher is that is may also perform automatic functions to "fix" certain aspects of demo playback if there are known playback issues resulting from playing the demo directly.
Probably the most popular demo launcher is Zloth's CoH Demo Launcher program.
Stopping Playback[edit | edit source]
Just hit the ESC key. The game will pop up a message box asking if you really want to quit. Unfortunately, under Windows Vista, this popup will often appear behind the game! Just alt-tab to it and select Yes to quit.
Uses For Demos[edit | edit source]
Recording Game Play[edit | edit source]
The most straightforward use for demo recordings is to capture some segment of game play for later viewing, sharing, or editing. Alternatively, there are stand-alone video capture applications (such as FRAPS, for example) that can directly record graphics displayed on your screen to a video file as another means of recording game play. There are both advantages and disadvantages to using the /demorecord function over other methods of recording game play.
Capturing Screenshots[edit | edit source]
Demos can also be useful for capturing Screenshots. If you have a particular screenshot in mind that requires specific timing, it can often be difficult to capture that specific moment during actual play. Particularly if you are rather busy trying to stay alive at the opportune moment. Demos have some answers to this problem.
The most straightforward way to do this is to play back the demo and take screenshots. Your screenshot key won't work but you can bring down the console (see below) and type in "screenshot" to take the shot. If you miss on the timing, simply replay the demo and try again.
Demo functions also include options to export the playback of a demo to a series of image files - one file for each frame displayed, as well as the option to adjust the speed of the demo by specifying the frames per second (FPS) of the playback. Between these two options, you can generate very precisely timed screenshots. The disadvantage of this is that exporting the playback of the demo to a series of image files can use a significant amount of disk space.
To use the image dump method, you'll need to turn on the -demodump option and set the -demofps to a number. (If you are using Zloth's Demo Launcher, select the Demo Dump option then set the "Speed (FPS)" number.) The higher you set the FPS, the more screenshots you will get. For instance, if you set the FPS to 7, you will get 7 screenshots for every second your demo plays back. When the demo is done, you simply go into the client_demos\screens directory and pick out your favorite screenshot(s) and delete the rest.
If your demo is huge, you might not have room on your hard drive for all the images that would be generated. The demo console comes in handy for this. Start your demo up with the FPS number you want and let it play until you start getting close to the area where you want screenshots saved. When you're ready, type the tilde (~) key on your keyboard and a command prompt will be shown. Enter "demodump 1" (without the quote marks) and the game will start saving screenshots. Type the tilde key again to get rid of the conosole. Let the demo play through the part you want to save. After that you can either quit the demo completely or do the tilde again and enter "demodump 0" to stop the screenshots from saving. Unfortunately, the -disable2D option will make it impossible to see the command console. The console still works but, without being able to see what you type or even if the console is open or closed, it's tricky to use.
The ability to edit and customize demos gives you the capability to produce screenshots of situations or events than can not be produced during actual play. You can replace players with NPCs like Ghost Widow or Statesman, change a player's costume or alter their sliders to make them taller or shorter, remove powers you don't want in your screenshot (like the glowing hands effect that comes with Hasten), give the enemies special powers (like the Freakshow disguise on the left), or even remove players or NPCs entirely!
Please note that the game user interface (UI) is not displayed during demo playback. If you require a screenshot that shows your chat windows, health/stamina bars, your enhancement screen, or other parts of the UI, this can not be captured from a demo.
Creating Custom Movies[edit | edit source]
Perhaps the most interesting application is using demos to create custom movies, or Machinima, using the City of Heroes game engine.
As mentioned, a recorded demo is saved as text file, rather than a standard video file. This text file contains all the commands required to instruct the game engine how to play back the recorded demo. This includes such information as what character models to display, special effects, character animations, character and object locations and orientations, character movements, camera angles and movements, and more. All of this information can edited, changed, deleted, or added to, and requires only a text editor (and a reasonable understanding of the appropriate demo information) to do so. This process is often referred to by players as Demo Editing.
An edited demo can then be converted to a standard video format (AVI, MPG, WMV, Quicktime, etc.). This can be done using a video capture tool such as FRAPS or by using demo playback options to export each frame of a demo to an image file (which could then be further manipulated if desired) and then converting that series of image files into a video. Once captured into a standard video format, video edit tools such as Windows Movie Maker can then be used to further customize the captured video with such additions as titles, scene transitions, voice-overs, and so forth.
Overall Demo Editing is a powerful tool for being able to create highly original movies using the City of Heroes game engine. To best understand what can be accomplished by editing demos, it may be useful to view some examples of movies created by this process. The following are just a few examples of many excellent and creative player-made movies created with Demo Editing:
- CoH Thank You at Maximilia.net (also a lo-res copy of CoH Thank You at YouTube)
- The Dance Gun at YouTube
- The Operatives - In The End at YouTube
- Vertical Studio featuring Night Prayers, Princess of Dusk, and Dies Irae videos
- MoonHill Productions
- Samuraiko Productions
- Hype Zero, Hype Won, and Hype Too at Vitae Rising (also lo-res copies of Hype Zero and Hype Won at YouTube)
Measuring Frames per Second[edit | edit source]
The /showfps Slash Command is nice as far as it goes but can't provide repeatable results. Demos can provide a much better solution to people who want to compare frame rates in the exact same situations. For instance, you may want to know if overclocking your CPU does anything other than void your warranty. You can record a demo, play it back using the -demostats and -demoloop commands, record the results, overclock your CPU, then play back the same demo with the same commands and compare just how much faster your computer is.
Limitations of Demos[edit | edit source]
Demos are not a perfect recording of the game and have a number of limitations/bugs.
- You must have the game to see the demo! If you email your demo to a friend that doesn't have CoH, your friend will have to download the entire game to see your demo.
- Demos are played back by your current version of the game, not the game 'as it was then.' So, if you took a demo on the north side of Talos Island back when the game first came out, you may find that the Arena has been put right on top of you when you play back a demo now. (On the plus side, if you've gotten a new computer since the demo was recorded, you can now watch the action with higher graphics settings!)
- Ragdoll physics look a little odd at times (but far better after Issue 12)
- Timing can sometimes be off. For instance, if your player runs forward, you might see your character start moving forward before the character starts running.
- Mission objectives (glowies) often do not appear in demos.
- Players and NPCs that try to turn invisible stay visible.
- Kheldians that shapechange will often stay stuck in the new shape when the demo is played back.
- After an enemy is defeated and has faded away, he/she/it will occasionally pop back in to the demo and just stand there.
- Sometimes demos will get a few stray commands tacked on to the end. These can cause the demo to keep playing for several seconds (even hours, though that's very rare) after the action has stopped.
- Demos made before Issue 8 can have slider problems. A new, invisible slider for arm length was introduced that can cause all the sliders following it in the demo description to get crazy. End result: players have huge/tiny arms and their face is all messed up. Very old demos made before sliders were introduced are not hurt by this problem.
List Of Demo Commands and Switches[edit | edit source]
Commands Used In-Game for Recording[edit | edit source]
- /demorecord <demo_name>
- Starts a demo recording with file name demo_name. The name must not have spaces or special characters. If you pick a name that you've already used, your new demo will overwrite your old demo.
- Stops a demo recording
Commands Used to Play Back Demos[edit | edit source]
- -demoplay <demo_name>
- Plays client_demos\demo_name.cohdemo. The demo must be in the client_demos folder or a subdirectory of that folder. The file played back CAN have spaces in the name, too, so feel free to rename your demos to something easier to read.
- -demofps <FPS>
- Renders demo at the specified frames per second (FPS); will not skip frames; changes the apparent speed of the demo playback
- Saves ("dumps") all frames of demo as JPEG images to client_demos\screens\demo_name
- Saves ("dumps") all frames of demo as TGA images to client_demos\screens\demo_name
- Hides all text effects (player chat, floating damage/healing text, etc.). This also hides the console.
- -fullscreen <fullscreenflag>
- fullscreenflag = 0 for windowed, 1 for fullscreen
- -screen <width> <height>
- Set the window size or screen resolution to the specified width and height
- -demopause <milliseconds>
- Stops at milliseconds
- -demoloop <loops>
- Causes the demo to repeat loops times before quitting
- -demoframestats 1
- When the demo completes, the game will display detailed statistics on how fast the display was being drawn. Normally used with the -demoloop command to run through the demo 3 or 4 times.
- Other Game Client commands like -renderthread will also work.
Console Commands[edit | edit source]
- ` or ~
- Use the ` (backwards apostrophe) or tilde key to turn the console command area on and off. If you have used the -disable2d command to start your demo then the console will not be visible. It will work, you just won't be able to see what you're typing.
- demodump <OnOffFlag>
- Demodump 1 starts saving screenshots of each frame to your hard drive. Demodump 0 to turn it off again. This is a handy thing if you only want screenshots from a small part of a large demo. Note that the console area will appear in your screenshots until you close it.
- demodumptga <OnOffFlag>
- Same thing as demodump but saves the screenshots in TGA format instead of JPG.
- Displays a huge list of commands (almost none of which work).
- Take a screenshot
- Take a screenshot in TGA format
- screenshotui <OnOffFlag>
- Screenshotui 1 will cause all following screenshots to display the user interface which, in this case, is the command console. Screenshotui 0 will make it so the command console doesn't get in the way of your screenshots.
- Quits out of the demo. There is no prompt to ask you if you really want to quit, it just quits.