3 <title>Q3Radiant Editor Manual: Page 1.2</title>
\r
4 <link rel = "stylesheet" type = "text/css" href = "../styles/q3rad.css">
\r
7 <h1 class = "MsoTitle">Q3Radiant Editor Manual</h1>
\r
9 <h1><a name = "install">Installation & Set Up</a></h1>
\r
10 Instalation of the editor has changed in the latest build. It is much more simple then before.
\r
12 <h2><a name = "insted">Installing the editor</a></h2>
\r
13 Run the setup file you downloaded of the latest GTKradiant program. You know longer have to install GTKRadiant to the Quake3 directory. It can reside in any directory you would like to have it.
\r
15 <h2><a name = "instpath">Setting up Paths</a></h2>
\r
16 During installation you will be asked where your Quake3 game is located. Browse to the folder and select Ok. Then you will be prompted for a directory name for the Quake3 game pak. Setup will create this directory in the Quake3 game directory.
\r
18 You will then be prompted for your Return To Castle Wolfenstein folder. Repeat the same process as you did for Quake3, only this time pointing to your RTCW directory.
\r
20 <h2><a name = "imprperf">Improving Performance</a></h2>
\r
21 If you find that the editor is sluggish on your system, try some or all of the following tweaks:
\r
24 <li>On the View menu, check Cubic Clipping to be ON. This reduces the number of game components in view, by shortening the distance that the editor can "see." Use CTRL + to set the distance to 13 (a good number in this case).
\r
25 <li>On the Textures menu, open the Render Quality option and select an option higher on the list than your current setting. We recommend not going below Nearest MipMap first. This reduces the amount of blending and filtering in the textures as they are seen in the Camera window, but still lets you see what the textures look like in a relatively undistorted manner. The Nearest setting will further improve performance, but textures may be distorted when seen in perspective.
\r
26 <li>On View Menu, open the Entities as
\85 option and select an option higher on the list than your current setting.
\r
27 <li>Select Preferences
\85 from the Edit Menu. Under
\93Display / 3D View
\94, deselect (uncheck)
\93Update XY views during mouse drags.
\94 This will stop the 2D-map window(s) from being repeatedly redrawn during Camera window mouse drags.
\r
28 <li>Select Preferences
\85 from the Edit Menu. Under
\93Display / Texturing Settings
\94, move the slider bar under "Texture Quality" one or more settings to the left, reducing overall texture quality.
\r
29 <li>Select Preferences - from the Edit Menu. Under
\93Interface / Editing
\94, lower the number of
\93Patch Subdivisions
\94 to a lower number.
\r
30 <li>Further performance can be gained by turning off curves (CTRL + p) or reducing curve displays to wireframe only.
\r
33 <h2><a name = "setpref">Setting up Preferences</a></h2>
\r
34 To set up your editing preferences, open the Edit menu and select Preferences. Use preferences to set a variety of options and editor behavior based on your personal preferences.
\r
36 <img src="../Q3Rad_Manual_files/image002.png" width=543 height=337 border=0 align="right" alt="">
\r
39 <span class = "subheading"><i></i>Game Settings / Select The Game</i></span>
\r
42 GTKRadiant now stores preferences on a per game basis. For instance: Any settings you set up for Quake3 are stored for that game mode only. Switching to Return To Castle Wolfenstein mode, will use the preferences you setup when that Game mode was set up.
\r
46 <span class = "subheading"><i>2D Display</i></span>
\r
48 <li>OpenGl Display Lists - Uncheck this option if you encounter any graphic errors. This can some times cuase problems with bad opengl drivers.
\r
49 <li>OpenGL Antialliased Points and Lines - This will render all points and lines in the 2D view using antialiasing. This can slow down the 2d view if your video card can not handle antialiasing very well.
\r
50 <li>Solid Selection Boxes - This will make anything selected draw with solid lines rather then the old style of dashed boxes. This can slow down the 2D view as well.
\r
51 <li>Display Size Info - If this is checked on, it will display the size information of any object selected.
\r
52 <li>Alternate Vertex Edge Handles - This changes the shape (a little bit) of the vertex and edge points when in either vertex or edge manipulation mode.
\r
55 <p><span class = "subheading"><i>3D View</i></span>
\r
56 <br>Thanks to some new code. Radiants 3D View is Ultra fast.
\r
58 <li>Movement Velocity - This will increase or decrease the movement of forward, back, and strafing speed in the 3d view.
\r
59 <li>Rotational Velocity - This will increase or decrease the turning speed in the 3D View.
\r
60 <li>Freelook in Camera View - With this checked, you will be able to use free look in the 3D View. Just Right Click in the 3d view to turn on free look, and Shift + Right Click again to turn it off.
\r
61 <li>Invert Mouse In Freelook - This will reverse the mouse controls in freelook mode.
\r
62 <li>Discrete Movement - If checked, this cuases the view in the 3d view to move one step at a time. If unchecked the movement is smoother.
\r
63 <li>Update XY Views On Camera Move - When interacting with the camera (which you will do a lot), turning this off will NOT update the camera icon location in the Map windows automatically. This can help with speed but prevents you from seeing exactly where the camera icon is positioned.
\r
66 <p><span class = "subheading"><i>Texture Settings</i></span>
\r
68 <li>Texture Quality - This will increase or decrease the texture quality displayed in the texture window and 3D View.
\r
69 <li>Texture Subsets - This provides a texture edit window within the texture window. It is still buggy as of build 188. It puts a text field at the top of the Texture window. Type in the first few letters of a texture name and the window will only display the textures beginning with that letter or letters.
\r
70 <li>Texture Scrollbar - If checked, this will add a scroll bar to the texture window.
\r
71 <li>Tex Increment Matches Grid - If checked, this will cuase Radiant to use the grid spacing when moving and aligning textures with the shift + arrow keys.
\r
72 <li>Default Scale - The default scaling of textures on load up of the editor.
\r
73 <li>Startup Shaders - You can choose to have certain shaders load upong startup of the editor or to not have any load on startup.
\r
78 <span class = "subheading"><i>Layout</i></span>
\r
80 <li>Layout - Choose 1 of 4 layouts.
\r
82 <li><img src = "../Q3Rad_Manual_files/image004.png" width = 31 height = 31 vspace = 3 hspace = 3 align = "left">Split Window View - This is the QeRadiant default view. The Camera, XY Map, Z-axis Scale, Texture, and Console windows are constantly displayed. While the arrangement of the windows cannot be changed, their size is adjustable by pulling the window border splitters. The Entity and Group windows share a common pop-up window. This arrangement is one that may work particularly well for mappers using smaller monitors and slower computers.<br><br>
\r
83 <li><img src = "../Q3Rad_Manual_files/image006.png" width = 31 height = 31 vspace = 3 hspace = 3 align = "left">Floating Window View - This is the view used by id designers. The position, arrangement, and size of the windows are all adjustable. The windows initially come up on top of one another (a known bug), but once positioned, this view offers the greatest flexibility. The Camera, XY Map, Z-axis Scale, and a shared Entity/Texture/Console/Group window are all displayed simultaneously. Changing the size of one window does not automatically affect the others (it can lay atop the others). Additional map layout views can be cycled from menu commands or bound keys. This view only works well if you have a 20+-inch monitor.
\r
84 <p><strong>Make it Big!</strong> In floating windows mode (ONLY), you can double-click on any window
\92s Title Bar to enlarge the contents of the window to fill the screen. Double clicking on it again reduces it back to normal size.<br><br>
\r
85 <li><img src = "../Q3Rad_Manual_files/image008.png" width = 31 height = 31 vspace = 3 hspace = 3 align = "left">Quad View - The display window is split into four equal-sized windows: Camera, XY Map, YZ Map, and XZ Map. This is similar to other editors and offers four-way viewing. You see the map components in three views simultaneously. The size of the windows (relative to each other) can be adjusted, by pulling the splitters. The combined Entity/Texture/Console/Group window is brought into view as a single, floating window that lays over the others. The Z-axis window is not used in this view. This is a popular editing configuration, but it has significant performance issues. The editor is drawing all the 2D map components three times (plus maintaining a camera view). Some mappers have notice significant performance slow-downs when working with curves. Using the Quad view is only recommended for mappers with more powerful computers.<br><br>
\r
86 <li><img src = "../Q3Rad_Manual_files/image010.png" width = 31 height = 31 vspace = 3 hspace = 3 align = "left">Reverse Split Window View - Essentially the same as the Split Window view, except that the windows are all flopped left to right.<br><br>
\r
88 <li>Floating Z Window - This will make the Z-Window float in the Floating Window View mode.
\r
89 <li>Patch Toolbar - Seems to have been disabled.
\r
90 <li>Use Win32 File Load Dialog - If checked, this will use the common windows style file browser. Unchecked it will have the unique GTK / Linux X-Windows file browser.
\r
93 <span class = "subheading"><i>Mouse</i></span>
\r
95 <li>2 Button / 3 Button - Use 2 button mode or 3 button mode. Each mode is different in some ways. The hot keys and key combinations are generally different for each mode.
\r
96 <li>Right Click To Drop Entities - If checked, this will create a menu where ever you click in the 2D View with a list of the entities you can select and place.
\r
97 <li>Mouse Chaser - Turning this on causes the view to chase the mouse if you drag something off the edge.
\r
98 <li>Alt + Multi-Drag - If this option is checked, you must hold down the ALT key to drag multiple brush edges. This lets you resize more than one brush at a time.
\r
99 <li>Wheel Mouse Inc - This number will adjust the amount the texture window scrolls in the texture window when using the mouse wheel. The higher the number, the faster it scroll basically.
\r
102 <span class = "subheading"><i>Editing</i></span>
\r
104 <li>Vertex Editing Splits Face - This will cuase face splits in brushes when in moving vertex points around and the brush becomes a concave shape.
\r
105 <li>Fix Target/Targetname Collisions - This prevents duplicate target/targetnames from happening if you load a map into your current map. For instance: if you load q3dm7 into q3dm7, it adds _1 to duplicate target/targetname pairs.
\r
106 <li>Cliiper Tool Uses Caulk - When using the clipper tool, the faces that are created from the clip will add a cualk texture to the brush.
\r
107 <li>Dont Clamp Plane Points - This turns off clamping of plane points. This allows for very precise brush/vertex manipulation but can make it difficult to get things properly aligned and can also cause the bsp process to take a LOT longer. In general, this should be unchecked.
\r
108 <li>Select Patches by Bounding Boxes - If checked, you will be able to select patches by there bounding boxes. Note: Bounding boxes for patches must be turned on.
\r
109 <li>Rotation Increment - This allows you to choose the increments in pixels a texture is rotated when rotating a texture with the shift + pgup or pgdn keys.
\r
110 <li>Undo Levels - Set how many undos you can do. This does require memmory so do not set it to high if you do not have alot of memmory.
\r
111 <li>Patch Subdivisions - Select how many subdivisions are drawn on the patches in all views. If set to high it can slow down the editor. If set very low it will look blocky. Essentially it works like the games r_subdivisions option.
\r
116 <span class = "subheading"><i>Startup/Autosave</i></span>
\r
118 <li>Snapshots - If checked, this will create snapshots every 5 minutes of your level. They are saved into your maps directory and have a numbered order (eg. .001 .002) for the file extension.
\r
119 <li>Load Last Project On Open - If checked, GTKRadiant will automatically load the project settings you last used.
\r
120 <li>Load Last Map On Open - If checked, GTKRadiant will load the last map you had open during your last session.
\r
121 <li>Auto-Save Every - Here you can choose to use auto saving, and how many minutes between each auto-save.
\r
124 <span class = "subheading"><i>Paths</i></span>
\r
126 <li>Prefab Path - Here you can choose the directory of where you will have your prefabs ( .pfb ) stored.
\r
127 <li>Game Path - This is now controlled by GTKRadiant. It displays the path of your game executable for which game mode you are in.
\r
128 <li>User Ini Path - This will allow you to choose a user .ini file and its path.
\r
131 <span class = "subheading"><i>Misc</i></span>
\r
133 <li>Light Drawing - This draws lights as shaded triangle things (octahedrons) instead of standard square entities. When enabled, the light entities also show their emitted light color.
\r
134 <li>Log The Console To radiant.log - This will cuase GTKRadiant to create a log file of all output from the GTKRadiant console. This can cuase the editor to slow down, and is normally used for debugging purposes.
\r
135 <li>Use Pak/PK3 Files - This will force GTKRadiant to read from .pak or .pk3 files before searching in the game directories like baseq3.
\r
138 <span class = "subheading"><i>BSP Monitoring</i></span>
\r
140 <li>Enable BSP Process Monitoring - This will have a ms-dos window open when you compile a map from the BSP menu.
\r
141 <li>Stop Compilation On Leak - This will cuase the bsp compile process to halt when a leak is found in a map during the BSP process.
\r
142 <li>Run Engine After Compile - This will cuase the game to launch after the compile process is complete.
\r
143 <li>Activate Sleep Mode When Running The Engine - This is automatic now. GTKRadiant will go into sleep mode when you load the engine after a compile. <p><strong>Warning.</strong> With some video drivers, it is a bad idea to run Quake 2 or Quake III Arena and the Q3Radiant editor. The drivers just will not sustain two demanding OpenGL applications simultaneously. This feature is best left turned off.
\r
146 <!-----============ Below is old ==========---->
\r
149 <h2><a name = "projfile">The Project File</a></h2>
\r
150 The project file contains the paths for the various GTKRadiant file-processing functions. Using the installer to set up the editor should write these for you.
\r
152 <p><span class = "subheading">New Project</span>
\r
153 <div class = "menu">(Menu: File > New Project)</div>
\r
154 <br>This creates a new folder (which you must name) in your Quake III Arena or RTCW directory.
\r
155 <br>This is a good function for mods. You can use a different directory other then baseq3 if you plan to have alot of new resources and dont want to clutter it into the baseq3 folder.
\r
157 <p><span class = "subheading">Load Project</span>
\r
158 <div class = "menu">(Menu: File > New Project)</div>
\r
159 <br>This opens up a browse directory pointed at the scripts directory. It is looking for a text file with a .qe4 file extension.
\r
161 <p><span class = "subheading">Changing the Project File</span>
\r
162 <div class = "menu">(Menu: File > Project Settings)</div>
\r
163 <br>You can edit the project file by changing the pathnames to various functions in field of the dialogue window that pops up. HOWEVER, before doing this, you should make a backup copy of your Quake project file and give it a new name. Make your changes to this new file. If you mess things up, you can always reload the original. This is a good thing to do if you are making maps for a mod that uses a separate set of definitions for entities or directories for textures and want to easily change between types of projects.
\r
165 <p><strong>Project Settings</strong>
\r
166 <ul><strong>Basepath:</strong> This traces a path, beginning in your root directory to the baseq3 where the editor expects to find resources.
\r
167 <p><strong>Mapspath:</strong> This traces a path, beginning in your root directory, to the location where maps are saved and from which they are loaded. The default is the maps directory.
\r
171 <p><strong>Rshcmd:</strong> This means "remote shell command." Use it only if you are directing a remote processing device (not your editing computer) to compile maps. The syntax for the field is: "rsh [processor name]"
\r
175 <p><strong>Remotebasepath:</strong> If you are running your compile from your editing computer, this should be the same as your basepath. If you are working off a remote compling device, this should trace the full path to the to the baseq3 folder where the compiler will find the resources it requires.
\r
179 <p><strong>Entitypath:</strong> This traces a path to the definition file for your game entities. This can either be a .c file which contains the game code, or a .def file which contains more instructive information about the entities.
\r
180 <br><br>Note: As of GTKRadiant 1.2.1 the default path for this is "Radiant", also known as the new game packs style it uses which allows for the remote installation of GTKRadiant anywhere on your computer.
\r
183 <p><strong>Texturepath:</strong> This traces a path, beginning in your root directory, to the location from which textures are loaded. The default is the textures directory.
\r
187 <p><strong>Menu commands</strong>
\r
188 <br>These commands are your map compile commands. You can CHANGE these commands or ADD your own. Each new command must start with
\93bsp_
\94 The following is the compile command string for
\93bsp_Fullvis
\94 taken off one of our project files.
\r
190 <ul class = "type">! q3map $ && ! q3map -vis -threads 8 $ && ! q3map -light -threads 8 $</ul>
\r
192 <p><strong>Command parameters:</strong>
\r
195 <tr valign = "top">
\r
196 <td><strong>!</strong></td>
\r
197 <td>The exclamation mark is replaced by the contents of the rshcmd field. It is the path to the processor.</td>
\r
199 <tr valign = "top">
\r
200 <td><strong>$</strong></td>
\r
201 <td>The dollar sign is replaced by the Mapspath.</td>
\r
203 <tr valign = "top">
\r
204 <td><strong>&&</strong></td>
\r
205 <td>The double ampersand is the command terminator (end of command)</td>
\r
207 <tr valign = "top">
\r
208 <td><strong>q3map</strong></td>
\r
209 <td>This is the process command. Without a switch after it, it performs the .bsp compile phase.</td>
\r
211 <tr valign = "top">
\r
212 <td><strong>-vis</strong></td>
\r
213 <td>This is a switch to select the vis compile phase.</td>
\r
215 <tr valign = "top">
\r
216 <td><strong>-light</strong></td>
\r
217 <td>This is a switch to select the lighting compile phase.</td>
\r
219 <tr valign = "top">
\r
220 <td><strong>-threads</strong></td>
\r
221 <td>This is a switch to break the compile up into a number of different processor threads. The number of processors follows the switch parameter.</td>
\r
226 <p><strong>Other parameters</strong>
\r
228 <tr valign = "top">
\r
229 <td><strong>-onlyents</strong></td>
\r
230 <td>Process only the entities in the map.</td>
\r
232 <tr valign = "top">
\r
233 <td><strong>-fast</td>
\r
234 <td>A quicker process. However, it treats the map as if it were all one vis area.</td>
\r
236 <tr valign = "top">
\r
237 <td><strong>-extra</strong></td>
\r
238 <td>As in -light -extra. This is a second lighting pass that more finely subdivides the map into areas of light and shadow.</td>
\r
240 <tr valign = "top">
\r
241 <td><strong>-nowater</strong></td>
\r
242 <td>Compiled without liquids in the map. Used in the first compile phase only.</td>
\r
244 <tr valign = "top">
\r
245 <td><strong>-nocurves</strong></td>
\r
246 <td>Compiles without curves in the map. Used in the first compile phase only.</td>
\r
251 <p><strong>Misc settings</strong>
\r
252 <br><strong>Use brush primitives in MAP files.</strong>
\r
253 <br>Once this is set for a map, the program converts the texture mapping to this format. Once chosen, there is no going back to the old format. Brush primitives are described in detail under the Working with Textures section.
\r
255 <h2><a name = "setwin">Setting up the Windows</a></h2>
\r
256 There are six configurable windows in Q3Radiant.
\r
258 <p><span class = "subheading">The Camera Window (CAM)</span>
\r
259 <br>The Camera window initially shows a gray field. This is where the 3D in-progress view of your map appears. You can SHIFT + click mouse button 1 to select objects in this window. If the images in this window appear overly dark, you can adjust the gamma value. Open the Misc menu and select Gamma. Enter a value between 0 and 1 for the light value. Close the program. Reopen the program. Check the darkness. Repeat this until you have a value you like.
\r
261 <p><span class = "subheading">Entity/Texture/Console/Group Window</span>
\r
262 <br>Depending on the Windows layout view that you
\92ve chosen, one or more of the following sub-windows share this window. They are selectable by the tab at the bottom of the window, or by shortcut keys.
\r
264 <p><strong>Entity Window</strong>
\r
265 <div class = "menu">(Shortcut: N)</div>
\r
266 The Entity window is one of four windows that share the same window space: Console, Entity and Texture and Group. The entity window is used to create and modify the properties of game entities. The uppermost box in this window contains the entity names. Use the scroll bar to find the one you want or for speed, type in the first letter of the class of entity you desire (
\93w
\94 for weapon,
\93I
\94 for item and so on). Refer to the Working with Entities section for more details on this.
\r
268 <p><strong>Texture Window</strong>
\r
269 <div class = "menu">(Shortcut: T)</div>
\r
270 The Texture window displays textures that have been loaded from the texture directories for easy use. The texture subset tool (set in preferences) allows you to quickly jump to a texture if you know the first few letters of its name. The scrollbar tool adds normal Windows functionality to the window. The most common method of navigating the window is to right-mouse click and drag through the window contents. SHIFT + right-mouse click and drag speeds up the rate of movement through the window
\92s contents. A thin green outline around a texture indicates a non-shadered texture in use in the map. A thin white outline indicates a shadered texture. A bold red outline indicates a selected texture.
\r
272 <p><strong>Console Window</strong>
\r
273 <div class = "menu">(Shortcut: O)</div>
\r
274 The console tracks the editor
\92s processes, like loading, saving, and compiling. When you compile (selecting an option from the bsp menu), the contents of the console are dumped into the junk.txt file in your Temp file folder on your root drive. In the Split Window view layout, the Console window is always in view.
\r
276 <p><strong>Groups Window</strong>
\r
277 <div class = "menu">(Shortcut: none)</div>
\r
278 This window will deal with the future grouping functions that will soon be a part of the editor. At this time, it is only a non-functioning window.
\r
280 <p><span class = "subheading">Z-axis Scale Window</span>
\r
281 <br>This window is used by three of the four views to show the Z-axis position (height) of the Point of View and any selected map components.
\r
283 <p><span class = "subheading">Map Window(s)</span>
\r
284 <p><span class = "subheading">The Grid</span>
\r
285 <br>Think of the Map window as a piece of graph paper, neatly divided into squares. However, unlike graph paper, you can change the size of the grid to fit your needs of the moment. You can change grid size from the Grid menu, but it
\92s faster to learn the key shortcuts listed below.
\r
287 <p><strong>Setting Grid Size</strong>
\r
289 <p><table cellpadding = 3>
\r
295 <td>1 unit grid</td>
\r
296 <td align = "center">(1)</td>
\r
299 <td>2 unit grid</td>
\r
300 <td align = "center">(2)</td>
\r
303 <td>4 unit grid</td>
\r
304 <td align = "center">(3)</td>
\r
307 <td>8 unit grid</td>
\r
308 <td align = "center">(4)</td>
\r
311 <td>16 unit grid</td>
\r
312 <td align = "center">(5)</td>
\r
315 <td>32 unit grid</td>
\r
316 <td align = "center">(6)</td>
\r
319 <td>64 unit grid</td>
\r
320 <td align = "center">(7)</td>
\r
324 <td>Decreases the size of the grid. [ key</td>
\r
328 <td>Increases the size of the grid. ] key</td>
\r
333 <p><strong>Grid and Window Layouts</strong>
\r
334 <br>There are four distinct ways of laying out the work windows for Q3Radiant.
\r
336 <p><div class = "tip"><strong>Design Notes:</strong>
\r
337 <br>Try not to build architecture with a grid smaller than 8 units.
\r
338 <br>Use a smaller grid if you need to build small details.
\r
339 <br>Use a large grid (32 or 64) for roughing in a level.
\r
340 <br>Use a large grid for moving large chunks of architecture around.</div>
\r
342 <p><strong>Snap to Grid</strong>
\r
343 <br>When this is checked, the edges and vertices of brushes and patches will
\93snap
\94 to grid coordinates. Unless you are attempting some very fussy maneuvering of a map component, Snap to Grid makes life much easier. In fact, if you are building objects out of curve patches, it is crucial that you be able to line up patch control points with the vertices of surrounding solid geometry brushes.
\r
345 <p><span class = "subheading">Colors</span>
\r
346 <br>Q3Radiant allows you to select the colors of your grids and tools. Because the manual refers to the colors of some features, you may wish to wait until you are more comfortable using the editor before changing too many things. You can always revert to the Q3Radiant defaults, should you choose change too much.
\r
348 <p>To change Map window and Texture window colors, select the
\93Misc
\94 menu and choose colors. The pop-up lists a number of options.
\r
350 <p><strong>Themes</strong>
\r
351 <br>Brings up three options:
\r
353 <ul><strong>QE4 Original:</strong> The settings for id
\92s original Quake 2 editor
\r
354 <br><strong>Q3Radiant Original:</strong> The default setting.
\r
355 <br><strong>Black & Green:</strong> a black background with a green grid major.
\r
358 <p>Each of the following options opens the Windows color selector.
\r
360 <p><strong>Grid Background
\85</strong>
\r
361 <br>The background color for the map window.
\r
363 <p><strong>Texture Background
\85</strong>
\r
364 <br>The background color behind the textures in the texture window. This is probably best left a neutral color.
\r
366 <p><strong>Grid Major
\85</strong>
\r
367 <br>These bolder grid lines mark 64 unit increments in the map window. These never change.
\r
369 <p><strong>Grid Minor
\85</strong>
\r
370 <br>The finer grid lines in the map window.
\r
372 <p><strong>Grid Text
\85</strong>
\r
373 <br>The color of the scale numbers along the left and top of the map window.
\r
375 <p><strong>Grid Blocks
\85</strong>
\r
376 <br>These lines mark the 1024 x 1024 unit grids on the map.
\r
378 <p><strong>Default Brush
\85</strong>
\r
379 <br>This is the color of unselected brushes in the map.
\r
381 <p><strong>Selected Brush
\85</strong>
\r
382 <br>The color of selected brushes in the map.
\r
384 <p><strong>Active View Name
\85</strong>
\r
385 <br>This is the text that says
\93XY Top
\94 or
\93YZ Side
\94 or
\93XZ Front
\94 in the map view window(s).
\r
389 <p align = "center"><a href = "pg1_1.htm">Back</a> | <a href = "../index.htm">Home</a> | <a href = "../ch02/pg2_1.htm">Next</a>
\r
projects / xonotic / netradiant.git / blob