Gameplay videos are useful for marketing, bug reports, or feature mock-ups.
Some game engines (cube2, ioquake3) have video capture support. Use this if available. If not, there are many screencasting software options.
On Linux, FFmpeg might work, when other pieces of software fail (instructions).
- Record at 30 frames per second (fps)!
- Capture the game window only, without window decorations.
- As long as you get 30 fps, record as as high resolution as possible.
- Capture the game audio!
- If you plan to cut the video during editing heavily, disable music but keep sounds.
Remove all video material that does not show the game software in action. Cut down long loading times, cut out changing settings.
Do not replace the audio with generic music or music you like. Keep in-game sounds and music or keep sounds and add music from the game, if you did not record it to make editing easier.
If you failed to record sounds, it is acceptable to add music tracks from the game.
You can add voice commentary to review or demonstrate game versions.
- Start playing the game at the start of the video.
- If you want to explain the game to the viewers, do it while playing the game.
- Don't talk about video recording issues.
Use a video title that explains what you do in the game, what the name of the game is and what version it is. Add an URL to the game's homepage in the video description.
Embed or link to the video from the project page and/or social network pages.
You can make the creation of translations for video commentary a community effort on Universal Translations.