User Tools
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
mapping:cawe:install [2005-09-14 11:14] Carsten created |
mapping:cawe:install [2013-01-07 12:07] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Installation ====== | + | ====== Installation, Initial Configuration and De-Installation ====== |
| - | The CaWE editor is included with the Ca3DE Developers Kit, and as such requires no explicit installation: | + | ===== Installation ===== |
| - | After unzipping the packed file, simply change into the ''CaWE'' sub-directory, and double-click on ''CaWE.exe'' | + | |
| - | ((The file is actually named ''CaWE_win32_vc60_r.exe'' for the Microsoft Windows release, and ''CaWE_li686_g++_r.linux'' for the Linux variant -- don't let that fact confuse you.)). | + | |
| + | The CaWE editor is included with the regular Cafu releases, and as such requires no explicit installation: | ||
| + | After unzipping the packed file, simply change into the ''Cafu-x.y'' directory. Under Windows, then double-click on ''RunCaWE.bat''. Under Linux, click ''CaWE-run'' in the ''Projects/Cafu/'' sub-directory. | ||
| - | ====== First-Time Configuration ====== | + | |
| + | ===== First-Time Configuration ===== | ||
| + | |||
| + | <color #CC0000/#FFD6D6>This section is relevant to CaWE releases **before February 2008 (version 8.02) only**. | ||
| + | If you have version 8.02 or newer, the initial setup is fully automatic and you can skip this section safely. | ||
| + | You may still check out the [[mapping:cawe:dialogs:options|Configure CaWE Options]] dialog anytime later. | ||
| + | </color> | ||
| CaWE requires some basic configuration for normal use, and thus asks you for providing at least one game (or "MOD") configuration when it is first run: | CaWE requires some basic configuration for normal use, and thus asks you for providing at least one game (or "MOD") configuration when it is first run: | ||
| - | - {{mapping:cawe:firstrun_nogameconfigs.png}} \\ After clicking on **OK**, CaWE will automatically show you the related configuration dialog. \\ \\ | + | - {{mapping:cawe:firstrun_nogameconfigs.png }} After clicking on **OK**, CaWE will automatically show you the related configuration dialog. <clear> \\ |
| - | - {{mapping:cawe:firstrun_emptyconfigdialog.png?300}} \\ Here, click on **Add New** for adding a new game configuration. You will then be asked for the desired name of the new config. \\ \\ | + | - {{mapping:cawe:firstrun_emptyconfigdialog.png?300 }} Here, click on **Add New** for adding a new game configuration. You will then be asked for the desired name of the new config. <clear> \\ |
| - | - {{mapping:cawe:firstrun_addnewgame.png}} \\ You can enter anything here, i.e. normally something that reminds you what MOD this config is related to, like "Ca3DE DeathMatch". \\ \\ | + | - {{mapping:cawe:firstrun_addnewgame.png }} You can enter anything here, i.e. normally something that reminds you what MOD this config is related to, like "Cafu DeathMatch". <clear> \\ |
| - | - Next you have to fill-in where the Game Data File is located. This is a file with ''.fgd'' suffix. One such file is already provided with the rest of the Ca3DE Developer Kit: the ''DeathMatch.fgd'' file in the ''Ca3D-Engine/Games/DeathMatch'' subdirectory. Click on the related **Browse...** button and locate the file. \\ \\ | + | - Next you have to fill-in where the Game Data File is located. This is a file with ''.fgd'' suffix. One such file is already provided with the Cafu package: the ''DeathMatch.fgd'' file in the ''Projects/Cafu/Games/DeathMatch'' subdirectory. Click on the related **Browse...** button and locate the file. \\ \\ |
| - | - {{mapping:cawe:firstrun_filledin.png}} \\ Finally, fill-in the rest of the dialog appropriately such that it eventually looks like this. The paths will of course be different for you, depending on where you installed the development kit and CaWE. Also, you do not have to provide all the settings for now, you can leave all fields with "executable" in their name empty (that is, the bottom four and the Game Executable Directory). \\ \\ | + | - {{mapping:cawe:firstrun_filledin.png }} Finally, fill-in the rest of the dialog appropriately such that it eventually looks like this. The paths will of course be different for you, depending on where you installed the Cafu package and its version. See the next step however for an alternative setup. <clear> \\ |
| + | - {{mapping:cawe:firstrun_filledin_rel.png }} Alternatively to the previous step, you can also fill-in relative paths as shown in this image. This is the preferred method, because it works better with future versions of CaWE, makes upgrading to a newer version of Cafu and CaWE easier, solves some problems with map compilation some people were reporting, and will become the default with future releases of CaWE! \\ Please note that under Linux, you have to use forward-slashes as the path separator (e.g. ''Games/DeathMatch'') and executable files must be referred to like e.g. ''./CaLight''. <clear> | ||
| > All settings in this dialog can be revised //later at any time// via the **File -> Configure CaWE...** menu. | > All settings in this dialog can be revised //later at any time// via the **File -> Configure CaWE...** menu. | ||
| Line 22: | Line 29: | ||
| - | ====== De-Installation ====== | + | ===== De-Installation ===== |
| - | CaWE, as all other Ca3DE related software, was designed to interfere with your computer and operating system as little as possible. | + | CaWE, as all other Cafu related software, has been designed to interfere with your computer and operating system as little as possible. |
| In general, it is enough to delete the directory that the packed file was unzipped to during installation, and all traces of CaWE are gone. | In general, it is enough to delete the directory that the packed file was unzipped to during installation, and all traces of CaWE are gone. | ||
mapping/cawe/install.1126689298.txt.gz · Last modified: 2013-01-07 12:07 (external edit)