Introduction | Singleplayer Recording | Singleplayer Playback | User Map Recording | User Map Playback
Multiplayer Recording | Multiplayer Playback | GameMenu Playback | AutoLoad W/Record | Notes | Specs/Tools

A DEMO: When you first start up duke, a preview(demo) will play behind the menu. Hit esc to hear and see the full demo. This type of display is good for use in stores, or if you just want to let the game play back a demo of your favorite TC(explained later). Either way you don't have to settle for the demos that came with the game. You can record your own, make teaching tools out of them. You will be able to find many sites that post user demos for you to download and run. (Before using DEMOs, read this ENTIRE Guide)

CommandLine alternative:

DUKE3D /L# /V# /R - This will load and record a specific level.(Use Level warping cheats if necessary)

1. Load Duke up, You will get to the game menu.
2. Goto options and turn Record ON.
3. Start your game. You will see the demo cam's floating static, recording action at different angles.
4. End the game. The Demo Stop and will be saved in your duke folder as demo1.dmo and will automatically overwrite the existing file (if present)
5. rename your recorded demo for backup if its satisfactory.

DEMO-RECORDER Proper Stop and Shutdown:

A-Exit the level with a nuke button.

1. New level loads, Hit esc
2. At the Menu, Pick QUIT
3. Duke will shut down and save your last recorded demo.

B - Died.

1. Recording has stopped.
2. Hit esc
3. At the Menu, Pick QUIT
4. Duke will shut down and save your last recorded demo.

C - ESC StopButton.

1. After hitting the ESC key(Stop Button), recording has stopped.
2. At the Menu, Pick QUIT
3. Duke will shut down and save your last recorded demo.

1. Make sure the demo you want to playback is using the default file name demo1.dmo in your duke dir.
2. Make sure your duke dir and all supporting files are the same at the time of the recording. They MUST be exact.
3. Load Duke up, You will get to the game menu.
4. The demo(demo1.dmo) will be playing in the background
5. Hit esc, sound will be activated and full picture.

DEMO-PLAYER Keys:

• ESC controls menu display/demosnd off or on. Demo picture will continue to play.
• The "W" key will display the weapons over the players head.
• The "K" key changes views between the players if the game was a dukematch demo.(Red player is the Default view)
• The "F7" key will give you the standard chase view. This chase view is most effective for demo playback viewing.

CommandLine alternative:  (duke1.4/1.5) DUKE3D /D<file> This will load up duke and the demo you entered.

CommandLine alternative:

SETUP /R
-or- These will load the setup.exe, pick your level and recording will begin once you the game and user level are loaded.
DUKE3D -map <file> /R

For 1.4/1.5-

1. Goto setup.exe
2. Select your level
3. Launch
4. When the game and map load up hit esc
5. Pick Options/Record ON from the menu
6. Return to your game by hitting esc. Recording will begin.

For 1.3D-

1. Goto SETUP /R
2. Select your level
3. Launch
4. When the game and map load up. Recording will begin.

DEMO-RECORDER Proper Stop and Shutdown:

A-Exit the level with a nuke button.

1. New level loads, Hit esc
2. At the Menu, Pick QUIT
3. Duke will shut down and save your last recorded demo.

B-Died.

1. Recording has stopped.
2. Hit esc
3. At the Menu, Pick QUIT
4. Duke will shut down and save your last recorded demo.

C-ESC StopButton.

1. After hitting the ESC key(Stop Button), recording has stopped.
2. At the Menu, Pick QUIT
3. Duke will shut down and save your last recorded demo.

CommandLine alternative:

(duke1.4/1.5); DUKE3D /D<file>.
This will load up duke and the demo you entered.

1. Make sure the demo you want to playback is using the default file name demo1.dmo in your duke dir.
2. Make sure you have the usermap and all supporting files are the same at the time of the recording. They MUST be exact.
3. Goto setup.exe and select the user map the demo was recorded with.
4. Launch duke, once the game and map loads, hit esc.
5. Pick Quite to Title
6. Hit enter, sound will be activated and full picture.

DEMO-PLAYER Keys:

• ESC controls menu display/demosnd off or on. Demo picture will continue to play.
• The "W" key will display the weapons over the players head.
• The "K" key changes views between the players if the game was a dukematch demo.(Red player is the Default view)
• The "F7" key will give you the standard chase view. This chase view is most effective for demo playback viewing.

CommandLine alternative:

(duke1.3d) SETUP /R
This will load the setup.exe and record the user level once your in the game.
MASTER Note: (duke1.3d) If you are the Master/Host, you can use the options menu in the game to turn Record ON.

1. Make sure you have the usermap and all supporting files.
2. PLAYER: Goto SETUP /R and in network, select the user map(all players must have the EXACT files and supporting files)
   MASTER: Goto setup.exe and in network, select the user map(all players must have the EXACT files and supporting files)
3. Launch your multiplayer game connection.
   MASTER: From Options/Record, turn it ON
4. When the Master starts the game, the recording will begin.

DEMO-RECORDER Proper Stop and Shutdown:

A-Exit the level with a nuke button.

1. New level loads, Hit esc
2. At the Menu, Pick QUIT
3. Duke will shut down and save your last recorded demo.

B-Died.

1. Recording has stopped.
2. Hit esc
3. At the Menu, Pick QUIT
4. Duke will shut down and save your last recorded demo.

C-ESC StopButton.

1. After hitting the ESC key(Stop Button), recording has stopped.
2. At the Menu, Pick QUIT
3. Duke will shut down and save your last recorded demo.

1. Use the same method as "PLAYBACK RECORDED DEMO from a USER MAP" outlined above.

If you want to have demos replay action from your TC to show off to the public. You know, at computer conventions, or at a buddy's house, or perhaps your taking a picture. Eitherway, Do the following:

1. Record 2 demos(v1.3d) or 3(v1.4/1.5) depending on your version.
2. Now name them in the order in which you want the MENU Display to play them back.
   demo1.dmo
   demo2.dmo
   demo3.dmo(v1.4/1.5 Only)
3. You must have your TC installed with all unmodified files that where used during the recording of the .demos
   This includes:
   .art files
   .map files
   .con files
   Sounds may or may not effect the playback timing.
4. okay, now Load up Duke
5. Hit esc and see if the demos will play in the correct order and performance you want.
6. If sound/picture and performance are 100%. Then this is what your "Store Display" would look like.

You can make a level auto-load with Duke by:

1. From the command prompt, type Duke3d -map <file> /r /l08
   This will take you straight to the level, with demo-record mode on.
2. When you subsequently start Duke, the level will load automatically.
3. When you start a game, a fifth option will appear: USER MAP <name.map>

Other Command lines, stack:

Load a CON Set, Load non-default grp, name of demo in grp
duke3d /<file.con> /<file.grp> /<demofile#>

A-Demos recorded using users maps are required to have the usermap present to function correctly. This includes the same cons and art when the demo was recorded. They must be EXACTLY the same at the time of the recording.(your better off distributing demos in a package, rather than alone)
Side effects include dukes movement not matching the path of the map, demo playback fail, playback timing offset.

B-Exiting a level by a Nuke Button ,Exiting with ESC,or Dying stops the demo recording(abnormal ejection from the game may corrupt the demo and/or the demo save process.) Note: if you pick Quite To Title after your done recording, the demo will not be saved, You MUST use the QUIT option to shutdown duke properly. Each and everytime. Not doing so will lose the demo.

C-Anytime a new level or game is started with the recorder on, it will write over any demo1.demo files in the duke dir. This is actually inconsistent for some reason, to the numerical order games(.sav) and screenshots(.pcx) are saved in duke. Kinda weird.

D-If the game locks up on you during a recording session. The demo may be intact. See if demo1.demo is present and able to be played back.

E-Demos can be recorded in multiplay, provides more over head aswell. Demos will record game pauses or jerkiness due to lag, lost packets, CPU slow downs, etc... Scores will be present, Item use is visible, along with every other event.

F-DEMOs from 1.3D and 1.4/1.5 have some incompatibility. Definitely Demos record in 1.4/5 trying to playback in 1.3d

G-You can disable the demos by deleting them from your duke(v1.3d) dir. For v1.4/1.5 since it defaults to the .grp file demos if there not present(deleted) Try using command line duke.exe /dnull or patch the atomic.exe and rename .demos internally.

H-Maps must have Demo CAMS Built in. When making a map, Demo cameras can be placed anywhere. Tile 11,12

I- Duke1.3d comes with two .demo files(checks external only). Duke3dv14/15 comes with three .demos(checks external then grp) PLAYback is in numerical order. At the end of each demo, duke will automatically quit to title and return to play the next demo in numerical order.

Uwe Girlich

Uwe programmed The Little Movie Processing Center (software to edit game recordings, rudimentary support for Duke Nukem 3D and Redneck Rampage DMO files). more importantly, Uwe created the demo specifications for LMP (doom to hexen), DMO (duke3d), DEM (quake) and QWD (quakeworld) recordings. the specs are essential for demo editing and client side bots.

DMB Demo Runner!

Playback DEMO's easily, for 1.4/1.5