User Tools

Site Tools


Differences

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

Link to this comparison view

Next revision
Previous revision
Next revision Both sides next revision
mapping:cawe:porting [2005-09-14 14:03]
Carsten created
mapping:cawe:porting [2006-07-30 00:38]
127.0.0.1 external edit
Line 1: Line 1:
 ====== Importing Maps from other Games/​Editors ====== ====== Importing Maps from other Games/​Editors ======
  
-FIXME  This text is out-of-date. +If you have already made worlds for other games (e.g. Half-Life, Quake3 or Doom3),
- +
-If you have already made worlds for other games (e.g. Half-Life ​DeathMatch),+
 you possibly wish to convert them for a Ca3DE MOD, like the //Ca3DE DeathMatch MOD//. you possibly wish to convert them for a Ca3DE MOD, like the //Ca3DE DeathMatch MOD//.
 You save a lot of work by doing so, and in general, porting "​foreign"​ worlds to Ca3DE is easily done. You save a lot of work by doing so, and in general, porting "​foreign"​ worlds to Ca3DE is easily done.
Line 18: Line 16:
     - If you are very experienced,​ you might solve many mismatchings directly by loading the ''​map''​ file into a text editor.     - If you are very experienced,​ you might solve many mismatchings directly by loading the ''​map''​ file into a text editor.
   * Although Ca3DE ignores unknown entities (e.g. entities left from other games), and fills-in default values for unknown properties, it is still best to do the conversion carefully in order to avoid unexpected results. For example, be specially careful with ''​func_wall''​ entities: you'll have to reset their //​rendermode//​ properties (translucent,​ blue becomes invisible, ...) //​explicitly//​!   * Although Ca3DE ignores unknown entities (e.g. entities left from other games), and fills-in default values for unknown properties, it is still best to do the conversion carefully in order to avoid unexpected results. For example, be specially careful with ''​func_wall''​ entities: you'll have to reset their //​rendermode//​ properties (translucent,​ blue becomes invisible, ...) //​explicitly//​!
-  * The worlds have to be //​re-textured//​. Re-texturing can either be done with the "​Replace"​ tool of CaWE, or (if you are very experienced) directly within the ''​map''​ file with a text editor, or even with a Perl script. +  * The worlds have to be //​re-textured//​. Re-texturing can either be done with the "​Replace"​ tool of CaWE, or (if you are very experienced) directly within the ''​cmap''​ file with a text editor, or even with a Perl script. ​In most cases, ​you'​ll ​have to work with the "Edit Face Properties"​ function thoughreplacing ​textures ​by hand
-  * Note that it is //not// advisable to use textures from WAD files other than the WAD file you have made yourself ​with ''​MakeWAD.exe''​. Foreign WAD files do not contain any new-style multi-image texture information (normal-maps,​ specular-maps,​ ...), and you had to manually extract their contents somewhere into the ''​Games/​MyMOD/​Textures''​ directory hierarchyor else the engine cannot find the textures ​when loading your world+  * Copying models and textures from other commercial games to Ca3DE is (usuallya copyright infringement. Please make sure that you only use those materials with Ca3DE whose author you are, or whose author gave you permission to use that materials with Ca3DE.
-  * Don't forget ​to change the name of the sky (environmentmap.+
  
mapping/cawe/porting.txt · Last modified: 2013-01-07 12:07 (external edit)