User Tools

Site Tools


Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
mapping:compiling [2006-05-04 17:29]
Carsten Minor revision of the wording, command line opening...
mapping:compiling [2013-01-07 12:07] (current)
Line 1: Line 1:
 ====== Compiling Maps at the Command-Line ====== ====== Compiling Maps at the Command-Line ======
  
-When you have finished editing a map in CaWE, you'll want to run it with Ca3DE.+When you have finished editing a map in CaWE, you'll want to run it with Cafu.
 The engine however requires that the map is in a precomputed form, and this section describes how you The engine however requires that the map is in a precomputed form, and this section describes how you
 turn your map into a fully precomputed world file. turn your map into a fully precomputed world file.
Line 15: Line 15:
 (Replace "​directoryname"​ with the name of the directory that you want to open.) Other useful commands are ''​dir''​ that shows all files that are in the directory you are currently in and ''​e:''​ (for example) to change the current hard drive. ​ (Replace "​directoryname"​ with the name of the directory that you want to open.) Other useful commands are ''​dir''​ that shows all files that are in the directory you are currently in and ''​e:''​ (for example) to change the current hard drive. ​
  
-In order to run the programs with the commands presented below, you'll first have to browse into the directory they are in (which is the ''​Ca3D-Engine''​ directory).+In order to run the programs with the commands presented below, you'll first have to browse into the directory they are in (which is the ''​Cafu-9.06''​ directory).
    
  
 ===== Compiling step 1: CaBSP ===== ===== Compiling step 1: CaBSP =====
  
-This program takes a cmap map file and creates a cw (Ca3DE world) file from it.+This program takes a cmap map file and creates a cw (Cafu world) file from it.
 Example: Example:
 <​code>​ <​code>​
-    C:\Ca3DE-MDK\Ca3D-Engine> CaBSP Games/​DeathMatch/​Maps/​MyMap.cmap Games/​DeathMatch/​Worlds/​MyMap.cw+    C:\Cafu-9.06> CaBSP Games/​DeathMatch/​Maps/​MyMap.cmap Games/​DeathMatch/​Worlds/​MyMap.cw
 </​code>​ </​code>​
 :!: **WARNING:​** The specified destination file (''​Games/​DeathMatch/​Worlds/​MyMap.cw''​ in the above example) gets :!: **WARNING:​** The specified destination file (''​Games/​DeathMatch/​Worlds/​MyMap.cw''​ in the above example) gets
 overwritten without prior notice! This is also true for mis-spelt file names. overwritten without prior notice! This is also true for mis-spelt file names.
-For example, if you type ''​Games/​DeathMatch/​Maps/​MyMap.map''​ instead of+For example, if you type ''​Games/​DeathMatch/​Maps/​MyMap.cmap''​ instead of
 ''​Games/​DeathMatch/​Worlds/​MyMap.cw''​ -- catastrophe! ''​Games/​DeathMatch/​Worlds/​MyMap.cw''​ -- catastrophe!
 As with most other computer software, in order to prevent a disaster, As with most other computer software, in order to prevent a disaster,
Line 33: Line 33:
  
 For quick tests during world development,​ you might want to skip the next two compiling steps For quick tests during world development,​ you might want to skip the next two compiling steps
-(CaPVS and CaLight). You can run the file obtained from the CaBSP tool directly in the Ca3D-Engine.+(CaPVS and CaLight). You can run the file obtained from the CaBSP tool directly in the Cafu engine.
 It will be unlit and without PVS information (which results in a lower frame rate), It will be unlit and without PVS information (which results in a lower frame rate),
 but is usually sufficient for early tests. but is usually sufficient for early tests.
Line 42: Line 42:
 This program creates the //​Potentially Visibility Set// for your worlds. Example: This program creates the //​Potentially Visibility Set// for your worlds. Example:
 <​code>​ <​code>​
-    C:\Ca3DE-MDK\Ca3D-Engine> CaPVS Games/​DeathMatch/​Worlds/​MyMap.cw+    C:\Cafu-9.06> CaPVS Games/​DeathMatch/​Worlds/​MyMap.cw
 </​code>​ </​code>​
  
Line 106: Line 106:
  
 This program calculates the lighting for a map. This program calculates the lighting for a map.
-The ''​CaLight.cfg''​ file contains the radiant exitance definitions for 
-textures that are supposed to be light emitters. 
 This program can take very long too, but you have better control over it This program can take very long too, but you have better control over it
 by specifying command line switches. Examples: by specifying command line switches. Examples:
 <​code>​ <​code>​
-    C:\Ca3DE-MDK\Ca3D-Engine> CaLight +    C:\Cafu-9.06> CaLight 
-    C:\Ca3DE-MDK\Ca3D-Engine> CaLight Games/​DeathMatch/​Worlds/​MyMap.cw +    C:\Cafu-9.06> CaLight Games/​DeathMatch/​Worlds/​MyMap.cw 
-    C:\Ca3DE-MDK\Ca3D-Engine> CaLight Games/​DeathMatch/​Worlds/​MyMap.cw -BlockSize 8 -StopUE 2 +    C:\Cafu-9.06> CaLight Games/​DeathMatch/​Worlds/​MyMap.cw -BlockSize 8 -StopUE 2 
-    C:\Ca3DE-MDK\Ca3D-Engine> CaLight Games/​DeathMatch/​Worlds/​MyMap.cw -fast +    C:\Cafu-9.06> CaLight Games/​DeathMatch/​Worlds/​MyMap.cw -fast
-    C:​\Ca3DE-MDK\Ca3D-Engine>​ CaLight Games/​DeathMatch/​Worlds/​MyMap.cw -SkipDialog+
 </​code>​ </​code>​
 The first line prints out detailed usage information for the CaLight tool, The first line prints out detailed usage information for the CaLight tool,
 the second line runs default lighting, which is recommended for most cases. the second line runs default lighting, which is recommended for most cases.
-The third and fourth lines are for very fast lighting, which is useful for quick tests during map development+The third and fourth lines are for very fast lighting, which is useful for quick tests during map development. 
-and the fifth runs default lighting without invoking the dialog, which is good for batch processing+
-If you don't use the ''​-SkipDialog''​ switch, CaLight will present you a dialog that +
-allows you to override the sunlight settings, that (should) have been set earlier in CaWE.+
 Please note that it is almost never reasonable to set BlockSize below 3 Please note that it is almost never reasonable to set BlockSize below 3
 and StopUE below 0.1 for highest quality lighting, even though that is possible and StopUE below 0.1 for highest quality lighting, even though that is possible
-(some of the worlds of the Ca3DE demo releases were compiled with a StopUE of 0.05).+(some of the worlds of the Cafu demo releases were compiled with a StopUE of 0.05).
  
 During the second phase of the computations ("​bounce lighting"​),​ note that you can interrupt the program During the second phase of the computations ("​bounce lighting"​),​ note that you can interrupt the program
 by pressing the ''​SPACE''​ button. That's sometimes useful for quick tests during map development. by pressing the ''​SPACE''​ button. That's sometimes useful for quick tests during map development.
  
-Finally, a word about memory consumption:​ CaLight requires ​64 MB of RAM for processing even the most simple worlds. +Finally, a word about memory consumption:​ CaLight requires ​//​plenty// ​of it! I would recommend to run CaLight only on computers with at least 1 GB of RAMit may or may not run with less
-Thus, make sure that you have at least 128 MBbetter 256 MB (or more) physical RAM available! +If //​permanent ​swapping// (extensive disk activity) ​occurs ​during the bounce lighting ​phase of CaLight, better abort it! 
-Note that it is normal that your computer swaps a lot of virtual memory right after program start+Under such circumstances,​ it will proceed ​//very// slow anyway, and the lengthy ​swap activity is certainly ​not healthy for your hard-disk. ​:!:
-If however the swapping (extensive disk activity) ​does not even stop during the direct or bounce lighting ​phases ​of the program, better abort it. +
-Under such circumstances,​ it will be proceeding ​//very// slow anyway, and the lengthy activity is probably ​not healthy for your hard-disk. +
-Only plugging-in more RAM will help then, but be assured that until now, I have never seen a world that required more than about 192 MB.+
  
  
-===== Done: Running the world with Ca3DE =====+===== Done: Running the world with Cafu =====
  
 If not already there, copy your world into the ''​Games/​DeathMatch/​Worlds''​ directory If not already there, copy your world into the ''​Games/​DeathMatch/​Worlds''​ directory
 if you made the world for the DeathMatch MOD, or into the ''​Games/​OtherMOD/​Worlds''​ if you made the world for the DeathMatch MOD, or into the ''​Games/​OtherMOD/​Worlds''​
 directory of the MOD you made the world for. directory of the MOD you made the world for.
-Then simply run ''​Ca3DE.exe''​ as stated in the user manual of the current demo release.+Then simply run ''​Cafu.exe''​ as stated in the user manual of the current demo release.
 Your world will be listed among the other worlds in the dialogs world list ("​server options"​). Your world will be listed among the other worlds in the dialogs world list ("​server options"​).
mapping/compiling.1146756557.txt.gz · Last modified: 2013-01-07 12:07 (external edit)