{"id":1225,"date":"2010-03-28T09:59:30","date_gmt":"2010-03-28T07:59:30","guid":{"rendered":"http:\/\/EinleitungIndiesemTutorialm\u00f6chteichdirzeigen,wiedudeinselbstgebautesBrushworkausalsMapobjekt(ASE-Datei)exportierenkannst.DasRotierenundSkalierenvonkomplexemBrushworkkannimRadiantmanchmalzuunerw\u00fcnschtenEffektenu"},"modified":"2020-06-18T10:42:44","modified_gmt":"2020-06-18T08:42:44","slug":"converting-brushwork-from-a-map-into-an-ase-map-object","status":"publish","type":"post","link":"https:\/\/worldofpadman.net\/en\/tutorials\/converting-brushwork-from-a-map-into-an-ase-map-object\/","title":{"rendered":"Converting brushwork from a map into an ASE map object"},"content":{"rendered":"

In this tutorial I want to show you how to convert your self-created brushwork from a map file into an ASE file as a map object. But before you start you should make sure that you have installed and configured the Q3Map2 compiler at least version 2.5.16 and the GtkRadiant 1.4 or newer for World of Padman. With older versions, you may encounter errors when using this tutorial.<\/p>\n

Introduction<\/h2>\n

Creating an ASE map object from existing brushwork of your map can have some advantages. Rotating and scaling complex brushwork can often lead to unwanted effects and shifts in your construction. Exporting your brushwork as a model in ASE format makes sense, because it can be easily re-imported into Radiant as a map object, which can then be rotated and scaled without restrictions. Another advantage is that an ASE map object references the textures from your map and therefore does not need an extra UV map. It is also a simple text file and can be edited directly in a text editor (e.g. Notepad++<\/a>) in order to adapt texture paths that have been changed afterwards. Also in the case that the adjustable grid sizes in the radiant limit you too much, an export can be helpful. Have you ever thought about making your brushwork much bigger and therefore more detailed and then simply inserting it again as a map object scaled much smaller?<\/p>\n

Of course, such an ASE map object also has disadvantages. You can only implement the ASE map object using the misc_model<\/em> entity, so it must be included in the BSP of your map. It is not possible to include the ASE Map object via the entity misc_externalmodel<\/em> or via the key model2<\/em> of any func<\/em> entity. In contrast to the MD3 format, ASE map objects are not automatically considered during the light calculation, i.e. they appear very bright in the map later. However, this can easily be corrected afterwards (see last section). So you see, the MD3 format is still justified.<\/p>\n

Preparing brushwork<\/h2>\n

To create an ASE map object, you need nothing more than your ready textured brushwork, which you have copied into an empty MAP file. It must have at least one brush with the property structural<\/em>, otherwise no ASE file will be created later. The positioning of the brushwork towards the coordinate origin of the grid in the Radiant is crucial, since this also defines the tag, i.e. the coordinate origin of the ASE map object. Therefore, for example, a table should be positioned centered above the coordinate origin in the grid of the Radiant, while a lamp should be positioned centered below. If you do not center your brushwork correctly before converting, it will not appear centered on the misc_model entity.<\/p>\n

\"Brushwork<\/a>

Brushwork with info_player_start and room with caulk texture<\/p><\/div>\n

Create a room around the brushwork that completely envelops the construction and apply the texture common\/caulk<\/em> to all six brushes of the room. In addition, all surfaces of your brushwork, which cannot be visible later in the game after positioning the map object anyway, should also have the caulk texture. These surfaces will then not be textured and thus unnecessary polygons will be saved. Finally you have to insert the entity info_player_start<\/em> somewhere in the room and save the map under the name of the later map object, e.g. myASEmapobject.map.<\/p>\n

Converting brushwork<\/h2>\n

There are several ways to convert your brushwork. But all of them use the same method. You can compile your small map e.g. via the build menu of the Radiant. To do so you have to select the command map2ase<\/em> which we created there for this very purpose.<\/p>\n

\"Build<\/a>

Build menu in Radiant with map2ase command<\/p><\/div>\n

Alternatively, you can of course compile without the build menu by creating a batch file (BAT) containing the following commands. This is a simple text file that can also be started directly by double-clicking on it in Windows. It contains the paths to the Q3Map2 compiler and to your map, which of course you have to adapt to your situation. Actually it is two commands that are executed one after the other. First a BSP file is created from the MAP file and second step an ASE file is created from the BSP file.<\/p>\n

"C:\\mypathtoq3map2\\q3map2.exe" -meta -patchmeta "C:\\Program Files\\World of Padman\\wop\\maps\\myASEmapobject.map"\r\n"C:\\mypathtoq3map2\\q3map2.exe" -convert -format ase "C:\\Program Files\\World of Padman\\wop\\maps\\myASEmapobject.bsp"<\/pre>\n
As a third possibility you can also use Q3Map2Build for compiling. In a first step, you activate only the -meta -patchmeta<\/em> switches under Options<\/em> in BSP<\/em>, click on Save<\/em> and then on Build<\/em>. You must deactivate all other calculation phases (VIS, LIGHT and BSPC). In a second step you activate again in BSP<\/em> under Options<\/em> only -convert<\/em> and enter the character string ase<\/em> next to it, if it is not already listed there. Then you click Save<\/em> again and then Build<\/em>. Here too, all other calculation phases remain deactivated (VIS, LIGHT and BSPC).<\/p>\n
\"Q3Map2Build<\/a>
Q3Map2Build BSP 1st step (left) and BSP 2nd step (right)<\/p><\/div>\n
No matter which way you use, after the compilation was finished successfully, you will find the new ASE file in the maps subdirectory of your WoP installation. For the sake of order, create a new directory of your choice, e.g. under models\/mapobjects\/mymapobjects\/<\/em> and move your ASE map object there.<\/p>\n
More detailed patches<\/h2>\n
If, in addition to brushes, you have also used patches, i.e. curved surfaces, and if these appear too angular after compiling the ASE model, you can increase the number of subdivisions to be made in your geometry using the parameter subdivisions<\/em> by specifying a value of 0 and greater. The higher the value, the higher the triangulation, but this can affect the performance in the game. So, depending on the size of the patches you use, this is where you should try it out. The parameter can be considered directly in the first BSP step of the BAT file.<\/p>\n
"C:\\mypathtoq3map2\\q3map2.exe" -meta -patchmeta -subdivisions 2 "C:\\Program Files\\World of Padman\\wop\\maps\\myASEmapobject.map"\r\n"C:\\mypathtoq3map2\\q3map2.exe" -convert -format ase "C:\\Program Files\\World of Padman\\wop\\maps\\myASEmapobject.bsp"<\/pre>\n
Alternatively you can also configure the map2ase command in the main menu of the Radiant under Build > Customize…<\/em> yourself. Unfortunately Q3Map2Build does not offer this parameter, at least I haven’t found it yet.<\/p>\n
\"Customize<\/a>
Customize the map2ase command in the build menu of the Radiant<\/p><\/div>\n
Importing the map object and setting spawnflags<\/h2>\n
Now you are able to import your previously converted brushwork as a new map object into your map via the entity misc_model<\/em>. Open the Entity Inspector by pressing the key N and enter as key spawnflags<\/em> with the value 4<\/em>. This will cause the Q3Map2 compiler to take the model into account during the LIGHT calculation phase and thus automatically provide it with a light map. If you also want to automatically clip the map object, you have to enter a 6<\/em> instead of a 4<\/em> for the key spawnflags<\/em>.<\/p>\n