-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">\r
-\r
-<html>\r
- <head>\r
- <meta name="generator" content="HTML Tidy, see www.w3.org">\r
-\r
- <title></title>\r
- </head>\r
-\r
- <body>\r
- <H1>How it works</H1>\r
-<P>The following is a description of how\r
-the program processes a single job:</P>\r
-<UL>\r
- <LI><P>The program takes your original\r
- demo, e.g. “C:\Nexuiz\data\demos\test.dem” and creates a\r
- copy of it, the <I>cut demo</I>. This file has the name\r
- <original_demo_name><B>_autocut</B>.dem. The cut demo is\r
- different to the original demo in a way that console commands have\r
- been <I>injected</I>, so basically the engine thinks that you had\r
- entered them yourself (e.g. cl_capturevideo 1 to start recording).</P>\r
- <UL>\r
- <LI><P>Since it is possible to inject\r
- any possible console command, the first command that is injected is\r
- to disable rendering (r_render 0), save the value of your “volume”\r
- setting and then setting it to 0 (as long as you have sound and\r
- rendering disabled while fast-forwarding in the preferences of the\r
- Demo Recorder). Then a slowmo 100 command (first stage value from\r
- the Demo Recorder preferences) is injected in order to fast-forward\r
- the demo.</P>\r
- <LI><P>Then, when the game time in the\r
- demo is about 1 minute less than your specified start time of the\r
- job, slowmo is reduced to 10 (second stage value from the\r
- preferences)</P>\r
- <LI><P>Then, when the game time in the\r
- demo is about 5 seconds less than your specified start time, <B>slowmo</B>\r
- is set to <B>1</B>, rendering and sound is enabled again, and\r
- whatever your put into the <B>exec before capture</B> field is\r
- being injected, too. Then, the values of cl_capturevideo_nameformat\r
- and _number are being saved to a temporary variable and are\r
- overwritten with defined values (<B>autorec</B> and <B>1234567</B>),\r
- so that the Nexuiz Demo Recorder will know the exact name of the\r
- output file (which is necessary so that it can move that file to\r
- your desired video destination/location)</P>\r
- <LI><P>When the the start time is\r
- reached, cl_capturevideo 1 is injected, once the end time is\r
- reached, cl_capturevideo 0 is injected.</P>\r
- <LI><P>Shortly after, whatever you put\r
- into the exec after capture field is executed, and then the\r
- original values of cl_capturevideo_nameformat and _number are being\r
- restored.</P>\r
- <LI><P>Then a disconnect command is\r
- injected</P>\r
- </UL>\r
- <LI><P>Next, your specified Nexuiz\r
- engine binary is launched. The parameters given to the binary are:</P>\r
- <UL>\r
- <LI><P>The content of the <B>engine\r
- parameters</B> field of the job, and</P>\r
- <LI><P><B>-demo\r
- <relative-demo-path>/<demo-file-name></B> (this will\r
- start Nexuiz, e.g. <B>-demo demos/test.dem</B>, launch the <B>test.dem</B>\r
- demo, and the engine will play the complete demo until a disconnect\r
- is issued (which we have injected above), and then Nexuiz will\r
- close automatically. This -demo parameter exists since Nexuiz 1.0</P>\r
- </UL>\r
- <LI><P>Once the Nexuiz Demo Recorder\r
- notices that your Nexuiz engine binary closed, it will look for the\r
- recorded video file in <DPVideo-directory>/autorec1234567.<avi/ogv>\r
- and move it (rename it) to your desired <video-destination>,\r
- keeping the original extension of the file. In case the preferences\r
- are setup to not overwrite an existing video file, a file with\r
- ending _copy1 (2, 3, …) will be created.</P>\r
-</UL>\r
- </body>\r
-</html>\r
-\r
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
+
+<html>
+ <head>
+ <meta name="generator" content="HTML Tidy, see www.w3.org">
+
+ <title></title>
+ </head>
+
+ <body>
+ <H1>How it works</H1>
+<P>The following is a description of how
+the program processes a single job:</P>
+<UL>
+ <LI><P>The program takes your original
+ demo, e.g. “C:\Nexuiz\data\demos\test.dem” and creates a
+ copy of it, the <I>cut demo</I>. This file has the name
+ <original_demo_name><B>_autocut</B>.dem. The cut demo is
+ different to the original demo in a way that console commands have
+ been <I>injected</I>, so basically the engine thinks that you had
+ entered them yourself (e.g. cl_capturevideo 1 to start recording).</P>
+ <UL>
+ <LI><P>Since it is possible to inject
+ any possible console command, the first command that is injected is
+ to disable rendering (r_render 0), save the value of your “volume”
+ setting and then setting it to 0 (as long as you have sound and
+ rendering disabled while fast-forwarding in the preferences of the
+ Demo Recorder). Then a slowmo 100 command (first stage value from
+ the Demo Recorder preferences) is injected in order to fast-forward
+ the demo.</P>
+ <LI><P>Then, when the game time in the
+ demo is about 1 minute less than your specified start time of the
+ job, slowmo is reduced to 10 (second stage value from the
+ preferences)</P>
+ <LI><P>Then, when the game time in the
+ demo is about 5 seconds less than your specified start time, <B>slowmo</B>
+ is set to <B>1</B>, rendering and sound is enabled again, and
+ whatever your put into the <B>exec before capture</B> field is
+ being injected, too. Then, the values of cl_capturevideo_nameformat
+ and _number are being saved to a temporary variable and are
+ overwritten with defined values (<B>autorec</B> and <B>1234567</B>),
+ so that the Nexuiz Demo Recorder will know the exact name of the
+ output file (which is necessary so that it can move that file to
+ your desired video destination/location)</P>
+ <LI><P>When the the start time is
+ reached, cl_capturevideo 1 is injected, once the end time is
+ reached, cl_capturevideo 0 is injected.</P>
+ <LI><P>Shortly after, whatever you put
+ into the exec after capture field is executed, and then the
+ original values of cl_capturevideo_nameformat and _number are being
+ restored.</P>
+ <LI><P>Then a disconnect command is
+ injected</P>
+ </UL>
+ <LI><P>Next, your specified Nexuiz
+ engine binary is launched. The parameters given to the binary are:</P>
+ <UL>
+ <LI><P>The content of the <B>engine
+ parameters</B> field of the job, and</P>
+ <LI><P><B>-demo
+ <relative-demo-path>/<demo-file-name></B> (this will
+ start Nexuiz, e.g. <B>-demo demos/test.dem</B>, launch the <B>test.dem</B>
+ demo, and the engine will play the complete demo until a disconnect
+ is issued (which we have injected above), and then Nexuiz will
+ close automatically. This -demo parameter exists since Nexuiz 1.0</P>
+ </UL>
+ <LI><P>Once the Nexuiz Demo Recorder
+ notices that your Nexuiz engine binary closed, it will look for the
+ recorded video file in <DPVideo-directory>/autorec1234567.<avi/ogv>
+ and move it (rename it) to your desired <video-destination>,
+ keeping the original extension of the file. In case the preferences
+ are setup to not overwrite an existing video file, a file with
+ ending _copy1 (2, 3, …) will be created.</P>
+</UL>
+ </body>
+</html>
+
projects / xonotic / xonotic.git / blobdiff